list-skills
Skill28 starsChanged 59 days agoApache-2.0View on GitHub
List the skills on this machine (your Library) and the skills your team shares (the Marketplace) as Markdown boards from the terum-skills CLI. Use when the user asks what skills they have, what the team shares, what is installed, edited, untracked or missing an eval, or wants an overview of their terum-skills state.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- MosoFin/mosofin-llm-plugintheir own version, first seen Nov 15, 2026
- danielrosehill/Claude-Israel-Agent-Skills-Plugintheir own version, first seen Nov 13, 2026
- MosoFin/mosofin-mcp-plugintheir own version, first seen Nov 12, 2026
- MosoFin/mosofin-pluginstheir own version, first seen Nov 12, 2026
- matthewyuh246/Claude_Skillstheir own version, first seen Oct 11, 2026
- TangleML/tangle-uitheir own version, first seen Oct 8, 2026
Used with
Projects with it also use list-tools, query-workspace and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MosoFinSkilllist-tools
Show which MosoFin API operations are available for a connected datasource and their policy (maps to the get_datasource_tools MCP tool). Use when the user asks what data can be pulled, which financial data operations exist, or whether an operation is allowed.
Also in 3 projects that use this
MosoFinSkillquery-workspace
Query MosoFin workspace business data (accounting platforms and other connected SaaS). Use when the user asks for P&L, invoices, cash, customers, or any live books data, or mentions MosoFin, a client workspace, or reconnecting a data source.
Also in 3 projects that use this
TheKontextCoSkillsave-skill
Save a reusable Agent Skill to Kontext so it is available from any MCP client
Also in 3 projects that use this
simstudioaiSkillrun-tool
Call one Sim integration tool directly through the sim CLI, using credentials Sim already holds. Use for a single action against a connected service — send a message, create an issue, scrape a page; not for multi-step logic or anything scheduled, which belongs in a workflow.
Also in 3 projects that use this
stacksyncdataSkillconnections
Lists, creates, reads, renames, shares, reauthorizes and deletes Stacksync connections, reads the live tables and columns of a connected app, and explains network options and app rate limits. Use when someone wants to connect an app or database, a connection expired or needs reauthorization, a teammate cannot see a connection, a connection must be deleted, someone asks which tables or fields an app has, or a database sits behind a firewall or in a private network.
Also in 3 projects that use this
LangChainSkillworkspaces
How a Robin workspace's sandbox image works and how to change it — create one, edit or fork an existing one, start from scratch, what setup_script and update_script are for, why a nightly refresh failed, where the build logs are, and how to read a rebuild in progress. Read this whenever someone asks about workspaces, snapshots, sandbox images, or a refresh, whether or not this is an admin thread.
Also in 3 projects that use this
- +1 more from MosoFin
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- TangleML/tangle-ui★ 104same name
- amebahead/skills-cleaner★ 43same name
- MosoFin/mosofin-llm-plugin★ 3same name
- MosoFin/mosofin-mcp-plugin★ 3same name
- MosoFin/mosofin-plugins★ 3same name
- danielrosehill/Claude-Israel-Agent-Skills-Plugin★ 2same name
- demithras/ClearMeta★ 1same name
- matthewyuh246/Claude_Skills★ 0same 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
- search-skillsSkill
- skill-infoSkill
- skill-statusSkill
- sync-skillsSkill
- terum-skillsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
Distinctive
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
- Distinctive: line 15
Run with your shell tool, from the current working directory:
- Very specific: line 32
No TTY: never pipe y, never drive the CLI with expect, never add --frames to dodge a question.
- Very specific: line 33
Never use the skill-file
!commandinjection. - Very specific: line 34
Do not cd; run from the current working directory and pass absolute paths.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Show the user's skills as boards. The terum-skills CLI renders them with --format md; the board it prints is the answer.
Arguments: everything after the command (in Claude Code this arrives as "$ARGUMENTS"). --local shows only your Library, --team only the team Marketplace, and --team <name> names a configured team (passed through unchanged); with no arguments show both.
Command
Run with your shell tool, from the current working directory:
npx -y terum-skills@latest ls --local --format md
npx -y terum-skills@latest ls --format mdWith --local, run only the first; with --team, only the second; with --team <name>, only the second with --team <name> appended. Add --rows all to either when the user asks for every row.
Before
Nothing to confirm: both commands only read this machine and the local team clone.
After
Show each board verbatim as the answer; do not re-summarise unless asked. The board's Next: line holds the follow-ups to offer. On a machine with no team the second command fails: the board carries a > ❌ No team is configured on this machine. block with the two get-started lines and exits 1. That is a result — say in one sentence that there is no team yet and show the Library board from the first command. If a board carries a Notes or > ❌ failure block naming a hand-off, say plainly "run this in a terminal" and give the command.
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.

