Agent skill

Sync Specs

A skill your agent uses when code changes may have made documentation outdated, when reviewing docs for consistency, or when the user asks to sync or audit documentation.

MITAuto-check passedDevelopment

Install Sync Specs

skills CLI

$ npx skills add nexu-io/nexu --skill sync-specs -a claude-code

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

GitHub CLI

$ gh skill install nexu-io/nexu sync-specs --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/nexu-io/nexu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/localdev/sync-specs .claude/skills/sync-specs && 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 "sync-specs" agent skill from https://github.com/nexu-io/nexu/tree/main/skills/localdev/sync-specs into .claude/skills/sync-specs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-specs", 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/nexu-io/nexu/tree/main/skills/localdev/sync-specs

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 nexu-io/nexu --skill sync-specs -a codex

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

GitHub CLI

$ gh skill install nexu-io/nexu sync-specs --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/nexu.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/localdev/sync-specs .agents/skills/sync-specs && 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 "sync-specs" agent skill from https://github.com/nexu-io/nexu/tree/main/skills/localdev/sync-specs into .agents/skills/sync-specs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-specs", 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 nexu-io/nexu --skill sync-specs -a cursor

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

GitHub CLI

$ gh skill install nexu-io/nexu sync-specs --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/nexu.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/localdev/sync-specs .cursor/skills/sync-specs && 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 "sync-specs" agent skill from https://github.com/nexu-io/nexu/tree/main/skills/localdev/sync-specs into .cursor/skills/sync-specs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-specs", 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/nexu-io/nexu.git --path skills/localdev/sync-specs

--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 nexu-io/nexu --skill sync-specs -a gemini-cli

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

GitHub CLI

$ gh skill install nexu-io/nexu sync-specs --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/nexu-io/nexu.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/localdev/sync-specs .gemini/skills/sync-specs && 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 "sync-specs" agent skill from https://github.com/nexu-io/nexu/tree/main/skills/localdev/sync-specs into .gemini/skills/sync-specs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-specs", 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 nexu-io/nexu sync-specs

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 nexu-io/nexu --skill sync-specs -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/nexu.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/localdev/sync-specs .github/skills/sync-specs && 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 "sync-specs" agent skill from https://github.com/nexu-io/nexu/tree/main/skills/localdev/sync-specs into .github/skills/sync-specs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-specs", 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 nexu-io/nexu --skill sync-specs -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 nexu-io/nexu sync-specs --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/nexu-io/nexu.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/localdev/sync-specs .opencode/skills/sync-specs && 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 "sync-specs" agent skill from https://github.com/nexu-io/nexu/tree/main/skills/localdev/sync-specs into .opencode/skills/sync-specs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-specs", 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: sync-specs
GitHub stars: 3.3k
Token cost: ~1.2k tokens
SKILL.md length: 468 words
Files: 2
Skills in repo: 10
Repo updated: Apr 26, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when code changes may have made documentation outdated, when reviewing docs for consistency, or when the user asks to sync or audit documentation.

Works in 9 steps: CLAUDE.md Commands section <-> AGENTS.md… → CLAUDE.md Documentation Map paths <->… → CLAUDE.md Hard Rules <-> AGENTS.md Hard… → …
Code changes may have made documentation outdated
SKILL.md covers Mode, Delta Mode Baseline, Impact Mapping and Cross-Reference Pairs, plus 3 more sections
Runs Shell scripts from its folder; calls git

What it does

Sync Specs is an agent skill from nexu-io/nexu. Use when code changes may have made documentation outdated, when reviewing docs for consistency, or when the user asks to sync or audit documentation.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `check-doc-drift.sh`).

It sits in Development, covering Messaging and chat bots. It works with WeChat, Feishu (Lark) and Slack. The repository describes itself as: The simplest desktop client for OpenClaw 🦞 — bridge your Agent to WeChat, Feishu, Slack & Discord in one click. Works with Claude Code, Codex & any LLM. BYOK, Oauth… The licence is MIT.

When your agent uses it

Code changes may have made documentation outdated
Reviewing docs for consistency
The user asks to sync
Audit documentation

Example prompts

“/sync-specs”

Requirements

A Bash shell

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

