CtrlK
BlogDocsLog inGet started
Tessl Logo

claude-api

Build apps with the Claude API or Anthropic SDK. TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`/`claude_agent_sdk`, or user asks to use Claude API, Anthropic SDKs, or Agent SDK. DO NOT TRIGGER when: code imports `openai`/other AI SDK, general programming, or ML/data-science tasks.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./configs/microservice/bff-service/configs/agent-skills/anthropics/claude-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A well-structured routing skill with genuinely actionable defaults, exact API parameter syntax, and an excellent task-indexed reading guide. Its main weaknesses are redundancy — model and thinking guidance is repeated in four sections — and inlined time-sensitive details (pricing, dates, beta headers) that both cost tokens and will age poorly.

Suggestions

State the adaptive-thinking/`budget_tokens` rule once in a single section and reference it from the others; the current repetition across Defaults, Current Models, Thinking & Effort, and Common Pitfalls costs tokens without adding information.

Move the model/pricing table and Compaction beta details into a shared reference file (e.g., `shared/models.md`, which is already referenced) to keep the overview stable and lean, since time-sensitive data inlined in SKILL.md ages poorly.

Trim conversational asides ("we wouldn't mess with you like that", "that's the user's decision, not yours") — they pad the skill without changing behavior.

DimensionReasoningScore

Conciseness

Mostly efficient tables and decision trees, but model/thinking guidance is repeated across Defaults, Current Models, Thinking & Effort, and Common Pitfalls ("do NOT use `budget_tokens`" appears four or more times), and time-sensitive data (pricing, "cached: 2026-02-17", beta header `compact-2026-01-12`) is inlined rather than confined to a deprecated/old-patterns section, with conversational asides ("we wouldn't mess with you like that") adding padding. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is above 2 because most sections are tight and load-bearing.

3 / 5

Actionability

Gives exact model ID strings, exact parameter syntax (`thinking: {type: "adaptive"}`, `output_config: {format: {...}}`), SDK helper names (`.get_final_message()` / `.finalMessage()`), and a task-to-file reading map — mostly executable guidance with minor gaps (no inline install/quick-start code). Per the rubric's instruction-only note, absence of code is not penalized when guidance is this actionable, but it lacks the copy-paste-ready examples of a 5.

4 / 5

Workflow Clarity

The core workflow (detect language → choose surface → read specific files) is a clear numbered sequence with ambiguity checkpoints: ask the user which language, fall back to AskUserQuestion options, and default to Python with a note. It is not a destructive or batch operation so no cap applies, but there are no explicit validate-and-recover loops, keeping it at 'clear sequence with most checkpoints' rather than 5.

4 / 5

Progressive Disclosure

The Reading Guide is a well-signaled, one-level-deep reference map with 'Read when...' conditions per file, which is 5-level navigation; however, detail-heavy content (the model/pricing table, Thinking & Effort, Compaction) is inlined in the overview rather than split into the referenced shared files, and no bundle files exist alongside SKILL.md to verify the referenced paths. Net: good structure with minor organization gaps, matching anchor 4.

4 / 5

Total

15

/

20

Passed

Description

82%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 that explicitly states what the skill does, when to trigger it, and — unusually — when not to trigger it, which sharply reduces conflict risk with other AI-SDK skills. The only notable gap is that the 'what' is a single broad action rather than a list of concrete capabilities.

Suggestions

Enumerate 2-3 concrete capabilities in the 'what' clause (e.g., streaming, tool use, batch processing, structured outputs) to raise specificity.

Add common user synonyms such as "Anthropic API" or "Claude SDK" to the trigger clause for broader natural-term coverage.

DimensionReasoningScore

Specificity

"Build apps with the Claude API or Anthropic SDK" names the domain with one broad concrete action, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; it stops short of listing several specific actions (streaming, tool use, agents, batching), so it is not a 4. Third-person voice, so no voice penalty.

3 / 5

Completeness

It explicitly answers both questions with concrete trigger phrasing: the 'what' ("Build apps with the Claude API or Anthropic SDK") and an explicit 'when' ("TRIGGER when: code imports ... or user asks to use Claude API, Anthropic SDKs, or Agent SDK"), plus negative triggers, matching the top anchor.

5 / 5

Trigger Term Quality

Concrete import strings (`anthropic`, `@anthropic-ai/sdk`, `claude_agent_sdk`) plus natural phrases users would say ("Claude API", "Anthropic SDKs", "Agent SDK") give good keyword coverage, but common synonyms like "Anthropic API" or "Claude SDK" are missing, so it falls short of the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

"DO NOT TRIGGER when: code imports `openai`/other AI SDK, general programming, or ML/data-science tasks" actively disambiguates from adjacent skills, and the trigger set is tightly scoped to Anthropic-specific terms — a clear niche with minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
UnicomAI/wanwu
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.