CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

claude-api

Anthropic Claude API patterns for Python and TypeScript. Covers Messages API, streaming, tool use, vision, extended thinking, batches, prompt caching, and Claude Agent SDK. Use when building applications with the Claude API or Anthropic SDKs.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/claude-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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-organized, code-dense reference that is lean and largely copy-paste actionable across the main Claude API features. Its weaknesses are structural and process-oriented: everything is inlined in one file with no progressive disclosure to reference files, and multi-step workflows (notably the Batches API and the agent loop) lack validation and error-recovery checkpoints.

Suggestions

Split advanced sections (vision, extended thinking, Batches API, Claude Agent SDK, cost optimization) into clearly signaled one-level-deep reference files (e.g., references/batches.md, references/agent-sdk.md), keeping SKILL.md a lean overview with quick-start examples.

Add validation and error-recovery checkpoints to multi-step workflows: check per-request batch results for failed/dismissed states before use, handle `stop_reason == "tool_use"` explicitly in the agent loop, and turn the error-handling snippet into a real retry-with-backoff loop.

Move time-sensitive model IDs and aliases into a clearly dated 'Model versions' section (or a deprecated/old-patterns section when they age out) so stale identifiers are easy to spot and update.

DimensionReasoningScore

Conciseness

Prose is minimal and nearly all bulk is executable code ("Cache large system prompts or context to reduce costs", "Process large volumes asynchronously at 50% cost reduction"), assuming Claude's competence. Minor trims are possible — the Agent SDK caveat note and unpinned, time-sensitive model IDs (e.g., `claude-sonnet-4-0`, `claude-3-5-haiku-latest`) that are not placed in a deprecated/old-patterns section — so it is efficient but not perfectly lean.

4 / 5

Actionability

Mostly copy-paste-ready examples: installation commands, basic message creation, streaming, system prompts, a complete tool_use/tool_result round-trip, vision, extended thinking, caching, and batches. The Claude Agent SDK loop terminates in a placeholder ("# ... execute tools and append tool_result messages") and the error-handling block uses a bare `pass` with no retry loop, leaving minor gaps that keep it below fully-executable.

4 / 5

Workflow Clarity

Sequences are shown for tool use, the agentic loop, and batch polling, but validation checkpoints are missing: the Batches API workflow (a batch operation) retrieves results without verifying per-request success/failure states, and the agent loop only breaks on `end_turn` without handling `tool_use` stop reasons or error recovery. Per the rubric, batch workflows without validation cap at 3.

3 / 5

Progressive Disclosure

The single SKILL.md is well-headered but inlines roughly 330 lines of full API reference material (vision, extended thinking, batches, Agent SDK) with no external reference files at all. Structure exists, but content that clearly belongs in separate reference files is inline, matching the anchor for good-but-unsplit organization.

3 / 5

Total

14

/

20

Passed

Description

78%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: it names a distinct niche, enumerates concrete capability areas, and includes an explicit 'Use when' trigger clause in third person without padding. The main improvement space is broader trigger coverage and mentioning the error-handling/cost-optimization guidance the body provides.

DimensionReasoningScore

Specificity

"Covers Messages API, streaming, tool use, vision, extended thinking, batches, prompt caching, and Claude Agent SDK" lists several concrete capabilities with only minor gaps (error handling, cost optimization, and environment setup from the body are not mentioned). It exceeds the 1-2-action anchor but is not fully comprehensive, so 4 fits best.

4 / 5

Completeness

Both a clear multi-item 'what' and an explicit trigger clause ("Use when building applications with the Claude API or Anthropic SDKs") are present. The 'when' could be more specific — it omits cost/latency optimization and API debugging scenarios the skill itself lists under When to Activate — so it sits at 4 rather than 5.

4 / 5

Trigger Term Quality

"Claude API", "Anthropic SDKs", "streaming", "tool use", and "Claude Agent SDK" are phrases users naturally say. A few natural terms are missing (e.g., "call/integrate Claude", the import names `anthropic` and `@anthropic-ai/sdk`), placing it just below comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Anthropic Claude API patterns for Python and TypeScript" carves a clear niche with distinct triggers (Claude API, Anthropic SDKs, Agent SDK); it is unlikely to fire for unrelated skills, matching the minimal-conflict anchor.

5 / 5

Total

17

/

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

valeriibeck-star/claude-skills

Path

skills/claude-api/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.