/skill-editor
REQUIRED for editing any skill file. Ensures changes sync to Claude, Codex, and Cursor. Never edit .claude/skills/ files directly - always use this skill.
$ npx -y skills add stacklok/toolhive-studio --skill skill-editor --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/skill-editor
Context preview
The summary Claude sees to decide when to auto-load this skill.
REQUIRED for editing any skill file. Ensures changes sync to Claude, Codex, and Cursor. Never edit .claude/skills/ files directly - always use this skill.
SKILL.md
skill-editor.SKILL.mdname: skill-editor
description: REQUIRED for editing any skill file. Ensures changes sync to Claude, Codex, and Cursor. Never edit .claude/skills/ files directly - always use this skill.
Skill Editor
Edit existing AI agent skills while keeping Claude, Codex, and Cursor in sync.
Workflow
1. **Always edit Claude first** - `.claude/skills/<name>/SKILL.md` is the canonical source 2. **Replicate with CLI** - Copy changes to `.codex/skills/` and `.cursor/skills/` 3. **Never edit Codex/Cursor directly** - They are copies of Claude's version
Finding Existing Skills
List all skills:
ls -la .claude/skills/
Read a skill:
cat .claude/skills/<name>/SKILL.md
Editing a Skill
1. Read the current skill content from `.claude/skills/<name>/SKILL.md` 2. Make the requested changes 3. Replicate to other agents:
cp .claude/skills/<name>/SKILL.md .codex/skills/<name>/
cp .claude/skills/<name>/SKILL.md .cursor/skills/<name>/
Verification
Always verify sync after editing:
diff .claude/skills/<name>/SKILL.md .codex/skills/<name>/SKILL.md
diff .claude/skills/<name>/SKILL.md .cursor/skills/<name>/SKILL.md
No output means files are identical.
Common Edits
- **Update description** - Improve auto-discovery keywords
- **Add instructions** - Expand the skill's capabilities
- **Fix errors** - Correct mistakes in the skill logic
- **Add references** - Create `references/` directory for supporting docs
Deleting a Skill
Remove from all three locations:
rm -rf .claude/skills/<name> .codex/skills/<name> .cursor/skills/<name>
Read more
name: skill-editor description: REQUIRED for editing any skill file. Ensures changes sync to Claude, Codex, and Cursor. Never edit .claude/skills/ files directly - always use this skill.
Skill Editor
Edit existing AI agent skills while keeping Claude, Codex, and Cursor in sync.
Workflow
1. **Always edit Claude first** - `.claude/skills/<name>/SKILL.md` is the canonical source 2. **Replicate with CLI** - Copy changes to `.codex/skills/` and `.cursor/skills/` 3. **Never edit Codex/Cursor directly** - They are copies of Claude's version
Finding Existing Skills
List all skills:
ls -la .claude/skills/
Read a skill:
cat .claude/skills/<name>/SKILL.md
Editing a Skill
1. Read the current skill content from `.claude/skills/<name>/SKILL.md` 2. Make the requested changes 3. Replicate to other agents:
cp .claude/skills/<name>/SKILL.md .codex/skills/<name>/ cp .claude/skills/<name>/SKILL.md .cursor/skills/<name>/
Verification
Always verify sync after editing:
diff .claude/skills/<name>/SKILL.md .codex/skills/<name>/SKILL.md diff .claude/skills/<name>/SKILL.md .cursor/skills/<name>/SKILL.md
No output means files are identical.
Common Edits
- **Update description** - Improve auto-discovery keywords
- **Add instructions** - Expand the skill's capabilities
- **Fix errors** - Correct mistakes in the skill logic
- **Add references** - Create `references/` directory for supporting docs
Deleting a Skill
Remove from all three locations:
rm -rf .claude/skills/<name> .codex/skills/<name> .cursor/skills/<name>
Run any Model Context Protocol (MCP) server — securely, instantly, anywhere. ToolHive is the easiest way to discover, deploy, and manage MCP servers. Launch any MCP server in a locked-down container with just a few clicks.
Repo: stacklok/toolhive-studio
Other skills on toolhive-studio.
- /bug-fix-tdd
Reproduce and fix bugs using TDD. Use when analyzing a bug report, writing a regression test, or applying a minimal fix. Covers test placement, mock patterns, and the red-green-refactor workflow for automated bug fixing.
Open skill - /deep-links
Deep links in ToolHive Studio. Use when implementing, debugging, or asking about deep link features (toolhive-gui:// protocol), adding new deep link intents, understanding the deep link architecture, IPC model, or platform/packaging support.
Open skill - /devcontainer-dev
Spin up and interact with ToolHive Studio's containerized dev environment (Xvfb + noVNC + DinD). Use when running, testing, or debugging the app in isolation — locally, in a git worktree, or in GitHub Codespaces; when touching `.devcontainer/*`, `scripts/devcontainer-*.sh`, or
Open skill - /security-vuln-remediation
Remediate security vulnerabilities found by Grype or pnpm audit. Use when a security scan fails, a CVE needs fixing, or you need to analyze, upgrade, override, or ignore a vulnerable dependency.
Open skill - /skill-creator
Create new AI agent skills for Claude Code, Codex, and Cursor. Use when asked to create a skill, add a new agent capability, or set up a slash command.
Open skill - /testing-api-assertions
Verify API requests in tests. Use when testing that correct API calls are made for create, update, or delete operations. Use when testing mutations, form submissions, or actions with backend side effects.
Open skill