CLAUDE.md Commands section <-> AGENTS.md Commands section (same entries)
CLAUDE.md Documentation Map paths <-> actual files on disk
CLAUDE.md Hard Rules <-> AGENTS.md Hard rules
ARCHITECTURE.md monorepo layout <-> actual apps/ + packages/ dirs
specs/DESIGN.md table <-> actual specs/design-specs/ + specs/designs/ contents
specs/design-specs/index.md table <-> actual design files
specs/product-specs/index.md table <-> actual specs/product-specs/*.md files
specs/PLANS.md table <-> specs/exec-plans/{active,completed}/ contents
specs/FRONTEND.md Pages table <-> apps/web/src/app.tsx routes

What it can do on your machine

Read from SKILL.md and the folder at commit dadfb1c. 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
Ships script files (Shell), which the agent can run.
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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

Sync Specs loads about 1.2k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 468 words of instructions outside code blocks.

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

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 nexu-io/nexu at commit dadfb1c, republished under its MIT licence (© nexu-io). 468 words, ~1,161 tokens.

Download SKILL.mdSave it as .claude/skills/sync-specs/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: sync-specs
description: Use when code changes may have made documentation outdated, when reviewing docs for consistency, or when the user asks to sync or audit documentation.

Documentation Sync

Review code changes and update project documentation for consistency.

Mode

Mode	How to activate	Behavior
`delta` (default)	No argument, or say "delta"	Diff against merge-base with `origin/main` + working tree changes
`full`	Say "full audit" or "full sync"	Complete audit of all docs against current codebase
Scope keyword	Say the keyword (e.g. "db", "api")	Targeted check (see Scope Filters below)

Delta Mode Baseline

Identify changed files using merge-base (not a fixed commit count):

bash

# Branch changes since diverging from main
git diff --name-only $(git merge-base HEAD origin/main)...HEAD
# Plus staged + unstaged
git diff --name-only --cached
git diff --name-only

Combine the results into a single list of changed files. Then use the Impact Mapping to identify which docs may need updates.

Impact Mapping

Map changed areas to the docs they affect:

Changed area	Affected docs
`apps/controller/src/routes/`	`specs/references/api-patterns.md`, `ARCHITECTURE.md`, `specs/product-specs/*.md` (if route is user-facing)
`apps/web/src/pages/` or `apps/web/src/app.tsx`	`specs/FRONTEND.md`
`apps/landing/`	`ARCHITECTURE.md` (Monorepo layout)
`apps/controller/src/runtime/`	`ARCHITECTURE.md`, `specs/RELIABILITY.md`
`packages/shared/src/schemas/`	`ARCHITECTURE.md` (Type safety)
`package.json` scripts	`CLAUDE.md` + `AGENTS.md` Commands sections
New apps/packages dirs	`ARCHITECTURE.md` (Monorepo layout)
Config generator	`specs/references/openclaw-config-schema.md`, `specs/openclaw-config-reference.md`
Auth changes	`specs/SECURITY.md`
New/moved doc files	`CLAUDE.md` Doc Map, `AGENTS.md` Where to look, relevant index files

Cross-Reference Pairs

Always verify consistency between these paired docs:

CLAUDE.md Commands section <-> AGENTS.md Commands section (same entries)
CLAUDE.md Documentation Map paths <-> actual files on disk
CLAUDE.md Hard Rules <-> AGENTS.md Hard rules
ARCHITECTURE.md monorepo layout <-> actual apps/ + packages/ dirs
specs/DESIGN.md table <-> actual specs/design-specs/ + specs/designs/ contents
specs/design-specs/index.md table <-> actual design files
specs/product-specs/index.md table <-> actual specs/product-specs/*.md files
specs/PLANS.md table <-> specs/exec-plans/{active,completed}/ contents
specs/FRONTEND.md Pages table <-> apps/web/src/app.tsx routes

Scope Filters

When the user specifies a scope keyword, limit the check to that area:

Keyword	What it checks
`db`	Schema source vs `specs/generated/db-schema.md`
`api`	Route files vs `specs/references/api-patterns.md`
`frontend`	`apps/web/` vs `specs/FRONTEND.md`
`commands`	`package.json` scripts vs `CLAUDE.md`/`AGENTS.md` Commands sections
`architecture`	All `apps/` + `packages/` vs `ARCHITECTURE.md` layout
`security`	Auth/crypto code vs `specs/SECURITY.md`
`links`	Verify all doc map paths and index references resolve to existing files
`guides`	`specs/guides/**` internal cross-references
`designs`	`specs/designs/` + `specs/design-specs/` vs index files
`exec-plans`	`specs/exec-plans/**` vs `specs/PLANS.md`
`product-specs`	`specs/product-specs/**` vs index + `specs/PRODUCT_SENSE.md`

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

Rules

Never remove forward-looking documentation — ask if uncertain whether content is aspirational or stale.
Preserve original language (English/Chinese) and writing style of existing docs.
For backend API updates, treat apps/controller as the source of truth; do not reference removed legacy package paths.
Always verify CLAUDE.md <-> AGENTS.md consistency after any update to either file.
Do NOT auto-commit — present the diff summary and let the user decide when to commit.

Workflow

Determine mode from user request (default: delta).
If delta mode: run the git diff commands above, collect changed files.
Map changed files to affected docs using the Impact Mapping.
Read each affected doc and compare against current code.
Check all Cross-Reference Pairs for consistency.
Present findings: what's outdated, what's missing, what's inconsistent.
Apply fixes with user approval.
After fixes, re-verify Cross-Reference Pairs touched by changes.

Files

SKILL.md and 1 other file in skills/localdev/sync-specs of nexu-io/nexu.

SKILL.md
check-doc-drift.sh

Open the folder on GitHubat commit dadfb1c

Compare with similar skills

Sync Specs 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.

Sync Specs compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sync Specs this skillnexu-io/nexu	3.3k	—	~1.2k	Automated safety check: Pass	MIT	5 mo ago
Use Avibeavibe-bot/avibe	620	—	~2.5k	Automated safety check: Pass	MIT	today
Claude To Imop7418/Claude-to-IM-skill	2.9k	—	~3.4k	Automated safety check: Notes	MIT	6 mo ago
Content CollectorvigorX777/content-collector-skill	240	—	~2k	Automated safety check: Pass	None	6 mo ago
Yichen Wechat Mp Batch Exportermcncarl/yichen-skills	4.3k	—	~1.5k	Automated safety check: Pass	Custom licence	4 days ago
Web To Markdownrookie-ricardo/erduo-skills	935	—	~894	Automated safety check: Pass	MIT	2 mo ago

Similar skills

Use Avibe
avibe-bot/avibe
Safely inspect and modify local Avibe configuration, routing, runtime settings, watches, scheduled tasks, Avibe Cloud remote access, and operational state.
620 GitHub stars~2.5k tokensUpdated today
Productivity & AutomationAuto-check passed
Claude To Im
op7418/Claude-to-IM-skill
Bridge THIS Claude Code or Codex session to Telegram, Discord, Feishu/Lark, QQ, or WeChat so the user can chat with Claude from their phone.
2.9k GitHub stars~3.4k tokensUpdated 6 mo ago
Productivity & AutomationAuto-check: notes
Content Collector
vigorX777/content-collector-skill
Collect social media content (X/Twitter, WeChat, Jike, Reddit, etc.) into Feishu bitable.
240 GitHub stars~2k tokensUpdated 6 mo ago
Productivity & AutomationAuto-check passed
Yichen Wechat Mp Batch Exporter
mcncarl/yichen-skills
批量下载微信公众号文章正文、历史文章列表、原创文章筛选、历史计数口径、阅读量、点赞/转发等指标、评论和评论回复。Use when the user asks to batch fetch mp.weixin.qq.com articles, export WeChat public-account history, distinguish publish groups vs expanded…
4.3k GitHub stars~1.5k tokensUpdated 4 days ago
Productivity & AutomationAuto-check passed
Web To Markdown
rookie-ricardo/erduo-skills
Convert a web URL into cleaned Markdown with deterministic routing.
935 GitHub stars~894 tokensUpdated 2 mo ago
Productivity & AutomationAuto-check passed
Feedgrab
iBigQiang/feedgrab
Universal content grabber — fetch any URL and return structured Markdown.
614 GitHub stars~2k tokensUpdated 1 mo ago
Media & CreativeAuto-check passed

More from nexu-io/nexu

All 10 skills in this repo

Libtv Video
nexu-io/nexu
Seedance 2.0 video & image generation via LibTV Gateway - AI text-to-video, image-to-video, video continuation, style transfer, and text-to-image using Seedance 2.0 model.
3.3k GitHub stars~3.5k tokensUpdated 5 mo ago
Auto-check passed
Nano Banana
nexu-io/nexu
Generate or edit images via Nano Banana image models. An agent skill from nexu-io/nexu.
3.3k GitHub stars~757 tokensUpdated 5 mo ago
Auto-check passed
Nano Banana One Shop
nexu-io/nexu
All-in-one image generation with Gemini models. An agent skill from nexu-io/nexu.
3.3k GitHub stars~870 tokensUpdated 5 mo ago
Auto-check passed
Qiaomu Mondo Poster Design
nexu-io/nexu
一句话生成大师级海报、书籍封面、专辑封面和各类设计作品。无需懂PS、配色或艺术史，AI自动选择最佳风格（基于33+位传奇设计师）。支持多平台多比例：公众号封面(21:9)、小红书配图(3:4)、文章配图(16:9)、书籍封面(9:16)、专辑封面(1:1)、电影海报(9:16)。包含AI提示词优化、风格对比、图生图转换功能。触发词："Mondo风格"、"书籍封面设计"、"专辑封面"、"海报设计"…
3.3k GitHub starsUsed in 1 repo~4.1k tokens
Auto-check passed
Static Deploy
nexu-io/nexu
Deploy static pages to nexu.space. An agent skill from nexu-io/nexu.
3.3k GitHub stars~989 tokensUpdated 5 mo ago
Auto-check passed
Nexu E2E Test
nexu-io/nexu
A skill your agent uses when verifying OpenClaw gateway fixes end-to-end, testing skill loading after restart, or running integration tests against the local Nexu+OpenClaw stack.
3.3k GitHub stars~1.7k tokensUpdated 5 mo ago
Auto-check passed

Works with

Questions about Sync Specs

What does Sync Specs do?

A skill your agent uses when code changes may have made documentation outdated, when reviewing docs for consistency, or when the user asks to sync or audit documentation. Sync Specs is an agent skill from nexu-io/nexu. Use when code changes may have made documentation outdated, when reviewing docs for consistency, or when the user asks to sync or audit documentation.

When should I use Sync Specs?

Sync Specs fits situations like: code changes may have made documentation outdated; reviewing docs for consistency; the user asks to sync; audit documentation.

How do I install Sync Specs in Claude Code?

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

How do I install Sync Specs in Codex?

Run `npx skills add nexu-io/nexu --skill sync-specs -a codex`. Or copy the skill folder (skills/localdev/sync-specs in nexu-io/nexu) into .agents/skills/sync-specs in your project. Codex loads it when a task matches its description.

Can I use Sync Specs 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 nexu-io/nexu --skill sync-specs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sync-specs, .gemini/skills/sync-specs, .github/skills/sync-specs and .opencode/skills/sync-specs in your project.

What does Sync Specs need to run?

Going by SKILL.md and its folder, Sync Specs needs a shell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell.

Does Sync Specs access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Sync Specs 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 Sync Specs use?

Sync Specs 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 Sync Specs use?

About 1.2k tokens (SKILL.md is roughly 4.6k 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 Sync Specs?

Skills that share tags, products or a category with Sync Specs: Use Avibe (avibe-bot/avibe, 620 stars), Claude To Im (op7418/Claude-to-IM-skill, 2.9k stars), Content Collector (vigorX777/content-collector-skill, 240 stars) and Yichen Wechat Mp Batch Exporter (mcncarl/yichen-skills, 4.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sync Specs?

nexu-io (a GitHub organization) maintains it in nexu-io/nexu, which has 3,281 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on April 26, 2026.

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

Install Sync Specs

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Documentation Sync

Mode

Delta Mode Baseline

Impact Mapping

Cross-Reference Pairs

Scope Filters

Rules

Workflow

Files

Compare with similar skills

Similar skills

More from nexu-io/nexu

Related

Questions about Sync Specs