How do I install the Sync Docs Structure skill?

Run npx skillmds@latest add majiayu000/sync-docs-structure 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 Sync Docs Structure safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sync Docs Structure?

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

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

Who published Sync Docs Structure?

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

Sync Docs Structure by majiayu000 — Agent Skill

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

Sync Docs Structure

Automatically sync the documentation structure from docs/content/{en,uk}/ to CLAUDE.md when changes are detected in the docs directory. This skill should be triggered when documentation files are added, removed, or reorganized, or when explicitly requested by the user or agents.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Sync Documentation Structure

Overview

Keep CLAUDE.md synchronized with the current documentation structure by scanning docs/content/{en,uk}/ and updating the Documentation section with the latest file tree and titles.

When to Use

Trigger this skill when:

New documentation files or directories are added to docs/
Documentation structure is reorganized or renamed
User explicitly requests documentation sync
After significant changes to docs/ are detected

Workflow

1. Scan Documentation Structure

Run the bundled scanner script to extract the current docs structure:

uv run .claude/skills/sync-docs-structure/scripts/scan_docs.py

The script:

Scans docs/content/en/ and docs/content/uk/ directories
Builds a tree structure showing files and folders
Extracts titles from markdown frontmatter when available
Outputs clean markdown-formatted tree

2. Update CLAUDE.md

Locate or create the ## Documentation section in CLAUDE.md (should be after ## Code Quality Standards).

Replace the entire Documentation section with:

## Documentation

**Source**: Bilingual markdown files in `docs/content/{en,uk}/`

[OUTPUT FROM SCAN SCRIPT]

3. Verify and Report

After updating:

Confirm what sections were found (en, uk)
Report number of documentation files discovered
Preserve all other sections in CLAUDE.md unchanged

Example Output

After running the skill, CLAUDE.md should contain:

## Documentation

**Source**: Bilingual markdown files in `docs/content/{en,uk}/`

docs/content/ ├── en/ │ ├── api/ │ │ └── endpoints.md - API Endpoints │ └── architecture/ │ ├── overview.md - System Architecture │ └── analysis-system.md - Analysis System └── uk/ ├── api/ │ └── endpoints.md - API точки доступу └── architecture/ ├── overview.md - Архітектура системи └── analysis-system.md - Система аналізу

Notes

Keep updates lightweight - structure only, not file contents
The script extracts titles from markdown frontmatter automatically
Skip docs/site/ and other generated directories
Preserve exact formatting for consistency

---name: sync-docs-structuredescription: Automatically sync the documentation structure from docs/content/{en,uk}/ to CLAUDE.md when changes are detected in the docs directory. This skill should be triggered when documentation files are added, removed, or reorganized, or when explicitly requested by the user or agents.--- # Sync Documentation Structure ## Overview Keep CLAUDE.md synchronized with the current documentation structure by scanning `docs/content/{en,uk}/` and updating the Documentation section with the latest file tree and titles. ## When to Use Trigger this skill when: - New documentation files or directories are added to `docs/` - Documentation structure is reorganized or renamed - User explicitly requests documentation sync - After significant changes to docs/ are detected ## Workflow ### 1. Scan Documentation Structure Run the bundled scanner script to extract the current docs structure: ```bash uv run .claude/skills/sync-docs-structure/scripts/scan_docs.py ``` The script: - Scans `docs/content/en/` and `docs/content/uk/` directories - Builds a tree structure showing files and folders - Extracts titles from markdown frontmatter when available - Outputs clean markdown-formatted tree ### 2. Update CLAUDE.md Locate or create the `## Documentation` section in CLAUDE.md (should be after `## Code Quality Standards`). Replace the entire Documentation section with: ```markdown ## Documentation **Source**: Bilingual markdown files in `docs/content/{en,uk}/` ``` [OUTPUT FROM SCAN SCRIPT] ``` ``` ### 3. Verify and Report After updating: - Confirm what sections were found (en, uk) - Report number of documentation files discovered - Preserve all other sections in CLAUDE.md unchanged ## Example Output After running the skill, CLAUDE.md should contain: ```markdown ## Documentation **Source**: Bilingual markdown files in `docs/content/{en,uk}/` ``` docs/content/ ├── en/ │ ├── api/ │ │ └── endpoints.md - API Endpoints │ └── architecture/ │ ├── overview.md - System Architecture │ └── analysis-system.md - Analysis System └── uk/ ├── api/ │ └── endpoints.md - API точки доступу └── architecture/ ├── overview.md - Архітектура системи └── analysis-system.md - Система аналізу ``` ``` ## Notes - Keep updates lightweight - structure only, not file contents - The script extracts titles from markdown frontmatter automatically - Skip `docs/site/` and other generated directories - Preserve exact formatting for consistency

Frequently asked questions