reference-creation

Create a structured references/ directory with topic-specific guides and cross-links.

7|Updated Jan 29, 2026

Search Tags:#documentation #readability #reference #navigation #organization #modular #subtopics

Ready to run

npx skills add https://github.com/joabgonzalez/ai-agents-skills --skill reference-creation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reference-creation
Source: https://github.com/joabgonzalez/ai-agents-skills/tree/main/skills/reference-creation
Command: npx skills add https://github.com/joabgonzalez/ai-agents-skills --skill reference-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex skills with 40+ patterns or multiple sub-topics can overwhelm learners if all content is packed into a single document. This Skill provides a standardized approach to organizing deep knowledge into navigable reference guides.

Core Features & Use Cases

Create a dedicated references/ directory for complex skills when SKILL.md grows too long or contains many patterns.
Name files descriptively as topic.md to clearly delineate sub-topics and improve discoverability.
Provide cross-links between SKILL.md and references and between references themselves to support quick navigation.
Use case: a skill with 70 patterns can be split into focused references (hooks.md, components.md, performance.md, etc.) to enable targeted study and efficient token usage.

Quick Start

Create a references folder for this skill, add a README.md with navigation, and create 4 to 9 topic files with descriptive names.

Frequently Asked Questions about reference-creation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I organize complex documentation with too many patterns in a single file?▼

To organize complex documentation with too many patterns, create a structured references/ directory containing topic-specific guides. This modular approach splits sub-topics into focused files, improving readability and enabling targeted study instead of overwhelming learners in a single document.

When should I split my skill documentation into modular reference files?▼

You should split documentation into modular reference files when your main SKILL.md grows too long or contains 40+ patterns. This enforces consistent naming and cross-linking conventions, preventing deep knowledge from overwhelming learners in a single document.

What is the best way to structure a references directory for sub-topics?▼

The best way to structure a references directory is creating a README.md for navigation alongside 4 to 9 topic files. Descriptive naming delineates sub-topics, while cross-links between files support quick navigation and consistent organization.

How do I cross-link navigation between modular reference guides?▼

Cross-link navigation between modular reference guides by applying standardized conventions for linking from the main file to topic-specific guides, and connecting the reference files themselves to ensure consistency and ease of navigation.

Does splitting documentation into topic-specific guides improve readability for large skills?▼

Splitting documentation into topic-specific guides improves readability by enabling targeted study and efficient token usage. Focused reference files prevent overwhelming learners, ensuring deep knowledge remains navigable and accessible.

What are the limitations of keeping complex skill patterns in a single document?▼

Keeping complex skill patterns in a single document overwhelms learners and hinders navigation. Without a modular references directory, discovering specific sub-topics becomes difficult, and token usage increases inefficiently during targeted study.