Agent skill

Doc Sync

Audit and synchronize documentation across website, READMEs, and docs/.

MITAuto-check passedDevelopment

Install Doc Sync

skills CLI

$ npx skills add macalbert/envilder --skill doc-sync -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install macalbert/envilder doc-sync --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/doc-sync .claude/skills/doc-sync && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "doc-sync" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/doc-sync into .claude/skills/doc-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-sync", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/macalbert/envilder/tree/main/.github/skills/doc-sync

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add macalbert/envilder --skill doc-sync -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install macalbert/envilder doc-sync --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/doc-sync .agents/skills/doc-sync && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "doc-sync" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/doc-sync into .agents/skills/doc-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-sync", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add macalbert/envilder --skill doc-sync -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install macalbert/envilder doc-sync --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/doc-sync .cursor/skills/doc-sync && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "doc-sync" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/doc-sync into .cursor/skills/doc-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-sync", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/macalbert/envilder.git --path .github/skills/doc-sync

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add macalbert/envilder --skill doc-sync -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install macalbert/envilder doc-sync --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/doc-sync .gemini/skills/doc-sync && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "doc-sync" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/doc-sync into .gemini/skills/doc-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-sync", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install macalbert/envilder doc-sync

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add macalbert/envilder --skill doc-sync -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/doc-sync .github/skills/doc-sync && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "doc-sync" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/doc-sync into .github/skills/doc-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-sync", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add macalbert/envilder --skill doc-sync -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install macalbert/envilder doc-sync --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/doc-sync .opencode/skills/doc-sync && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "doc-sync" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/doc-sync into .opencode/skills/doc-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-sync", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: doc-sync
GitHub stars: 138
Token cost: ~1.3k tokens
SKILL.md length: 460 words
Files: 1
Skills in repo: 30
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Audit and synchronize documentation across website, READMEs, and docs/.

Works in 6 steps: Identify Scope → Extract Source of Truth → Audit Each Surface → …
Verifying docs are aligned after feature changes
SKILL.md covers When to Use, Documentation Surfaces, Procedure and Cross-Reference Matrix, plus 1 more section
Calls pnpm

What it does

Doc Sync is an agent skill from macalbert/envilder. Audit and synchronize documentation across website, READMEs, and docs/. Use when verifying docs are aligned after feature changes, SDK updates, CLI changes, or release preparation. Detects drift between website content, markdown docs, and SDK READMEs.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Technical documentation and CI/CD. It works with Astro. The repository describes itself as: One secret mapping for local dev, CI/CD, and runtime. Envilder resolves cloud secrets from your own vaults without SaaS middlemen, duplicated config, or .env drift. The licence is MIT.

When your agent uses it

Verifying docs are aligned after feature changes
Release preparation

Example prompts

“/doc-sync”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Identify Scope
Extract Source of Truth
Audit Each Surface
Report Drift
Apply Fixes
Validate

What it can do on your machine

Read from SKILL.md and the folder at commit b6a0327. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Doc Sync loads about 1.3k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 460 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~65
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from macalbert/envilder at commit b6a0327, republished under its MIT licence (© macalbert). 460 words, ~1,269 tokens.

