Show the state of terum-skills on this machine — team, clone, session hook, pending work, machine facts — and whether a newer CLI release exists, as Markdown boards. Use when the user asks whether terum-skills is set up, in sync or up to date, or when something about it seems off.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Show where this machine stands.
Arguments: everything after the command (in Claude Code this arrives as "$ARGUMENTS"): none are expected; ignore any.
npx -y terum-skills@latest status --format md
npx -y terum-skills@latest update --format md
Run both and show both boards, status first. Without network access (see Sandbox) run only the first and say the release check was skipped.
Nothing to confirm: status reads; update reads git tags from the terum-skills release repository (a configured GitHub team authorises that one probe, at most once a day) and prints the command that would update this copy — it never runs a package manager.
Show the boards verbatim. Exit 0 from status means the query succeeded, not that setup is complete: a get-started headline means there is no team yet. Pending work on the status board needs the matching install or removal retried, not a fetch. Offer the Next: line; the update board's command is for the user to run in a terminal, never for you.
y, never drive the CLI with expect, never add --frames to dodge a question. A question the CLI asks means the verb belongs in a terminal: say so and hand over the command.!`command` injection; run every command with your shell tool and read its output.cd; run from the current working directory and pass absolute paths.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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Evaluate a local skill with the terum-skills CLI — hygiene, trigger evals and execution cases against a baseline, billed to the user's own Claude Code — after confirming the cost, and show the result as a Markdown board. Use when the user asks to eval, test, score or benchmark a skill, or to see whether an edit made it better.
The English summary is being prepared. Showing the original description.
Show a team skill's eval history — committed receipts per version and this machine's local runs — as a Markdown board from the terum-skills CLI, without fetching. Use when the user asks how a shared skill scored, which version passed, or what its receipts say.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Show one skill in full — its team record or Library folder, versions, installs, health, and its eval report when it is a team skill — as Markdown boards from the terum-skills CLI. Use when the user names a skill and asks what it is, who installed it, how it scored, or what its receipt says.
The English summary is being prepared. Showing the original description.
Fetch the team's shared skills — reset each disposable team clone to origin/main — and show the outcome per team as a Markdown board from the terum-skills CLI. Use when the user wants the newest catalogue, receipts or roster before listing, searching or installing.
The English summary is being prepared. Showing the original description.