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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Show the eval history of one shared skill.
Arguments: everything after the command (in Claude Code this arrives as "$ARGUMENTS"): the skill's name (a unique prefix works, and nothing is needed inside a Library skill folder) and --team <name> when the user names a team, passed through.
npx -y terum-skills@latest eval-report <skill> --format md
It reads the local team clone and this machine's run history; it never fetches. When the user wants the newest receipts, run the sync-skills skill first.
Nothing to confirm: the command only reads.
Show the board verbatim. A skill that lives only in the Library (never published) has no team report: the failure says so — offer the eval skill instead. Offer the Next: line.
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.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.