Download SKILL.mdSave it as .claude/skills/doc-sync/SKILL.md (or your agent's skills folder).

name: doc-sync
description: Audit and synchronize documentation across website, READMEs, and docs/. Use when verifying docs are aligned after feature changes, SDK updates, CLI changes, or release preparation. Detects drift between website content, markdown docs, and SDK READMEs.
argument-hint: feature area to audit or "full" for complete audit

Doc Sync: Cross-Surface Documentation Alignment

Audit and synchronize documentation across all surfaces to prevent drift.

When to Use

After adding or changing a feature, CLI flag, or SDK capability
After updating website content (DocsContent.astro, i18n strings)
Before a release to verify all docs reflect current behavior
When a code review flags outdated documentation

Documentation Surfaces

Surface	Location	Purpose
Website docs	`src/website/src/components/DocsContent.astro`	User-facing docs page with code examples
Website i18n	`src/website/src/i18n/{en,ca,es}.ts`	Translated strings for website
Root README	`README.md`	Project overview, install, quick start
GHA README	`github-action/README.md`	GitHub Action usage and inputs
CLI docs	`docs/pull-command.md`, `docs/push-command.md`	CLI command reference
GHA docs	`docs/github-action.md`	GitHub Action detailed docs
SDK READMEs	`src/sdks/{dotnet,python,typescript}/README.md`	SDK-specific install and usage
SDK examples	`examples/sdk/{dotnet,python}/README.md`	Example code with explanations
Changelogs	`docs/changelogs/{cli,gha,sdk-*}.md`	Per-component changelogs
ROADMAP	`ROADMAP.md`	Feature status tracking

Procedure

1. Identify Scope

Determine which feature area to audit:

CLI: root README, docs/pull-command.md, docs/push-command.md, website DocsContent
GHA: github-action/README.md, docs/github-action.md, website DocsContent
SDK (per runtime): src/sdks/{runtime}/README.md, examples/sdk/{runtime}/, website DocsContent + Sdks.astro, i18n strings
Full: all surfaces

2. Extract Source of Truth

For each feature area, identify the authoritative source:

Area	Source of Truth
CLI flags/options	`src/envilder/apps/cli/entry/Cli.ts`
GHA inputs	`github-action/action.yml`
SDK public API	SDK source code (`src/sdks/{runtime}/`)
Providers	`src/envilder/core/infrastructure/`
Map-file format	`envilder.json` (example) + copilot-instructions

3. Audit Each Surface

For each documentation surface, check:

Code examples compile/run: verify syntax matches current API
CLI flags match: documented flags exist in Cli.ts
GHA inputs match: documented inputs exist in action.yml
SDK methods match: documented methods exist in source
Install commands correct: package names, versions, registries
Provider names consistent: aws/azure naming across all docs
Links not broken: internal cross-references resolve
i18n complete: all 3 locales (en, ca, es) have matching keys

Show full SKILL.md (188 more words)Show less

4. Report Drift

Present findings in a structured table:

text

## Documentation Drift Report

| Surface | File | Issue | Severity |
|---------|------|-------|----------|
| Website | DocsContent.astro | Missing --profile flag in CLI section | High |
| SDK README | src/sdks/python/README.md | load() example uses old API | High |
| Root README | README.md | Version badge outdated | Low |

## Alignment Actions

1. {file}: {what to update}
2. {file}: {what to update}

5. Apply Fixes

For each drift item:

Update the documentation surface
If i18n strings changed, update all 3 locales
Verify the fix against the source of truth

6. Validate

Run pnpm lint to check for formatting issues
For website changes, verify the build: check i18n key consistency

Cross-Reference Matrix

Use this matrix to ensure consistency when updating a feature:

When you change...	Also update...
CLI flag in `Cli.ts`	`docs/pull-command.md` or `docs/push-command.md`, root README, DocsContent, i18n
GHA input in `action.yml`	`github-action/README.md`, `docs/github-action.md`, website DocsContent, i18n
SDK public API	SDK README, examples README, website DocsContent + Sdks.astro, i18n
New SDK added	Run full `sdk-release-checklist` skill (version badge, changelog, i18n, docs)
SDK version bump	Bump canonical source file; changelog entry; website picks up version at build time
New provider	All provider listings: root README, website Providers.astro, DocsContent, SDK READMEs
Map-file format	Root README, all SDK READMEs, website DocsContent
ROADMAP status	`ROADMAP.md`, website Roadmap.astro

Constraints

Never invent features not present in code
Verify claims against source code before writing
Preserve existing document structure and tone
Keep code examples minimal and runnable

Files

Just SKILL.md in .github/skills/doc-sync of macalbert/envilder.

Open the folder on GitHubat commit b6a0327

Compare with similar skills

Doc Sync next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Doc Sync compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Doc Sync this skillmacalbert/envilder	138	—	~1.3k	Automated safety check: Pass	MIT	2 days ago
Benchmark Readme Syncrstackjs/build-tools-performance	115	—	~1.6k	Automated safety check: Pass	MIT	yesterday
Posting Review Summarybitwarden/ai-plugins	154	—	~2.3k	Automated safety check: Pass	Custom licence	today
Writing Commentswithastro/astro	63k	—	~2.7k	Automated safety check: Pass	Custom licence	today
Ccb GitHubSeemSeam/claude_codex_bridge	3.5k	—	~4.9k	Automated safety check: Pass	Custom licence	yesterday
Star History Chartdavila7/claude-code-templates	32k	—	~1.1k	Automated safety check: Pass	MIT	today

Similar skills

Benchmark Readme Sync
rstackjs/build-tools-performance
Refresh README benchmark results from a successful GitHub Actions Benchmark run, preserving data provenance and separate development, build, and memory tables.
115 GitHub stars~1.6k tokensUpdated yesterday
DevelopmentAuto-check passed
Posting Review Summary
bitwarden/ai-plugins
Official
A skill your agent uses when posting the final summary comment, including its No Verdict form when nothing could be reviewed and no inline comments exist.
154 GitHub stars~2.3k tokensUpdated today
DevelopmentAuto-check passed
Writing Comments
withastro/astro
Official
How to write JSDoc (/ /) and inline (//) comments in the Astro codebase, for contributors reading the source — not end users.
63k GitHub stars~2.7k tokensUpdated today
DevelopmentAuto-check passed
Ccb GitHub
SeemSeam/claude_codex_bridge
Maintain this CCB project's GitHub-facing release and npm publication surface.
3.5k GitHub stars~4.9k tokensUpdated yesterday
DevelopmentAuto-check passed
Star History Chart
davila7/claude-code-templates
Add a self-hosted "Stargazers over time" chart to any GitHub repo's README.
32k GitHub stars~1.1k tokensUpdated today
DevOps & CloudAuto-check passed
Nemo Rl Docs
NVIDIA/skills
Official
Documentation conventions for NeMo-RL. An agent skill from NVIDIA/skills.
3.5k GitHub stars~357 tokensUpdated today
DevelopmentAuto-check passed

Questions about Doc Sync

What does Doc Sync do?

Audit and synchronize documentation across website, READMEs, and docs/. Doc Sync is an agent skill from macalbert/envilder. Audit and synchronize documentation across website, READMEs, and docs/.

When should I use Doc Sync?

Doc Sync fits situations like: verifying docs are aligned after feature changes; release preparation.

How do I install Doc Sync in Claude Code?

Run `npx skills add macalbert/envilder --skill doc-sync -a claude-code`. Or copy the skill folder (.github/skills/doc-sync in macalbert/envilder) into .claude/skills/doc-sync in your project. Claude Code loads it when a task matches its description.

How do I install Doc Sync in Codex?

Run `npx skills add macalbert/envilder --skill doc-sync -a codex`. Or copy the skill folder (.github/skills/doc-sync in macalbert/envilder) into .agents/skills/doc-sync in your project. Codex loads it when a task matches its description.

Can I use Doc Sync in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add macalbert/envilder --skill doc-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doc-sync, .gemini/skills/doc-sync, .github/skills/doc-sync and .opencode/skills/doc-sync in your project.

What does Doc Sync need to run?

Going by SKILL.md and its folder, Doc Sync needs the command-line tools its instructions call (pnpm).

Does Doc Sync access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Doc Sync safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Doc Sync use?

Doc Sync is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Doc Sync use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Doc Sync?

Skills that share tags, products or a category with Doc Sync: Benchmark Readme Sync (rstackjs/build-tools-performance, 115 stars), Posting Review Summary (bitwarden/ai-plugins, 154 stars), Writing Comments (withastro/astro, 63k stars) and Ccb GitHub (SeemSeam/claude_codex_bridge, 3.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Doc Sync?

macalbert (a GitHub user) maintains it in macalbert/envilder, which has 138 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 5, 2026.

Source: macalbert/envilder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Doc Sync

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Doc Sync: Cross-Surface Documentation Alignment

When to Use

Documentation Surfaces

Procedure

1. Identify Scope

2. Extract Source of Truth

3. Audit Each Surface

4. Report Drift

5. Apply Fixes

6. Validate

Cross-Reference Matrix

Constraints

Files

Compare with similar skills

Similar skills

More from macalbert/envilder

Related

Questions about Doc Sync