search-skills
Skill28 starsChanged 59 days agoApache-2.0View on GitHub
Search the team's shared skills by name, description or category, optionally narrowed by author or project, and show the matches as a Markdown board from the terum-skills CLI. Use when the user asks whether the team has a skill for something or wants to find one by keyword.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- danielvm-git/bigpowerstheir own version, first seen Nov 6, 2026
- wentorai/research-pluginstheir own version, first seen Oct 8, 2026
- amebahead/skills-cleanertheir own version, first seen Mar 20, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- wentorai/research-plugins★ 298same name
- danielvm-git/bigpowers★ 292same name
- amebahead/skills-cleaner★ 43same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- desktop/AGENTS.mdAGENTS.md
- eval-reportSkill
- evalSkill
- list-skillsSkill
- skill-infoSkill
- skill-statusSkill
- sync-skillsSkill
- terum-skillsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
No TTY: never pipe y, never drive the CLI with expect, never add --frames to dodge a question.
- Very specific: line 30
Never use the skill-file
!commandinjection. - Very specific: line 31
Do not cd; run from the current working directory and pass absolute paths.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Find skills in the team Marketplace.
Arguments: everything after the command (in Claude Code this arrives as "$ARGUMENTS"): the search term, then any of --category <c>, --author <a>, --project <p>, passed through unchanged. Search covers every configured team. Ask for a term when none is given.
Command
npx -y terum-skills@latest search <term> [--category <c>] [--author <a>] [--project <p>] --format mdQuote a term that contains spaces.
Before
Nothing to confirm: the command only reads the local team clone. When the user wants the newest catalogue, run the sync-skills skill first.
After
Show the board verbatim. No skills found. is a result: say so and offer a broader term or the list-skills skill. Offer the Next: line (the skill-info skill for a match; installing goes through the terum-skills skill, which confirms the destination first).
Rules
- No TTY: never pipe
y, never drive the CLI withexpect, never add--framesto dodge a question. A question the CLI asks means the verb belongs in a terminal: say so and hand over the command. - Never use the skill-file
!`command`injection; run every command with your shell tool and read its output. - Do not
cd; run from the current working directory and pass absolute paths. - Exit 1 is a result, not a retry: show the failure block, do not re-run, and do not claim earlier steps were rolled back.
Sandbox
When CODEX_SANDBOX_NETWORK_DISABLED=1 is set and the command starts with npx, add --prefer-offline after npx so a cached package resolves without the registry; if npx still reports a network error, ask the user to run the command in a terminal. In that sandbox the verbs that need the network — sync, install, publish, invite, eval, and update's release probe — are handed to a terminal with the reason.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

