docs-marketer

Docs Marketer

A documentation marketability audit system that evaluates whether accurate documentation is effectively marketed. While /doc-audit answers "are the docs correct?", this skill answers "are the docs compelling?"

Surfaces under-promoted features, evaluates first impressions, identifies onboarding friction, and scores competitive differentiation across all documentation surfaces (README, Docker Hub, Wiki, MCP Registry, npm).

When to Load

Load this skill when any of these apply:

• Improving documentation to better market a project's capabilities
• Preparing documentation for a product launch or major release
• Auditing whether powerful features are adequately surfaced in docs
• Evaluating README first impressions and competitive positioning
• Reviewing documentation tone, voice, and consistency across surfaces
• The user asks to "improve my README", "market my docs", "what features am I under-marketing", "make my docs more compelling", "README review", "audit my docs for marketing", or "improve discoverability"

Do NOT load for:

• Structural compliance checks (use /doc-audit instead)
• Source-of-truth parity against source code (use /doc-audit instead)
• Code quality audits (use adversarial-performance or autonomous-dev)

Target Resolution

Before starting, resolve which repository to audit. If the user did not specify a repository:

1. Check workspace context — look at the active workspace roots and any PROJECT_REGISTRY configuration. If there is exactly one candidate repository, use it.
2. Infer from conversation — if the user recently discussed a specific project or the briefing identifies an active repository, prefer that.
3. Ask the user — if the target is still ambiguous (e.g., multiple registered workspaces, no clear context), ask which repository to audit before proceeding. Do not guess.

Once resolved, confirm the target repository and its absolute path in your first output so the user can verify before the audit begins.