JavaScript Concept Fact Checker
leonardomso/33-js-concepts
Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.
Make the v<version.0 directory of the opencrvs/documentation repo reflect what an OpenCRVS core release ships — find missing and outdated pages, draft the edits on a branch.
Install Release Docs Sync
$ npx skills add opencrvs/opencrvs-core --skill release-docs-sync -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install opencrvs/opencrvs-core release-docs-sync --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/opencrvs/opencrvs-core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release-docs-sync .claude/skills/release-docs-sync && rm -rf skills-srcUse ~/.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/
Install the "release-docs-sync" agent skill from https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/release-docs-sync into .claude/skills/release-docs-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-docs-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 install https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/release-docs-syncType 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.
$ npx skills add opencrvs/opencrvs-core --skill release-docs-sync -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install opencrvs/opencrvs-core release-docs-sync --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opencrvs/opencrvs-core.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/release-docs-sync .agents/skills/release-docs-sync && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-docs-sync" agent skill from https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/release-docs-sync into .agents/skills/release-docs-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-docs-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.
$ npx skills add opencrvs/opencrvs-core --skill release-docs-sync -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install opencrvs/opencrvs-core release-docs-sync --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opencrvs/opencrvs-core.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/release-docs-sync .cursor/skills/release-docs-sync && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-docs-sync" agent skill from https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/release-docs-sync into .cursor/skills/release-docs-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-docs-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 https://github.com/opencrvs/opencrvs-core.git --path .claude/skills/release-docs-sync--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add opencrvs/opencrvs-core --skill release-docs-sync -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install opencrvs/opencrvs-core release-docs-sync --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opencrvs/opencrvs-core.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/release-docs-sync .gemini/skills/release-docs-sync && rm -rf skills-srcUse ~/.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/
Install the "release-docs-sync" agent skill from https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/release-docs-sync into .gemini/skills/release-docs-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-docs-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.
$ gh skill install opencrvs/opencrvs-core release-docs-syncInstalls 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).
$ npx skills add opencrvs/opencrvs-core --skill release-docs-sync -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/opencrvs/opencrvs-core.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/release-docs-sync .github/skills/release-docs-sync && rm -rf skills-srcUse ~/.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/
Install the "release-docs-sync" agent skill from https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/release-docs-sync into .github/skills/release-docs-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-docs-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.
$ npx skills add opencrvs/opencrvs-core --skill release-docs-sync -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install opencrvs/opencrvs-core release-docs-sync --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opencrvs/opencrvs-core.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/release-docs-sync .opencode/skills/release-docs-sync && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-docs-sync" agent skill from https://github.com/opencrvs/opencrvs-core/tree/develop/.claude/skills/release-docs-sync into .opencode/skills/release-docs-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-docs-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
release-docs-sync- GitHub stars
- 120
- Token cost
- ~1.4k tokens
- SKILL.md length
- 679 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Make the v<version.0 directory of the opencrvs/documentation repo reflect what an OpenCRVS core release ships — find missing and outdated pages, draft the edits on a branch.
- Works in 4 steps: Set up both sides → Build the change → page worklist → Edit → …
- Tasks that involve Technical writing
- SKILL.md covers 1. Set up both sides, 2. Build the change → page…, 3. Edit and 4. Hand back
- Calls git and gh
What it does
Release Docs Sync is an agent skill from opencrvs/opencrvs-core. Make the v<version.0 directory of the opencrvs/documentation repo reflect what an OpenCRVS core release ships — find missing and outdated pages, draft the edits on a branch. Run as /release-docs-sync <version [path-to-documentation-checkout].
Its SKILL.md is about 1.4k 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 Writing & Content, covering Technical writing. The repository describes itself as: A global solution to civil registration.
When your agent uses it
- Tasks that involve Technical writing
Example prompts
- “/release-docs-sync”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Set up both sides
- Build the change → page worklist
- Edit
- Hand back
What it can do on your machine
Read from SKILL.md and the folder at commit 0090b5f. 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:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, 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
Release Docs Sync loads about 1.4k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 679 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 679 words (~1,353 tokens).
“Bring opencrvs/documentation → v.0/ in line with core . Arguments: $ARGUMENTS`.”
- name
- release-docs-sync
- argument-hint
- <version, e.g. 2.1> [path to documentation checkout]
- disable-model-invocation
- true
Files
Just SKILL.md in .claude/skills/release-docs-sync of opencrvs/opencrvs-core.
Open the folder on GitHubat commit 0090b5f
Compare with similar skills
Release Docs 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Docs Sync this skillopencrvs/opencrvs-core | 120 | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| JavaScript Concept Fact Checkerleonardomso/33-js-concepts | 67k | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| Beads Documentation Style Guidegastownhall/beads | 28k | — | ~3.2k | Automated safety check: Pass | MIT | |
| JavaScript Concept Page Workflowleonardomso/33-js-concepts | 67k | — | ~3.9k | Automated safety check: Pass | MIT | |
| JS Concept Resource Curatorleonardomso/33-js-concepts | 67k | — | ~4.9k | Automated safety check: Pass | MIT | |
| Technical Writing Standardcursor/plugins | 10k | 10 repos | ~2.4k | Automated safety check: Pass | None |
Similar skills
Beads Documentation Style Guide
gastownhall/beads
Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.
JavaScript Concept Page Workflow
leonardomso/33-js-concepts
Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.
JS Concept Resource Curator
leonardomso/33-js-concepts
Finds, vets, writes up and maintains external articles, videos and courses for JavaScript concept pages, including audits for broken and outdated links.
- Official
Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
Writing Docs
nukeop/nuclear
A skill your agent uses when writing or editing documentation in packages/docs.
More from opencrvs/opencrvs-core
Release Prep
opencrvs/opencrvs-core
Entry point for preparing an OpenCRVS core release — lists the release-prep tasks and gathers what changed in the release.
Grilling
opencrvs/opencrvs-core
Grill the user relentlessly about a plan or design. An agent skill from opencrvs/opencrvs-core.
PR Desc
opencrvs/opencrvs-core
A skill your agent uses when the user asks to write, update, or amend a GitHub PR description — e.g.
Compile Lint Check
opencrvs/opencrvs-core
Run TypeScript compilation and lint checks for an OpenCRVS package after modifying or adding files under packages/{packagename}.
Related
Categories
Questions about Release Docs Sync
What does Release Docs Sync do?
Make the v<version.0 directory of the opencrvs/documentation repo reflect what an OpenCRVS core release ships — find missing and outdated pages, draft the edits on a branch. Release Docs Sync is an agent skill from opencrvs/opencrvs-core.0 directory of the opencrvs/documentation repo reflect what an OpenCRVS core release ships — find missing and outdated pages, draft the edits on a branch.
When should I use Release Docs Sync?
Release Docs Sync fits situations like: tasks that involve Technical writing.
How do I install Release Docs Sync in Claude Code?
Run `npx skills add opencrvs/opencrvs-core --skill release-docs-sync -a claude-code`. Or copy the skill folder (.claude/skills/release-docs-sync in opencrvs/opencrvs-core) into .claude/skills/release-docs-sync in your project. Claude Code loads it when a task matches its description.
How do I install Release Docs Sync in Codex?
Run `npx skills add opencrvs/opencrvs-core --skill release-docs-sync -a codex`. Or copy the skill folder (.claude/skills/release-docs-sync in opencrvs/opencrvs-core) into .agents/skills/release-docs-sync in your project. Codex loads it when a task matches its description.
Can I use Release Docs 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 opencrvs/opencrvs-core --skill release-docs-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/release-docs-sync, .gemini/skills/release-docs-sync, .github/skills/release-docs-sync and .opencode/skills/release-docs-sync in your project.
What does Release Docs Sync need to run?
Going by SKILL.md and its folder, Release Docs Sync needs the command-line tools its instructions call (git and gh).
Does Release Docs Sync access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release Docs 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 Release Docs Sync use?
Release Docs Sync has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Release Docs Sync use?
About 1.4k tokens (SKILL.md is roughly 5.4k 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 Release Docs Sync?
Skills that share tags, products or a category with Release Docs Sync: JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars), Beads Documentation Style Guide (gastownhall/beads, 28k stars), JavaScript Concept Page Workflow (leonardomso/33-js-concepts, 67k stars) and JS Concept Resource Curator (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Docs Sync?
opencrvs (a GitHub organization) maintains it in opencrvs/opencrvs-core, which has 120 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.
Source: opencrvs/opencrvs-core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.