CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

claude-code

Operate Claude Code CLI (v2.1+) via the terminal. Load only when the user explicitly authorizes this skill or names Claude Code / claude-code. Before any command, confirm the `claude` binary is available; if missing, stop and give install or auth guidance. Covers print mode (-p), interactive tmux sessions, and background (--bg) orchestration.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary skill body: executable commands with concrete values, a decision-first mode-selection table, an operational guardrail checklist with validation and feedback steps, and clean one-level progressive disclosure to five real bundle files. No material weaknesses found.

DimensionReasoningScore

Conciseness

Lean and dense throughout: decision table, flag lists, and command blocks with no concept padding — every line carries version-specific operational detail Claude would not reliably know ("the `--dangerously-skip-permissions` dialog defaults to 'No, exit'", "Session resume is per-directory", "Slash commands don't work in `-p`"). Matches anchor 5; nothing to trim without losing information.

5 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: setup (`npm install -g @anthropic-ai/claude-code && claude auth login`), the primary `terminal(...)` invocation with concrete values (`--allowedTools 'Read,Edit'`, `--max-turns 10`, `timeout=180`), and five variants including pipe-review, `--resume`, `--json-schema`, CI (`--bare`), and cost caps (`--max-budget-usd 0.50`). Matches anchor 5.

5 / 5

Workflow Clarity

Explicit sequence — "Setup (once)" → "Platform check (before running anything)" → "Mode Selection (decide FIRST)" → mode sections → guardrail checklist — with validation steps ("verify with `claude auth status` / `claude doctor`", "Report back... use the JSON `result` + `git diff`"), a feedback loop ("monitor `/context`, use `/compact`"), and safety checks ("only run in trusted directories", "Don't kill slow sessions — capture progress first"). Matches anchor 5.

5 / 5

Progressive Disclosure

A ~70-line overview with all detail pushed to five verified, one-level-deep reference files, each clearly signaled inline ("→ `references/flags.md`") and in a closing "read when" table. Structure mirrors the anchor-5 example; no nested reference chains and no content that should be externalized inlined in the body.

5 / 5

Total

20

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete, third-person, with an explicit load condition and the three operating modes enumerated with their flags. The main improvement opportunities are broader natural-keyword coverage (delegate/agent phrasings) and mentioning the delegation use-cases the skill actually serves.

Suggestions

Add natural trigger variations users would say, e.g. 'delegate coding work to Claude Code' or 'spawn/run a claude agent', to broaden keyword coverage.

Name one or two concrete delegation use-cases (fix a bug, review a diff) so the 'what' covers what tasks the skill performs, not just which modes it operates.

DimensionReasoningScore

Specificity

Lists several concrete actions — "confirm the `claude` binary is available", "stop and give install or auth guidance", "Covers print mode (-p), interactive tmux sessions, and background (--bg) orchestration" — but coverage has minor gaps (delegation use-cases like bug fixes/diff reviews and `ultrareview` are not mentioned). Matches anchor 4 (several specific actions, minor gaps) rather than 5 (comprehensive) or 3 (only 1-2 actions).

4 / 5

Completeness

Clearly answers both: what — "Operate Claude Code CLI (v2.1+) via the terminal... Covers print mode (-p), interactive tmux sessions, and background (--bg) orchestration"; when — "Load only when the user explicitly authorizes this skill or names Claude Code / claude-code", an explicit trigger clause with concrete phrasing. Fits anchor 5; the 'when' is fully explicit, so anchor 4's caveat does not apply.

5 / 5

Trigger Term Quality

Good natural-keyword coverage: "names Claude Code / claude-code", "CLI", "terminal", "print mode (-p)", "tmux", "background (--bg)" — terms users would naturally say. A few natural variations are missing (e.g., "delegate to Claude Code", "claude agent", "spawn claude"), matching anchor 4 rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche ("Operate Claude Code CLI") with distinct explicit triggers ("names Claude Code / claude-code"), so it is unlikely to fire for the wrong skill. Minimal conflict risk matches anchor 5; anchor 4's 'minor overlap risk with closely related skills' is not evidenced.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

XiaomiMiMo/MiMo-Code

Path

packages/cli/src/skill/builtin/.bundle/claude-code/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.