Internal Comms
alirezarezvani/claude-skills
A skill your agent uses when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement…
Internal diagnosis engine for the Spectre Fix workflow. An agent skill from joenandez/spectre.
$ npx skills add joenandez/spectre --skill spectre-fix-core -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install joenandez/spectre spectre-fix-core --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/plugins/spectre/skills/spectre-fix-core .claude/skills/spectre-fix-core && 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 "spectre-fix-core" agent skill from https://github.com/joenandez/spectre/tree/main/plugins/spectre/skills/spectre-fix-core into .claude/skills/spectre-fix-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spectre-fix-core", 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/plugins/spectre/skills/spectre-fix-coreType 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 spectre-fix-core -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install joenandez/spectre spectre-fix-core --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/plugins/spectre/skills/spectre-fix-core .agents/skills/spectre-fix-core && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spectre-fix-core" agent skill from https://github.com/joenandez/spectre/tree/main/plugins/spectre/skills/spectre-fix-core into .agents/skills/spectre-fix-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spectre-fix-core", 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 spectre-fix-core -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install joenandez/spectre spectre-fix-core --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/plugins/spectre/skills/spectre-fix-core .cursor/skills/spectre-fix-core && 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 "spectre-fix-core" agent skill from https://github.com/joenandez/spectre/tree/main/plugins/spectre/skills/spectre-fix-core into .cursor/skills/spectre-fix-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spectre-fix-core", 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 plugins/spectre/skills/spectre-fix-core--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 spectre-fix-core -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install joenandez/spectre spectre-fix-core --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/plugins/spectre/skills/spectre-fix-core .gemini/skills/spectre-fix-core && 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 "spectre-fix-core" agent skill from https://github.com/joenandez/spectre/tree/main/plugins/spectre/skills/spectre-fix-core into .gemini/skills/spectre-fix-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spectre-fix-core", 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 spectre-fix-coreInstalls 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 spectre-fix-core -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/plugins/spectre/skills/spectre-fix-core .github/skills/spectre-fix-core && 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 "spectre-fix-core" agent skill from https://github.com/joenandez/spectre/tree/main/plugins/spectre/skills/spectre-fix-core into .github/skills/spectre-fix-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spectre-fix-core", 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 spectre-fix-core -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 spectre-fix-core --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/plugins/spectre/skills/spectre-fix-core .opencode/skills/spectre-fix-core && 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 "spectre-fix-core" agent skill from https://github.com/joenandez/spectre/tree/main/plugins/spectre/skills/spectre-fix-core into .opencode/skills/spectre-fix-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spectre-fix-core", 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.
spectre-fix-coreInternal diagnosis engine for the Spectre Fix workflow. An agent skill from joenandez/spectre.
Spectre Fix Core is an agent skill from joenandez/spectre. Internal diagnosis engine for the Spectre Fix workflow. Use only when invoked by spectre-fix to investigate a reported bug and prepare its Execute handoff. Do NOT invoke directly for user requests.
Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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.
4 steps, taken from the first numbered list in SKILL.md.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
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.
Spectre Fix Core loads about 793 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 347 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); files beside SKILL.md are not scanned.
The full file from joenandez/spectre at commit 931c9e8, republished under its MIT licence (© joenandez). 347 words, ~793 tokens.
.claude/skills/spectre-fix-core/SKILL.md (or your agent's skills folder).Own the diagnostic phase of the bug flow: reproduce the failure, ground the root cause and behavioral blast radius, then return a source-faithful Execute handoff. Execute owns all code changes.
PHASE=diagnose.--orchestrated — withhold user-facing routing, never content.@spectre:analyst for causal and impact traces. Keep returns compact and in-thread, with no scratch reports.Experience-contract rows map technical evidence to product behavior: journey/surface | current experience | expected experience | technical path/consumer | disposition=intended-change|preserved-invariant|collateral-change|unresolved | evidence | verification.
diagnose → DIAGNOSIS_READY: reproduction, root cause, affected files, candidate repair, evidence-backed experience contract, and regression/invariant opportunities; no code writes.DONE when: root cause is grounded and its hypotheses were traced by dispatched analysts; the product and technical direct blast radius was independently explored after the candidate repair boundary was known; no row is unresolved; and the parent receives the diagnosis result.
@spectre:analyst traces; reproduce; synthesize one cause-level repair.@spectre:analyst; parallelize separable product journeys or technical boundaries. Trace shared callers, state, and data paths through to user/operator-observable outcomes. Return compact experience-contract rows that explicitly identify experiences that change, remain invariant, or are unresolved; synthesize and deduplicate the results.diagnose returns DIAGNOSIS_READY before any code write.unresolved row or a new experience-contract row returns to the user for clarification.Return phase status, hypotheses, diagnosis, experience contract with row-level evidence, proposed repair, limitations, and exact Execute source. Execute owns implementation and verification; the parent owns user-facing Next Steps.
© joenandez, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/spectre/skills/spectre-fix-core of joenandez/spectre.
Open the folder on GitHubat commit 931c9e8
Spectre Fix Core 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 |
|---|---|---|---|---|---|---|
| Spectre Fix Core this skilljoenandez/spectre | 164 | — | ~793 | Automated safety check: Pass | MIT | |
| Internal Commsalirezarezvani/claude-skills | 28k | — | ~3.4k | Automated safety check: Pass | MIT | |
| Internal Communicationsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Internal Communications Writeranthropics/skills | 180k | 38 repos | ~378 | Automated safety check: Pass | Apache-2.0 | |
| Internal Comms Anthropicsickn33/agentic-awesome-skills | 47k | 1 repos | ~702 | Automated safety check: Pass | Apache-2.0 | |
| Nofollow Internalthedaviddias/Front-End-Checklist | 74k | — | ~579 | Automated safety check: Pass | MIT |
alirezarezvani/claude-skills
A skill your agent uses when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement…
sickn33/agentic-awesome-skills
Internal communication log: title, type, date, department, host and attendees, agenda, action items, follow-up date, meeting link and delivery status.
anthropics/skills
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill…
sickn33/agentic-awesome-skills
Compatibility alias for internal-comms: draft status updates, newsletters and FAQs from approved sources.
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing internal link structure or reviewing link attributes.
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing a site's internal link structure, identifying pages that need more incoming links, generating contextual linking opportunities between related content, or…
joenandez/spectre
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.
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.
Internal diagnosis engine for the Spectre Fix workflow. An agent skill from joenandez/spectre. Spectre Fix Core is an agent skill from joenandez/spectre. Internal diagnosis engine for the Spectre Fix workflow.
Run `npx skills add joenandez/spectre --skill spectre-fix-core -a claude-code`. Or copy the skill folder (plugins/spectre/skills/spectre-fix-core in joenandez/spectre) into .claude/skills/spectre-fix-core in your project. Claude Code loads it when a task matches its description.
Run `npx skills add joenandez/spectre --skill spectre-fix-core -a codex`. Or copy the skill folder (plugins/spectre/skills/spectre-fix-core in joenandez/spectre) into .agents/skills/spectre-fix-core 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 spectre-fix-core -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spectre-fix-core, .gemini/skills/spectre-fix-core, .github/skills/spectre-fix-core and .opencode/skills/spectre-fix-core in your project.
SKILL.md names no scripts, command-line tools or credentials: Spectre Fix Core is instructions for the agent only.
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.
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.
Spectre Fix Core is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 793 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Spectre Fix Core: Internal Comms (alirezarezvani/claude-skills, 28k stars), Internal Communication (sickn33/agentic-awesome-skills, 47k stars), Internal Communications Writer (anthropics/skills, 180k stars) and Internal Comms Anthropic (sickn33/agentic-awesome-skills, 47k 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.