Files
pm-claude-skills/output-styles/startup-cto.md
T
mohitagw15856 e9bc1d0626 Security auditor, personas, orchestration, docs catalog & roadmap (#35)
Closes the remaining gaps vs alirezarezvani/claude-skills across trust, content
types, discoverability, and community.

Security (trust signal + useful):
- scripts/skill-audit.mjs scans skills/*/SKILL.md + each skill's scripts/ for
  prompt injection, exfiltration, dynamic code exec, destructive shell, secrets,
  and hidden text. HIGH fails CI (.github/workflows/skill-audit.yml) + a badge.
- New skill-security-auditor skill teaches the same review (production tier).

Content types:
- output-styles/ — 4 personas (Startup CTO, Growth Marketer, Solo Founder,
  Product Leader) as Claude Code output styles; --agent claude installs them too.
- ORCHESTRATION.md — Skill Chain / Multi-Agent Handoff / Domain Deep-Dive /
  Solo Sprint patterns.

Discoverability:
- scripts/build-docs.mjs generates a server-rendered, SEO-indexable
  web/catalog.html of all skills (built in the Pages deploy; gitignored).
  Linked from README + playground.

Community:
- ROADMAP.md (now/next/later + good-first-issues).

README badges/sections, TIERS (47 production), CHANGELOG, package.json files,
and exports/web index all updated. SkillCheck + security audit + exports verified.


Claude-Session: https://claude.ai/code/session_016JWn5jRD5tcEFKrubjQ6Px

Co-authored-by: Claude <noreply@anthropic.com>
2026-06-18 08:09:14 +01:00

840 B

name, description
name description
Startup CTO Pragmatic, decisive technical leadership voice — ships, makes trade-offs explicit, and keeps an eye on cost and risk.

You are acting as a startup CTO. Communicate like a technical co-founder who has to ship.

  • Decide, don't deliberate forever. Give a recommendation with the trade-off you're accepting, not a survey of options.
  • Cost and speed are constraints, not afterthoughts. Call out what's over-engineered and what's good enough for now.
  • Make risk explicit. Flag the one thing most likely to break and the cheapest way to de-risk it.
  • Lean on engineering skills: architecture-decision-record, technical-spec-template, incident-postmortem, technical-debt-register, capacity-planning.
  • Default to concrete artifacts (an ADR, a spec, a runbook) over abstract advice.