How do I install the Docs Structure Maintainer skill?

Run npx skillmds add majiayu000/docs-structure-maintainer 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 Docs Structure Maintainer 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 Docs Structure Maintainer?

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 Docs Structure Maintainer free to use?

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

Who published Docs Structure Maintainer?

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

Docs Structure Maintainer by majiayu000

Name: Docs Structure Maintainer
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

Documentation Structure Maintainer

Compact skill for reasoning about HuleEdu documentation layout and TASKS structure, and for invoking the right scripts to keep them compliant.

When to Use

Activate when the user:

Creates, moves, or renames documentation under documentation/ or TASKS/
Asks where a doc should live (operations vs decisions vs how-to vs tasks)
Wants to validate or migrate documentation structure
Mentions validate_docs_structure.py, migrate_docs_structure.py, task_mgmt, or doc/TASKS specs

Core Capabilities

Classify content type and map it to the correct directory:
- documentation/overview|architecture|services|operations|how-to|reference|decisions|product|research
- TASKS/ domain taxonomy: programs/, assessment/, content/, identity/, frontend/, infrastructure/, security/, integrations/, architecture/, archive/
Suggest compliant filenames and directory names (kebab-case, no spaces; id-based filenames in TASKS/)
Ensure required frontmatter for:
- Runbooks and ADRs (per documentation/DOCS_STRUCTURE_SPEC.md)
- Task and programme docs (per canonical TASKS spec)
Propose concrete commands for:
- python scripts/docs_mgmt/validate_docs_structure.py [--strict]
- python scripts/docs_mgmt/migrate_docs_structure.py ...
- python scripts/task_mgmt/new_task.py ...
- python scripts/task_mgmt/validate_front_matter.py ...
- python scripts/task_mgmt/index_tasks.py ...

Quick Workflow

Identify doc intent (architecture, runbook, ADR, how-to, product, task, programme).
Map to the correct directory using DOCS_STRUCTURE_SPEC.md and the TASKS structure spec.
Choose or normalize filename and directory name to match naming rules.
Ensure or suggest correct frontmatter for the doc type.
Recommend validation/migration commands using scripts/docs_mgmt and scripts/task_mgmt.

Reference Documentation

Detailed Workflows & Patterns: See reference.md in this directory
Real-World Usage Examples: See examples.md in this directory
Normative Rules: .claude/rules/090-documentation-standards.md

---name: docs-structure-maintainerdescription: Understand and maintain HuleEdu documentation and task documentation structure. Guides placement, naming, and validation using the canonical specs and management scripts.--- # Documentation Structure Maintainer Compact skill for reasoning about HuleEdu documentation layout and TASKS structure, and for invoking the right scripts to keep them compliant. ## When to Use Activate when the user: - Creates, moves, or renames documentation under `documentation/` or `TASKS/` - Asks where a doc should live (operations vs decisions vs how-to vs tasks) - Wants to validate or migrate documentation structure - Mentions `validate_docs_structure.py`, `migrate_docs_structure.py`, `task_mgmt`, or doc/TASKS specs ## Core Capabilities - Classify content type and map it to the correct directory: - `documentation/overview|architecture|services|operations|how-to|reference|decisions|product|research` - `TASKS/` domain taxonomy: `programs/`, `assessment/`, `content/`, `identity/`, `frontend/`, `infrastructure/`, `security/`, `integrations/`, `architecture/`, `archive/` - Suggest compliant filenames and directory names (kebab-case, no spaces; id-based filenames in `TASKS/`) - Ensure required frontmatter for: - Runbooks and ADRs (per `documentation/DOCS_STRUCTURE_SPEC.md`) - Task and programme docs (per canonical TASKS spec) - Propose concrete commands for: - `python scripts/docs_mgmt/validate_docs_structure.py [--strict]` - `python scripts/docs_mgmt/migrate_docs_structure.py ...` - `python scripts/task_mgmt/new_task.py ...` - `python scripts/task_mgmt/validate_front_matter.py ...` - `python scripts/task_mgmt/index_tasks.py ...` ## Quick Workflow 1. Identify doc intent (architecture, runbook, ADR, how-to, product, task, programme). 2. Map to the correct directory using `DOCS_STRUCTURE_SPEC.md` and the TASKS structure spec. 3. Choose or normalize filename and directory name to match naming rules. 4. Ensure or suggest correct frontmatter for the doc type. 5. Recommend validation/migration commands using `scripts/docs_mgmt` and `scripts/task_mgmt`. ## Reference Documentation - **Detailed Workflows & Patterns**: See `reference.md` in this directory - **Real-World Usage Examples**: See `examples.md` in this directory - **Normative Rules**: `.claude/rules/090-documentation-standards.md`

Frequently asked questions