reference-docsReference documentation patterns for API and symbol documentation. Use when writing reference docs, API docs, parameter tables, or technical specifications....
Install via ClawdBot CLI:
clawdbot install anderskev/reference-docsGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Accesses sensitive credential files or environment variables
process.env.API_KEYAI Analysis
The skill definition is a documentation template and style guide focused on writing reference documentation. It contains no code, API calls, or executable instructions. The flagged credential access signal appears to be a false positive, likely from an example code snippet within the documentation template, not from the skill's operational logic.
Audited Apr 17, 2026 · audit v1.0
Generated Apr 26, 2026
A SaaS company needs to write clear and consistent API reference docs for its REST endpoints. Using this skill, they can create parameter tables, return types, and runnable code examples that help experienced developers integrate quickly. The structured template ensures all endpoints follow the same format, reducing support inquiries.
An open source maintainer wants to document a JavaScript library with multiple functions and options. This skill provides patterns for documenting each symbol with consistent headings, parameter tables, and example code. The resulting docs help users find specific details without reading tutorials.
A large enterprise needs to document internal microservice APIs for other teams. Using the reference docs skill, they can create concise reference pages with endpoint details, authentication requirements, and error conditions. This speeds up cross-team development and reduces onboarding time.
A company building a developer tool (e.g., CLI or SDK) wants to provide quick reference material for advanced users. The skill helps document command flags, function signatures, and configuration options with scannable tables and realistic examples. This improves user self-service and reduces documentation burden.
A team using GraphQL needs to document their schema, including types, queries, mutations, and arguments. This skill can be adapted to produce field-by-field reference pages with type information, descriptions, and example queries. Developers can quickly look up available operations and their parameters.
Self-serve developer tools with excellent reference documentation reduce time-to-value and increase activation. Clear API docs lower the barrier for trial users to integrate, driving conversions from free to paid tiers.
Open source projects attract community adoption via well-documented APIs. The reference docs skill helps maintain clear, professional documentation for the core product, while premium enterprise features (e.g., SSO, audit logs) are upsold separately.
A platform that aggregates multiple APIs can use this skill to standardize documentation across all published APIs. Consistent, high-quality reference docs attract more developers to the marketplace, increasing API usage and transaction fees.
💬 Integration Tip
Pair this skill with 'docs-style' to ensure all reference docs adhere to a consistent tone and style guide, maximizing readability and professionalism.
Scored Apr 19, 2026
Manage Trello boards, lists, and cards via the Trello REST API.
Query and manage Linear issues, projects, and team workflows.
Interact with Linear for issue tracking. Use when creating, updating, listing, or searching issues. Supports viewing assigned issues, changing status, adding comments, and managing tasks.
Manage Plane.so projects and work items using the `plane` CLI. List projects, create/update/search issues, manage cycles and modules, add comments, and assign members.
Prioritize GitHub issues by ROI, solution sanity, and architectural impact. Identifies quick wins, over-engineered proposals, and actionable bugs. Use for is...
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira...