How do I install the Aps Documentation skill?

Run npx skillmds add majiayu000/aps-documentation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Aps Documentation safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aps Documentation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aps Documentation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aps Documentation?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aps Documentation by majiayu000 — Agent Skill

Name: Aps Documentation
Rating: 4.2 (5 reviews)
Author: majiayu000

Aps Documentation

Comprehensive skill for working with Agile Protocol Specification documentation. Automatically activates when creating, editing, or reviewing APS content. Provides templates, naming conventions, and document lifecycle guidance.

majiayu000 6b1cfa2 2 files · 3.0 KB Updated Sep 9, 2026 567 repo stars

File contents

APS Documentation Skill

This skill provides comprehensive guidance for working with the Agile Protocol Specification documentation system.

When This Skill Activates

Creating new documentation chapters or sections
Editing existing APS content
Reviewing documents for compliance
Managing document lifecycle transitions
Working with metadata-rich filenames

Key Concepts

Document States

Mutable States (open to changes):

Draft: Initial creation, open for major edits
Provisional: Temporary acceptance, awaiting full review
In Review: Under formal review process

Immutable States (locked):

Accepted: Approved by stakeholders
Final: Officially complete, archived

Metadata-Rich Naming

Pattern: {Type}_{Version}_{State}_{Date}_{Author}.ext

Examples:

requirements_v1.0.0_draft_2024-03-22_SC.md
architecture_v2.1.0_accepted_2024-04-15_Team.md

Templates

New Chapter

# [Chapter Title]

[Introduction explaining purpose]

## [Main Section]

[Content]

## Conclusion

[Key takeaways]

---

Context File

---
module-name: [Name]
version: 1.0.0
description: |
  [Purpose and content description]
related-modules:
  - name: [Related]
    path: ./path/to/module.md
technologies:
  - Markdown
  - mdBook
conventions:
  - Follow APS naming conventions
  - Include metadata headers
---

Best Practices

Structure First: Plan document hierarchy before writing
Clear Headings: Use descriptive section titles
Cross-Reference: Link related content
Context Files: Create for new modules
Update SUMMARY.md: Add new chapters to navigation
Build Test: Run mdbook build to verify

Resources

Main SUMMARY: specification-guide/src/SUMMARY.md
Glossary: specification-guide/src/appendices/glossary.md
Templates: specification-guide/src/appendices/templates_examples.md

---name: aps-documentationdescription: Comprehensive skill for working with Agile Protocol Specification documentation. Automatically activates when creating, editing, or reviewing APS content. Provides templates, naming conventions, and document lifecycle guidance.--- # APS Documentation Skill This skill provides comprehensive guidance for working with the Agile Protocol Specification documentation system. ## When This Skill Activates - Creating new documentation chapters or sections - Editing existing APS content - Reviewing documents for compliance - Managing document lifecycle transitions - Working with metadata-rich filenames ## Key Concepts ### Document States **Mutable States** (open to changes): - **Draft**: Initial creation, open for major edits - **Provisional**: Temporary acceptance, awaiting full review - **In Review**: Under formal review process **Immutable States** (locked): - **Accepted**: Approved by stakeholders - **Final**: Officially complete, archived ### Metadata-Rich Naming Pattern: `{Type}_{Version}_{State}_{Date}_{Author}.ext` Examples: - `requirements_v1.0.0_draft_2024-03-22_SC.md` - `architecture_v2.1.0_accepted_2024-04-15_Team.md` ## Templates ### New Chapter ```markdown # [Chapter Title] [Introduction explaining purpose] ## [Main Section] [Content] ## Conclusion [Key takeaways] --- ``` ### Context File ```yaml --- module-name: [Name] version: 1.0.0 description: | [Purpose and content description] related-modules: - name: [Related] path: ./path/to/module.md technologies: - Markdown - mdBook conventions: - Follow APS naming conventions - Include metadata headers --- ``` ## Best Practices 1. **Structure First**: Plan document hierarchy before writing 2. **Clear Headings**: Use descriptive section titles 3. **Cross-Reference**: Link related content 4. **Context Files**: Create for new modules 5. **Update SUMMARY.md**: Add new chapters to navigation 6. **Build Test**: Run `mdbook build` to verify ## Resources - Main SUMMARY: `specification-guide/src/SUMMARY.md` - Glossary: `specification-guide/src/appendices/glossary.md` - Templates: `specification-guide/src/appendices/templates_examples.md`

Frequently asked questions