Darwin Skill Optimizer
alchaincyf/darwin-skill
Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.
Decides where a new agent skill belongs in the ToolJet repo, public root or private ee submodule, then wires the symlinks so it loads in Claude Code, Cursor and Codex.
Install ToolJet Skill Manager
$ npx skills add ToolJet/ToolJet --skill manage-skills -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ToolJet/ToolJet manage-skills --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/ToolJet/ToolJet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/manage-skills .claude/skills/manage-skills && 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 "manage-skills" agent skill from https://github.com/ToolJet/ToolJet/tree/main/.agents/skills/manage-skills into .claude/skills/manage-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-skills", 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/ToolJet/ToolJet/tree/main/.agents/skills/manage-skillsType 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 ToolJet/ToolJet --skill manage-skills -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ToolJet/ToolJet manage-skills --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ToolJet/ToolJet.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/manage-skills .agents/skills/manage-skills && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "manage-skills" agent skill from https://github.com/ToolJet/ToolJet/tree/main/.agents/skills/manage-skills into .agents/skills/manage-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-skills", 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 ToolJet/ToolJet --skill manage-skills -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ToolJet/ToolJet manage-skills --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ToolJet/ToolJet.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/manage-skills .cursor/skills/manage-skills && 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 "manage-skills" agent skill from https://github.com/ToolJet/ToolJet/tree/main/.agents/skills/manage-skills into .cursor/skills/manage-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-skills", 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/ToolJet/ToolJet.git --path .agents/skills/manage-skills--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 ToolJet/ToolJet --skill manage-skills -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ToolJet/ToolJet manage-skills --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ToolJet/ToolJet.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/manage-skills .gemini/skills/manage-skills && 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 "manage-skills" agent skill from https://github.com/ToolJet/ToolJet/tree/main/.agents/skills/manage-skills into .gemini/skills/manage-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-skills", 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 ToolJet/ToolJet manage-skillsInstalls 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 ToolJet/ToolJet --skill manage-skills -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ToolJet/ToolJet.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/manage-skills .github/skills/manage-skills && 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 "manage-skills" agent skill from https://github.com/ToolJet/ToolJet/tree/main/.agents/skills/manage-skills into .github/skills/manage-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-skills", 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 ToolJet/ToolJet --skill manage-skills -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ToolJet/ToolJet manage-skills --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ToolJet/ToolJet.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/manage-skills .opencode/skills/manage-skills && 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 "manage-skills" agent skill from https://github.com/ToolJet/ToolJet/tree/main/.agents/skills/manage-skills into .opencode/skills/manage-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-skills", 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
manage-skills- GitHub stars
- 41k
- Token cost
- ~867 tokens
- SKILL.md length
- 394 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Decides where a new agent skill belongs in the ToolJet repo, public root or private ee submodule, then wires the symlinks so it loads in Claude Code, Cursor and Codex.
- Works in 6 steps: Ask: is this for outside contributors,… → Pick a name. Check it does not collide… → Create //SKILL.md with frontmatter name… → …
- Adding a new agent skill to the ToolJet repository
- SKILL.md covers Steps, Moving or renaming, Skill not showing up and Rules
- Calls git
What it does
This skill covers adding, moving, renaming and repairing agent skills inside the ToolJet repository. Skills live in the private frontend/ee submodule by default. A skill goes in the public root only when outside contributors without enterprise access are meant to use it and its text is safe to publish. Skills that file to ToolJet/tj-ee, hand off to a private skill or need the submodules stay private, and always in frontend/ee rather than server/ee.
The steps are to ask who will use the skill, pick a name that does not collide with a loaded plugin skill, create SKILL.md with name and description frontmatter, run scripts/sync-skills.sh from the repo root to create missing links and remove stale ones, and verify that the skill resolves under .claude/skills. Moves use git mv followed by the same sync script. The script refuses to overwrite a real directory, so a name clash with a public skill fails loudly. A separate section covers a skill that is not showing up.
When your agent uses it
- Adding a new agent skill to the ToolJet repository
- Moving or renaming a skill between the public root and the private submodule
- Fixing a skill that does not show up in Claude Code, Cursor or Codex
Example prompts
- “Add a new team-only skill for triaging support tickets and link it up.”
- “Move the release-notes skill from the private submodule to the public root.”
- “My new skill is not showing up in Claude Code, so repair its links.”
Requirements
- A checkout of the ToolJet repository
- Git
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Ask: is this for outside contributors, and is the text safe on GitHub? Unless both are yes, it's 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…
- Create //SKILL.md with frontmatter name and description (description = when to trigger, one paragraph). Cite shared material by repo-root…
- Run scripts/sync-skills.sh from repo root. It creates every missing link and removes stale ones.
- Verify: ls -L .claude/skills//SKILL.md resolves from repo root. The script refuses to overwrite a real directory, so a name already used…
- Private skill → commit content in frontend/ee first, then links + submodule pointer in root (commit skill handles the order).
What it can do on your machine
Read from SKILL.md and the folder at commit d33ebe7. 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:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
ToolJet Skill Manager loads about 867 tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 394 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.
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.
SKILL.md
The full file from ToolJet/ToolJet at commit d33ebe7, republished under its AGPL-3.0 licence (© ToolJet). 394 words, ~867 tokens.
Download SKILL.mdSave it as
.claude/skills/manage-skills/SKILL.md (or your agent's skills folder).- name
- manage-skills
- description
- 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
Skills live in the private frontend/ee submodule by default. A skill goes in the public root only if outside contributors, who have no EE access, are meant to use it.
| Who uses it? | Content lives in | Root gets |
|---|---|---|
| Outside contributors too (and the text is public-safe) | .agents/skills/<name>/ | .claude/skills/<name> link |
| The team (default) | frontend/ee/.agents/skills/<name>/ | .agents/skills/<name> + .claude/skills/<name> links |
A skill that depends on EE access belongs in frontend/ee. That includes skills that file to ToolJet/tj-ee, hand off to a private skill, or need the submodules checked out.
Private skills always go in frontend/ee, never server/ee, even if backend-flavoured. Skills are not code, and one home keeps a single link chain. server/ee has no .agents/, so don't create one.
Steps
- Ask: is this for outside contributors, and is the text safe on GitHub? Unless both are yes, it's private.
- Pick a name. Check it does not collide with a plugin skill already loaded (e.g.
superpowers:test-driven-development); prefix withtj-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.mdwith frontmatternameanddescription(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.shfrom repo root. It creates every missing link and removes stale ones. - Verify:
ls -L .claude/skills/<name>/SKILL.mdresolves 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/eefirst, then links + submodule pointer in root (commitskill handles the order).
Show full SKILL.md (125 more words)Show less
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 → runscripts/sync-skills.sh.- Link resolves but harness still blind → private skill on a clone without
frontend/eechecked 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.
© ToolJet, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/manage-skills of ToolJet/ToolJet.
Open the folder on GitHubat commit d33ebe7
Compare with similar skills
ToolJet Skill Manager 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 |
|---|---|---|---|---|---|---|
| ToolJet Skill Manager this skillToolJet/ToolJet | 41k | — | ~867 | Automated safety check: Pass | AGPL-3.0 | |
| Darwin Skill Optimizeralchaincyf/darwin-skill | 6.2k | 1 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Darwin SkillHHU3637kr/skills | 145 | 1 repos | ~2.2k | Automated safety check: Pass | None | |
| Skill Creatorzhayujie/CowAgent | 47k | — | ~4.7k | Automated safety check: Notes | MIT | |
| Open-Science Skill Creatoraipoch/open-science | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Skill Quality ReviewerGalaxy-Dawn/claude-scholar | 5.7k | 1 repos | ~3k | Automated safety check: Pass | MIT |
Similar skills
Darwin Skill
HHU3637kr/skills
Darwin Skill (达尔文.skill): autonomous skill optimizer inspired by Karpathy's autoresearch.
Skill Creator
zhayujie/CowAgent
Guides creating, installing and updating agent skills in a workspace: SKILL.md frontmatter, bundled scripts and references, with scripts to scaffold, validate and package.
Open-Science Skill Creator
aipoch/open-science
Creates, revises, evaluates and publishes skills in the Open-Science app through its native host.skills composer, with optional test prompts and benchmarks.
Skill Quality Reviewer
Galaxy-Dawn/claude-scholar
Scores a skill across description, content organization, writing style and structure, then produces letter grades and a prioritized improvement plan.
Harness Evolution Feedback Loop
revfactory/harness
Collects feedback on how an agent harness performed, generalizes it, and updates the harness agents, skills and orchestrator along with a change-history table.
More from ToolJet/ToolJet
ToolJet Marketplace Plugin Builder
ToolJet/ToolJet
Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.
ToolJet Multi-Repo Commit
ToolJet/ToolJet
Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.
ToolJet Pull Request Creator
ToolJet/ToolJet
Opens a pull request for the current ToolJet branch, pushing the root repo and the ee submodules, creating submodule PRs first and then the main PR with a generated description.
ToolJet Pull Request Review
ToolJet/ToolJet
Reviews a ToolJet pull request of any size and writes a findings report for you to read first, scaling the process to the diff and posting to GitHub only on request.
ToolJet Release Cutter
ToolJet/ToolJet
Cuts a ToolJet release branch, bumps the version and moves feature PRs onto it, or adds more PRs to a release that already exists.
ToolJet Multi-Repo Merge
ToolJet/ToolJet
Merges a source branch into the current branch across ToolJet's root repo and its server/ee and frontend/ee submodules, handling conflicts and submodule order.
Related
Works with
Categories
Questions about ToolJet Skill Manager
What does ToolJet Skill Manager do?
Decides where a new agent skill belongs in the ToolJet repo, public root or private ee submodule, then wires the symlinks so it loads in Claude Code, Cursor and Codex. This skill covers adding, moving, renaming and repairing agent skills inside the ToolJet repository. Skills live in the private frontend/ee submodule by default.
When should I use ToolJet Skill Manager?
ToolJet Skill Manager fits situations like: adding a new agent skill to the ToolJet repository; moving or renaming a skill between the public root and the private submodule; fixing a skill that does not show up in Claude Code, Cursor or Codex.
How do I install ToolJet Skill Manager in Claude Code?
Run `npx skills add ToolJet/ToolJet --skill manage-skills -a claude-code`. Or copy the skill folder (.agents/skills/manage-skills in ToolJet/ToolJet) into .claude/skills/manage-skills in your project. Claude Code loads it when a task matches its description.
How do I install ToolJet Skill Manager in Codex?
Run `npx skills add ToolJet/ToolJet --skill manage-skills -a codex`. Or copy the skill folder (.agents/skills/manage-skills in ToolJet/ToolJet) into .agents/skills/manage-skills in your project. Codex loads it when a task matches its description.
Can I use ToolJet Skill Manager 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 ToolJet/ToolJet --skill manage-skills -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/manage-skills, .gemini/skills/manage-skills, .github/skills/manage-skills and .opencode/skills/manage-skills in your project.
What does ToolJet Skill Manager need to run?
Going by SKILL.md and its folder, ToolJet Skill Manager needs the command-line tools its instructions call (git). Our summary lists: A checkout of the ToolJet repository; Git.
Does ToolJet Skill Manager access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is ToolJet Skill Manager 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 ToolJet Skill Manager use?
ToolJet Skill Manager is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does ToolJet Skill Manager use?
About 867 tokens (SKILL.md is roughly 3.5k 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 ToolJet Skill Manager?
Skills that share tags, products or a category with ToolJet Skill Manager: Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars), Darwin Skill (HHU3637kr/skills, 145 stars), Skill Creator (zhayujie/CowAgent, 47k stars) and Open-Science Skill Creator (aipoch/open-science, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains ToolJet Skill Manager?
ToolJet (a GitHub organization) maintains it in ToolJet/ToolJet, which has 41,058 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 10, 2026.
Source: ToolJet/ToolJet on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.