Install the "skill-edit-validation" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/skill-edit-validation into .claude/skills/skill-edit-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-edit-validation", 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.
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 ZaxbyHub/opencode-swarm --skill skill-edit-validation -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "skill-edit-validation" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/skill-edit-validation into .agents/skills/skill-edit-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-edit-validation", 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 ZaxbyHub/opencode-swarm --skill skill-edit-validation -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "skill-edit-validation" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/skill-edit-validation into .cursor/skills/skill-edit-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-edit-validation", 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.
--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 ZaxbyHub/opencode-swarm --skill skill-edit-validation -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "skill-edit-validation" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/skill-edit-validation into .gemini/skills/skill-edit-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-edit-validation", 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.
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 ZaxbyHub/opencode-swarm --skill skill-edit-validation -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "skill-edit-validation" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/skill-edit-validation into .github/skills/skill-edit-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-edit-validation", 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 ZaxbyHub/opencode-swarm --skill skill-edit-validation -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "skill-edit-validation" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/skill-edit-validation into .opencode/skills/skill-edit-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-edit-validation", 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
skill-edit-validation
GitHub stars
493
Token cost
~532 tokens
SKILL.md length
248 words
Files
1
Skills in repo
91
Repo updated
First seen
Licence
MIT
At a glance
Content-assertion sweep after editing SKILL.md files. An agent skill from ZaxbyHub/opencode-swarm.
Works in 6 steps: Extract changed phrases: Identify old… → Targeted sweep: For each OLD phrase,… → For each match: Read the assertion… → …
Tasks that involve Failing and flaky tests
SKILL.md covers Trigger, Protocol, Constraint and Root cause
Calls rg
What it does
Skill Edit Validation is an agent skill from ZaxbyHub/opencode-swarm. Content-assertion sweep after editing SKILL.md files. Triggered when a task changes skill or prompt content that tests assert against. Prevents stale-assertion CI failures.
Its SKILL.md is about 530 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 Agent Workflows, covering Failing and flaky tests and Skill authoring. The repository describes itself as: Architect-centric agentic swarm plugin for OpenCode. Hub-and-spoke orchestration with SME consultation, code generation, and QA review. The licence is MIT.
When your agent uses it
Tasks that involve Failing and flaky tests
Tasks that involve Skill authoring
Example prompts
“/skill-edit-validation”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
1Extract changed phrases: Identify old wording vs new wording (e.g., "spec.md does NOT exist" changed to "NO effective spec exists")
2Targeted sweep: For each OLD phrase, grep test files
3For each match: Read the assertion context (surrounding 10 lines). Verify
4Prefer the semantic registry: If the assertion is checking skill behavior
5Update stale assertions in the same changeset. Do NOT defer to CI.
6Preserve behavioral intent: When updating, preserve what the assertion TESTS (e.g., "the plan skill has a spec-absent branch"), not just…
What it can do on your machine
Read from SKILL.md and the folder at commit eee4534. 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:
rg
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Skill Edit Validation loads about 532 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 248 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~49
When it runs· the whole SKILL.md, loaded when a task matches
~532
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.
Download SKILL.mdSave it as .claude/skills/skill-edit-validation/SKILL.md (or your agent's skills folder).
name
skill-edit-validation
description
Content-assertion sweep after editing SKILL.md files. Triggered when a task changes skill or prompt content that tests assert against. Prevents stale-assertion CI failures.
audience
swarm-plugin
Skill Edit Validation
Trigger
After editing ANY .md file under .opencode/skills/, .claude/skills/, or .agents/skills/ that changes content wording (not just whitespace/formatting).
Protocol
Extract changed phrases: Identify old wording vs new wording (e.g., "spec.md does NOT exist" changed to "NO effective spec exists")
Targeted sweep: For each OLD phrase, grep test files:
rg "<old-phrase>" tests/ src/ --type ts -l
Focus on: *-audit*, *-security*, *-spec-gate*, *skill-mirror*, *soft-spec*, *prompt*, *workflow*
For each match: Read the assertion context (surrounding 10 lines). Verify:
Does the assertion still hold against the new content?
Is it checking a substring containing the old phrase?
Is it checking for the ABSENCE of a word the new wording introduces? (e.g., not.toContain('skip') catches "this check is skipped")
Prefer the semantic registry: If the assertion is checking skill behavior
rather than an exact contract string, move it behind
tests/helpers/skill-content-registry.ts (or add a concept there) and assert
the named concept from the test.
Update stale assertions in the same changeset. Do NOT defer to CI.
Preserve behavioral intent: When updating, preserve what the assertion TESTS (e.g., "the plan skill has a spec-absent branch"), not just the string match.
Constraint
Do NOT rubber-stamp brittle assertions. If an assertion tests implementation detail rather than behavioral intent, flag it for refactoring to a semantic check.
Root cause
Skill-content tests should assert named semantic concepts where possible. The
registry in tests/helpers/skill-content-registry.ts is the preferred safety
net for recurring skill wording checks; use the manual grep sweep for exact
contract strings and any tests not yet migrated.
Skill Edit Validation 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 Edit Validation compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Skill Edit Validation this skillZaxbyHub/opencode-swarm
A skill your agent uses when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing…
A skill your agent uses when asked to add an Archestra PR to the merge queue, monitor it through merge, or diagnose and repair merge-group CI failures.
Runs an evidence-gated, quote-grounded audit of a codebase for security, QA, accessibility, performance and more, and writes a verified report without changing source files.
Drives a bug report from validation and root-cause tracing through a critic-reviewed plan, an approved minimal fix and a PR-ready closure, never merging without recorded human approval.
Codex adapter for opencode-swarm that governs commits, pushes, draft PRs, PR body updates and CI closeout, deferring to the repo's canonical commit-pr protocol.
Ingests existing pull request feedback such as review comments and CI failures, verifies each claim, fixes confirmed issues and reports closure status for every item.
Content-assertion sweep after editing SKILL.md files. An agent skill from ZaxbyHub/opencode-swarm. Skill Edit Validation is an agent skill from ZaxbyHub/opencode-swarm.md files.
When should I use Skill Edit Validation?
Skill Edit Validation fits situations like: tasks that involve Failing and flaky tests; tasks that involve Skill authoring.
How do I install Skill Edit Validation in Claude Code?
Run `npx skills add ZaxbyHub/opencode-swarm --skill skill-edit-validation -a claude-code`. Or copy the skill folder (.opencode/skills/skill-edit-validation in ZaxbyHub/opencode-swarm) into .claude/skills/skill-edit-validation in your project. Claude Code loads it when a task matches its description.
How do I install Skill Edit Validation in Codex?
Run `npx skills add ZaxbyHub/opencode-swarm --skill skill-edit-validation -a codex`. Or copy the skill folder (.opencode/skills/skill-edit-validation in ZaxbyHub/opencode-swarm) into .agents/skills/skill-edit-validation in your project. Codex loads it when a task matches its description.
Can I use Skill Edit Validation 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 ZaxbyHub/opencode-swarm --skill skill-edit-validation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-edit-validation, .gemini/skills/skill-edit-validation, .github/skills/skill-edit-validation and .opencode/skills/skill-edit-validation in your project.
What does Skill Edit Validation need to run?
Going by SKILL.md and its folder, Skill Edit Validation needs the command-line tools its instructions call (rg).
Does Skill Edit Validation 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 Skill Edit Validation 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 Skill Edit Validation use?
Skill Edit Validation 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 Skill Edit Validation use?
About 532 tokens (SKILL.md is roughly 2.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 Skill Edit Validation?
Skills that share tags, products or a category with Skill Edit Validation: Aliyun Skill Creator (cinience/alicloud-skills, 397 stars), Waza Skill Evaluator (microsoft/waza, 1.4k stars), Waza Interactive (microsoft/waza, 1.4k stars) and Writing Skills (ed3dai/ed3d-plugins, 250 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skill Edit Validation?
ZaxbyHub (a GitHub organization) maintains it in ZaxbyHub/opencode-swarm, which has 493 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 9, 2026.
Source: ZaxbyHub/opencode-swarm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
