How do I install the Manage Skills skill?

Run npx skillmds add tooljet/manage-skills in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Manage Skills safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Manage Skills?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Manage Skills free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Manage Skills?

ToolJet (@tooljet) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Manage Skills by tooljet — Agent Skill

Name: Manage Skills
Rating: 4.2 (5 reviews)
Author: ToolJet

Manage Skills

Add, move, or repair agent skills in this repo — decide public root vs private EE submodule placement and wire the symlinks so a skill is invokable from repo root in Claude Code, Cursor and Codex. Use when asked to add, create, move, relocate, or rename a skill, or when a skill is not showing up.

ToolJet f67d89f 2.7 KB Updated Sep 9, 2026

File contents

Manage skills

Skill placement is decided by sensitivity, not by which code the skill touches.

Would we mind this text on GitHub?	Content lives in	Root gets
No (public)	`.agents/skills/<name>/`	`.claude/skills/<name>` link
Yes (private)	`frontend/ee/.agents/skills/<name>/`	`.agents/skills/<name>` + `.claude/skills/<name>` links

Private skills always go in frontend/ee, even if backend-flavoured — skills are not code, one home is enough.

Steps

Ask: would we mind this skill text on GitHub? If unsure, treat as private.
Pick a name. Check it does not collide with a plugin skill already loaded (e.g. superpowers:test-driven-development); prefix with tj- or pick a domain name if it does. Private names are still visible in the public repo via link targets — keep them non-revealing.
Create <home>/<name>/SKILL.md with frontmatter name and description (description = when to trigger, one paragraph). Cite shared material by repo-root path, e.g. frontend/ee/.agents/skills/_shared/investigation-templates.md.
Run scripts/sync-skills.sh from repo root. It creates every missing link and removes stale ones.
Verify: ls -L .claude/skills/<name>/SKILL.md resolves from repo root. The script refuses to overwrite a real directory, so a name already used by a public skill fails loudly — pick another name.
Private skill → commit content in frontend/ee first, then links + submodule pointer in root (commit skill handles the order).

Moving or renaming

git mv the directory to its new home or name, run scripts/sync-skills.sh (removes stale links, adds new ones), then git add .agents/skills .claude/skills.

Skill not showing up

ls -L .claude/skills/<name>/SKILL.md — missing link → run scripts/sync-skills.sh.
Link resolves but harness still blind → private skill on a clone without frontend/ee checked out, or the harness session predates the link (restart it).

Rules

Never create .claude/, .cursor/ or .codex/ inside a submodule — harnesses scope nested dirs to that subtree and surface duplicates.
_shared/ is reference material, not a skill; it is never linked.
A dangling root link (EE not checked out) is expected on OSS clones and is silently skipped.
Pre-commit runs scripts/sync-skills.sh --check; if it fails, run the script and stage the links.

---name: manage-skillsdescription: Add, move, or repair agent skills in this repo — decide public root vs private EE submodule placement and wire the symlinks so a skill is invokable from repo root in Claude Code, Cursor and Codex. Use when asked to add, create, move, relocate, or rename a skill, or when a skill is not showing up.--- # Manage skills Skill placement is decided by **sensitivity**, not by which code the skill touches. | Would we mind this text on GitHub? | Content lives in | Root gets | |---|---|---| | No (public) | `.agents/skills/<name>/` | `.claude/skills/<name>` link | | Yes (private) | `frontend/ee/.agents/skills/<name>/` | `.agents/skills/<name>` + `.claude/skills/<name>` links | Private skills always go in `frontend/ee`, even if backend-flavoured — skills are not code, one home is enough. ## Steps 1. Ask: *would we mind this skill text on GitHub?* If unsure, treat as private. 2. Pick a name. Check it does not collide with a plugin skill already loaded (e.g. `superpowers:test-driven-development`); prefix with `tj-` or pick a domain name if it does. Private names are still visible in the public repo via link targets — keep them non-revealing. 3. Create `<home>/<name>/SKILL.md` with frontmatter `name` and `description` (description = when to trigger, one paragraph). Cite shared material by repo-root path, e.g. `frontend/ee/.agents/skills/_shared/investigation-templates.md`. 4. Run `scripts/sync-skills.sh` from repo root. It creates every missing link and removes stale ones. 5. Verify: `ls -L .claude/skills/<name>/SKILL.md` resolves from repo root. The script refuses to overwrite a real directory, so a name already used by a public skill fails loudly — pick another name. 6. Private skill → commit content in `frontend/ee` first, then links + submodule pointer in root (`commit` skill handles the order). ## Moving or renaming `git mv` the directory to its new home or name, run `scripts/sync-skills.sh` (removes stale links, adds new ones), then `git add .agents/skills .claude/skills`. ## Skill not showing up 1. `ls -L .claude/skills/<name>/SKILL.md` — missing link → run `scripts/sync-skills.sh`. 2. Link resolves but harness still blind → private skill on a clone without `frontend/ee` checked out, or the harness session predates the link (restart it). ## Rules - Never create `.claude/`, `.cursor/` or `.codex/` inside a submodule — harnesses scope nested dirs to that subtree and surface duplicates. - `_shared/` is reference material, not a skill; it is never linked. - A dangling root link (EE not checked out) is expected on OSS clones and is silently skipped. - Pre-commit runs `scripts/sync-skills.sh --check`; if it fails, run the script and stage the links.

Frequently asked questions