docs-as-marketing

This skill empowers software agents to bridge the gap between technical documentation and marketing strategy. It focuses on the reality that for developers, documentation is often the primary touchpoint before product adoption, making it the most critical conversion tool in your marketing stack. The skill guides the creation of documentation that serves the dual purpose of education and acquisition, ensuring your content ranks for technical search queries while effectively guiding users toward activation.

• Information Architecture: Implementing logical structures for Tutorials, How-to Guides, API References, and Explanations to reduce bounce rates and cognitive load.

• Quickstart Optimization: Applying the 5-minute rule to design high-conversion onboarding flows, including prerequisite validation, installation commands, and 'what's next' pathways.

• API Documentation Best Practices: Standardizing request/response formats, providing verifiable copy-paste examples, and documenting error codes to ensure reliable integration.

• SEO for Developers: Optimizing documentation content to capture technical search intent, focusing on 'how-to' queries and specific error message troubleshooting.

• Conversion-Focused Writing: Moving beyond dry technical specs to articulate the 'what', 'why', and 'how' of product capabilities, building developer trust through transparency and accuracy.

• Inputs: Requires access to your API endpoints, code snippets, existing documentation structure, and identified developer audience personas (via developer-audience-context).

• Outputs: Actionable markdown-based documentation files, optimized quickstart flows, restructured navigation hierarchies, and high-fidelity code examples.

• Practical Usage: Use this skill when auditing your current docs for drop-off points, launching new API features, or optimizing your getting-started experience. It is designed to be used in conjunction with devrel-content and sdk-dx skills to maintain consistency across the developer lifecycle. Always prioritize functional code snippets and verify that all curl or SDK examples are up-to-date to prevent developer frustration.