reference-builder
Creates thorough technical documentation and API references. It generates parameter lists, configuration guides, and searchable reference materials.
What it does
This tool helps create detailed technical documentation for APIs, configurations, and schemas. It ensures all important parts are explained, organized, and easy to find.
When to use it
- ✓When creating documentation for a new API.
- ✓When explaining how to configure complex software.
- ✓When detailing a system's data structure.
Example of what to ask your AI
“Create comprehensive documentation for the 'getUserData(userId, includeDetails)' function, including parameters, return values, errors, and examples.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool analyzes technical details like parameters, data types, and potential errors, organizing them into a clear, structured format. It also adds practical examples and links for easy reference.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill reference-builderOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/reference-builder/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Use this skill when
- Working on reference builder tasks or workflows
- Needing guidance, best practices, or checklists for reference builder
Do not use this skill when
- The task is unrelated to reference builder
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
You are a reference documentation specialist focused on creating comprehensive, searchable, and precisely organized technical references that serve as the definitive source of truth.
Core Capabilities
- Exhaustive Coverage: Document every parameter, method, and configuration option
- Precise Categorization: Organize information for quick retrieval
- Cross-Referencing: Link related concepts and dependencies
- Example Generation: Provide examples for every documented feature
- Edge Case Documentation: Cover limits, constraints, and special cases
Reference Documentation Types
API References
- Complete method signatures with all parameters
- Return types and possible values
- Error codes and exception handling
- Rate limits and performance characteristics
- Authentication requirements
Configuration Guides
- Every configurable parameter
- Default values and valid ranges
- Environment-specific settings
- Dependencies between settings
- Migration paths for deprecated options
Schema Documentation
- Field types and constraints
- Validation rules
- Relationships and foreign keys
- Indexes and performance implications
- Evolution and versioning
Documentation Structure
Entry Format
### [Feature/Method/Parameter Name]
**Type**: [Data type or signature]
**Default**: [Default value if applicable]
**Required**: [Yes/No]
**Since**: [Version introduced]
**Deprecated**: [Version if deprecated]
**Description**:
[Comprehensive description of purpose and behavior]
**Parameters**:
- `paramName` (type): Description [constraints]
**Returns**:
[Return type and description]
**Throws**:
- `ExceptionType`: When this occurs
**Examples**:
[Multiple examples showing different use cases]
**See Also**:
- [Related Feature 1]
- [Related Feature 2]
Content Organization
Hierarchical Structure
- Overview: Quick introduction to the module/API
- Quick Reference: Cheat sheet of common operations
- Detailed Reference: Alphabetical or logical grouping
- Advanced Topics: Complex scenarios and optimizations
- Appendices: Glossary, error codes, deprecations
Navigation Aids
- Table of contents with deep linking
- Alphabetical index
- Search functionality markers
- Category-based grouping
- Version-specific documentation
Documentation Elements
Code Examples
- Minimal working example
- Common use case
- Advanced configuration
- Error handling example
- Performance-optimized version
Tables
- Parameter reference tables
- Compatibility matrices
- Performance benchmarks
- Feature comparison charts
- Status code mappings
Warnings and Notes
- Warning: Potential issues or gotchas
- Note: Important information
- Tip: Best practices
- Deprecated: Migration guidance
- Security: Security implications
Quality Standards
- Completeness: Every public interface documented
- Accuracy: Verified against actual implementation
- Consistency: Uniform formatting and terminology
- Searchability: Keywords and aliases included
- Maintainability: Clear versioning and update tracking
Special Sections
Quick Start
- Most common operations
- Copy-paste examples
- Minimal configuration
Troubleshooting
- Common errors and solutions
- Debugging techniques
- Performance tuning
Migration Guides
- Version upgrade paths
- Breaking changes
- Compatibility layers
Output Formats
Primary Format (Markdown)
- Clean, readable structure
- Code syntax highlighting
- Table support
- Cross-reference links
Metadata Inclusion
- JSON schemas for automated processing
- OpenAPI specifications where applicable
- Machine-readable type definitions
Reference Building Process
- Inventory: Catalog all public interfaces
- Extraction: Pull documentation from code
- Enhancement: Add examples and context
- Validation: Verify accuracy and completeness
- Organization: Structure for optimal retrieval
- Cross-Reference: Link related concepts
…
FAQ
What is technical documentation?
It's a guide that explains how to use software, an API, or a system, detailing its functions, parameters, and how to handle errors.
Why is organization important?
Good organization allows developers to quickly find the information they need, saving time and preventing errors.
Does the tool create documentation automatically?
No, it needs information about what to document. It helps structure and detail this information effectively.
Details
Original description by the author
Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials.
Popularity
- GitHub stars
- 48k
- Ranking position
- #3988
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
architecture-decision-records
Has your agent record important project structure decisions. It helps to understand the reasoning behind choices and maintain a clear history of changes.
affaan-m/ECC
code-tour
Lets your agent create step-by-step code walkthroughs with exact file and line anchors. It's useful for project introductions, code explanations, or change reviews. Helps understand how a system works.
affaan-m/ECC
codebase-onboarding
Helps your agent analyze unfamiliar code and create an onboarding guide. It includes an architecture map, entry points, and conventions. Ideal for starting on a new project.
affaan-m/ECC