A skill your agent uses when validating that the Spectre plugin itself still works after ANY change to this repo — skills, prompts, agents, hooks, the CLI, the Codex mirror, or a release.
$ npx skills add joenandez/spectre --skill verify-spectre -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install joenandez/spectre verify-spectre --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/joenandez/spectre.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/verify-spectre .claude/skills/verify-spectre && 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 "verify-spectre" agent skill from https://github.com/joenandez/spectre/tree/main/.agents/skills/verify-spectre into .claude/skills/verify-spectre/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-spectre", 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/joenandez/spectre/tree/main/.agents/skills/verify-spectreType 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 joenandez/spectre --skill verify-spectre -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install joenandez/spectre verify-spectre --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/joenandez/spectre.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/verify-spectre .agents/skills/verify-spectre && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify-spectre" agent skill from https://github.com/joenandez/spectre/tree/main/.agents/skills/verify-spectre into .agents/skills/verify-spectre/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-spectre", 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 joenandez/spectre --skill verify-spectre -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install joenandez/spectre verify-spectre --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/joenandez/spectre.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/verify-spectre .cursor/skills/verify-spectre && 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 "verify-spectre" agent skill from https://github.com/joenandez/spectre/tree/main/.agents/skills/verify-spectre into .cursor/skills/verify-spectre/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-spectre", 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/joenandez/spectre.git --path .agents/skills/verify-spectre--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 joenandez/spectre --skill verify-spectre -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install joenandez/spectre verify-spectre --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/joenandez/spectre.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/verify-spectre .gemini/skills/verify-spectre && 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 "verify-spectre" agent skill from https://github.com/joenandez/spectre/tree/main/.agents/skills/verify-spectre into .gemini/skills/verify-spectre/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-spectre", 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 joenandez/spectre verify-spectreInstalls 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 joenandez/spectre --skill verify-spectre -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/joenandez/spectre.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/verify-spectre .github/skills/verify-spectre && 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 "verify-spectre" agent skill from https://github.com/joenandez/spectre/tree/main/.agents/skills/verify-spectre into .github/skills/verify-spectre/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-spectre", 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 joenandez/spectre --skill verify-spectre -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install joenandez/spectre verify-spectre --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/joenandez/spectre.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/verify-spectre .opencode/skills/verify-spectre && 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 "verify-spectre" agent skill from https://github.com/joenandez/spectre/tree/main/.agents/skills/verify-spectre into .opencode/skills/verify-spectre/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-spectre", 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.
verify-spectreA skill your agent uses when validating that the Spectre plugin itself still works after ANY change to this repo — skills, prompts, agents, hooks, the CLI, the Codex mirror, or a release.
Verify Spectre is an agent skill from joenandez/spectre. Use when validating that the Spectre plugin itself still works after ANY change to this repo — skills, prompts, agents, hooks, the CLI, the Codex mirror, or a release. Runs the full gate suite (structure, tests, Codex translation, real-CLI behavior, release readiness) and reports PASS/FAIL per gate. Trigger on: verify, validate, does this still work, check the plugin, pre-commit check, pre-release check, did I break anything, is the Codex mirror stale, ready to publish. Do NOT trigger for validating a user's own…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files.
It sits in Product & Project Management, covering Feature launches and release readiness and Translation. The repository describes itself as: Spectre is a battle-tested 6 stage agentic engineering workflow for building complex, production-ready features. You stay in the loop for the decisions that matter. Your agents…. The licence is MIT.
Read from SKILL.md and the folder at commit 931c9e8. It shows what the files ask for, not the result of running them.
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.
Ships 6 files in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
nodenpmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Verify Spectre loads about 1.5k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 145 tokens; SKILL.md has 708 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.
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); the scripts in this folder are not scanned.
The full file from joenandez/spectre at commit 931c9e8, republished under its MIT licence (© joenandez). 708 words, ~1,523 tokens.
.claude/skills/verify-spectre/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.The gate suite for the Spectre plugin itself. Run it after any change to skills, agents, hooks, src/lib/, or the Codex mirror — and always before a release.
The reason this exists as scripts rather than a checklist: Spectre's real failures are silent. A skill whose frontmatter name drifts from its directory never triggers. A stale Codex mirror serves every Codex user the previous version indefinitely. A missing SessionStart registry or exact-load path leaves project knowledge undiscoverable without blocking the user's work. None of these break a test or throw an error — they just quietly stop working. So every check asserts an observable condition (file contents, exit code, byte-comparison) and exits nonzero. Nothing here is eyeballed.
node .agents/skills/verify-spectre/scripts/verify.mjs # gates 1-4 (default, pre-commit)
node .agents/skills/verify-spectre/scripts/verify.mjs --fast # gates 1-2 (seconds, on every change)
node .agents/skills/verify-spectre/scripts/verify.mjs --release # gates 1-5 (before publishing)
node .agents/skills/verify-spectre/scripts/verify.mjs --gate 4 # one gate, when iterating on a fixThe scripts live alongside this skill under .agents/skills/verify-spectre/scripts/ and are the single canonical copy tracked by the public repository. Keeping the executable gates beside the skill makes a fresh clone independently verifiable without relying on ignored .claude/ state.
Run from the repo root. The scripts locate the repo from their own path, so they work regardless of your working directory.
Report the PASS/FAIL summary. On failure, each check already names what was expected and what was found — quote that rather than re-deriving it.
| # | Gate | Asserts |
|---|---|---|
| 1 | structure | Skill/agent frontmatter valid and name matches its directory · expected-skills manifest intact · hooks.json parses, scripts exist, SessionStart order is bootstrap → handoff-resume → load-knowledge · no active skill contains {{REGISTRY}} · no stale fork naming · every Skill(spectre-x) / /spectre:spectre-x / @spectre:agent reference resolves · four canonical version files agree |
| 2 | tests | npm test passes; reports the test count so a silent drop (deleted tests, not fixed ones) is visible |
| 3 | codex | sync-codex --check is clean — the committed mirror matches canonical source · generated hooks reference .mjs, never .cjs, and every referenced script exists · user commands use $spectre:spectre-* and skill paths use .agents/skills/ |
| 4 | real-cli | The CLI and hooks actually run, in throwaway temp dirs with a fresh CODEX_HOME (see below) |
| 5 | release | Clean tree · mirror in sync · versions in lockstep · tag free · GitHub authenticated |
Tests exercise functions; users exercise the installed CLI and the hooks that fire at session start. Those are different things, and the gap between them is where this project's actual bugs have lived. Gate 4 closes it by driving the real binary:
systemMessage.recordDirectory and safe resources paths, and one invocation advances successful-load activity exactly once.handoff-resume.install/update/uninstall codex return CODEX_PLUGIN_REQUIRED and do not mutate files.spectre_* agents, reject unowned collisions, remove legacy direct-install runtime, and doctor codex reports native readiness.Transcript file-read evidence may inform a later curation review, but it is optional secondary evidence and never changes runtime registry rank.
If gate 4 can't run safely (no codex binary, sandbox restrictions), say so and stop — don't substitute the test suite for it and call the work validated. A green gate 2 with a skipped gate 4 means the functions work and the product is unverified.
references/expected-skills.txt (alongside the scripts) is the skill manifest. Skills get added and removed on purpose, never by accident, so gate 1 fails on any drift — update the manifest in the same commit as the skill change. That's the check that catches a skill silently lost in a merge or refactor.
When you add a new invariant to the plugin, add its check to the gate it belongs to. A check that lives in a script runs every time; a check that lives in someone's memory runs once.
© joenandez, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 7 other files (scripts, references) in .agents/skills/verify-spectre of joenandez/spectre.
Open the folder on GitHubat commit 931c9e8
Verify Spectre 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 |
|---|---|---|---|---|---|---|
| Verify Spectre this skilljoenandez/spectre | 164 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Sealeap Amazon New Product Launch Planxjli360/sealeap-amazon-skills | 251 | — | ~548 | Automated safety check: Pass | MIT | |
| Roam Release ReadinessCranot/roam-code | 517 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Feature Launch Playbookgooseworks-ai/goose-skills | 1.2k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Operating System Visualizationmingchen666/Reviva | 244 | — | ~1.2k | Automated safety check: Pass | None | |
| Strategizeghaida/intent | 207 | — | ~6.1k | Automated safety check: Pass | CC0-1.0 |
xjli360/sealeap-amazon-skills
Create a quantified Amazon new-product launch plan by translating a sales target into comparable-product benchmarks, keyword economics, budget scenarios, milestones, and stop-loss rules.
Cranot/roam-code
Qualify a Roam commit or accumulated batch for package, website, or server publication; reconcile source, tests, review, CI and deployed identities, and identify the next authorized release step.
gooseworks-ai/goose-skills
Take a new feature or product update and generate the full launch kit: changelog entry, email announcement, LinkedIn post variants, in-app banner text, Twitter/X thread, and internal sales…
mingchen666/Reviva
A skill your agent uses whenever the user wants visual learning for operating systems, process states, CPU scheduling, Gantt charts, synchronization, semaphore/PV problems, deadlock, Banker's…
ghaida/intent
Frames product design problems before solutions exist. An agent skill from ghaida/intent.
dotnet/maui
Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.
joenandez/spectre
A skill your agent uses when modifying the Codex SPECTRE install flow, SessionStart continuity, project skill syncing, registry injection, or Codex-specific runtime files.
joenandez/spectre
Save a quiet, branch-keyed session snapshot with continuity, active work, and optional task/todo state for automatic resume.
joenandez/spectre
User-invoked front door for durable capture. An agent skill from joenandez/spectre.
joenandez/spectre
Rewrite a verbose SPECTRE skill into a compact, contract-form Spectre skill proposal — clear on WHAT, silent on HOW — grounded in the spectre-light distillation and freedom-tier budget.
joenandez/spectre
Rewrite Spectre subagent definitions into compact, contract-driven agents with clear routing, least-privilege tools, output schemas, and an auditable rewrite trail.
joenandez/spectre
Capture durable project decisions, accepted corrections, verified reusable patterns or gotchas, disproved guidance, and changed persistent blockers as soon as they matter.
A skill your agent uses when validating that the Spectre plugin itself still works after ANY change to this repo — skills, prompts, agents, hooks, the CLI, the Codex mirror, or a release. Verify Spectre is an agent skill from joenandez/spectre. Use when validating that the Spectre plugin itself still works after ANY change to this repo — skills, prompts, agents, hooks, the CLI, the Codex mirror, or a release.
Verify Spectre fits situations like: validating that the Spectre plugin itself still works after ANY change to this repo — skills; the Codex mirror; does this still work; check the plugin.
Run `npx skills add joenandez/spectre --skill verify-spectre -a claude-code`. Or copy the skill folder (.agents/skills/verify-spectre in joenandez/spectre) into .claude/skills/verify-spectre in your project. Claude Code loads it when a task matches its description.
Run `npx skills add joenandez/spectre --skill verify-spectre -a codex`. Or copy the skill folder (.agents/skills/verify-spectre in joenandez/spectre) into .agents/skills/verify-spectre in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add joenandez/spectre --skill verify-spectre -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-spectre, .gemini/skills/verify-spectre, .github/skills/verify-spectre and .opencode/skills/verify-spectre in your project.
Going by SKILL.md and its folder, Verify Spectre needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node and npm). Our summary lists: Node.js.
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Verify Spectre is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 129 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Verify Spectre: Sealeap Amazon New Product Launch Plan (xjli360/sealeap-amazon-skills, 251 stars), Roam Release Readiness (Cranot/roam-code, 517 stars), Feature Launch Playbook (gooseworks-ai/goose-skills, 1.2k stars) and Operating System Visualization (mingchen666/Reviva, 244 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
joenandez (a GitHub user) maintains it in joenandez/spectre, which has 164 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 2, 2026.
Source: joenandez/spectre on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
