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.

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, actionable skill body that uses tables and decision trees efficiently and provides clear navigation to per-language details. The main gaps are minor: a little trimmable prose, navigational rather than copy-paste code, and templated references whose target files are not present to verify.

Suggestions

Tighten the Defaults section and drop the 'if any of the model strings look unfamiliar...' reassurance paragraph to reach a leaner token budget.

Add one short copy-paste code example for the most common single-call case so the guidance is executable rather than purely navigational.

Verify or materialize the referenced bundle files (e.g. `{lang}/claude-api/README.md`, `shared/tool-use-concepts.md`) so the progressive-disclosure references resolve to real files.

DimensionReasoningScore

Conciseness

The body is mostly efficient, using tables and a decision tree rather than prose, with only minor over-explanation (e.g., the 'A note: if any of the model strings look unfamiliar...' reassurance and the slightly padded Defaults paragraph). It does not reach anchor 5 because a few tokens could still be trimmed.

4 / 5

Actionability

Provides concrete, executable guidance — exact model ID strings, `thinking: {type: "adaptive"}`, `output_config: {effort: ...}`, beta header names, and a task-to-file reading guide — with minor gaps; it is navigational rather than copy-paste code, so it does not fully reach the copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (numbered language-detection steps 1-5, the 'Which Surface' decision tree, and the 'Should I Build an Agent?' four-criteria checklist with a 'stay at a simpler tier' fallback checkpoint). It lacks the explicit validate->fix->retry feedback loop of anchor 5, and no destructive/batch cap applies.

4 / 5

Progressive Disclosure

Well-organized sections with a clear Reading Guide mapping common tasks to one-level-deep files (`{lang}/claude-api/README.md`, `shared/tool-use-concepts.md`, etc.) and easy navigation. It falls short of anchor 5 because the referenced bundle paths are templated and the actual referenced files are not verifiably present in the bundle.

4 / 5

Total

16

/

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, explicit description that clearly states what the skill does and when to activate it, with well-chosen positive and negative triggers. Specificity of the primary action and synonym/extension coverage are the only minor gaps.

DimensionReasoningScore

Specificity

Names the domain ('Build apps with the Claude API or Anthropic SDK') plus several concrete triggers (imports of `anthropic`/`@anthropic-ai/sdk`/`claude_agent_sdk`, Claude API, Anthropic SDKs, Agent SDK), but the core action verb 'Build apps' is somewhat generic, leaving minor coverage gaps relative to the comprehensive anchor 5.

4 / 5

Completeness

Clearly answers both 'what' ('Build apps with the Claude API or Anthropic SDK') and 'when' with explicit concrete trigger phrases ('TRIGGER when...') and an explicit 'DO NOT TRIGGER when...' exclusion, matching the anchor 5 example.

5 / 5

Trigger Term Quality

Good keyword coverage including package/import names (`anthropic`, `@anthropic-ai/sdk`, `claude_agent_sdk`) and natural terms ('Claude API', 'Anthropic SDKs', 'Agent SDK'), plus negative triggers (`openai`); falls just short of anchor 5 which expects synonyms and file extensions.

4 / 5

Distinctiveness Conflict Risk

The negative-trigger clause carves out openai/other AI SDKs, general programming, and ML/data-science tasks, giving it a clear niche with minimal conflict risk as described in anchor 5.

5 / 5

Total

18

/

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.

Validation16 / 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.