CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl/api

Find and call Tessl API endpoints token-efficiently. Fires whenever an agent needs a Tessl REST API endpoint — to discover which endpoint does something, learn its path/parameters/request-body/response shape, or actually call it via `tessl api`. Searches and renders just the one endpoint you need instead of loading the whole openapi.json into context.

87

1.91x
Quality

94%

Does it follow best practices?

Impact

94%

1.91x

Average score across 2 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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: lean, fully actionable with executable commands at every step, a clear progressive workflow, and a single well-signaled reference that keeps the overview light. No weaknesses to address.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what OpenAPI/JSON:API is or how HTTP works, and every line (helper usage, the 5-step workflow, the notes) earns its place, matching the lean-and-efficient top anchor.

3 / 3

Actionability

Every step ships a concrete, copy-paste-ready command — 'python3 scripts/tessl_api_discover.py search install policy', 'show post /v1/install/policy/evaluate --expand', and a full 'tessl api -X POST … --input -' invocation — fully executable with real flags and pagination params.

3 / 3

Workflow Clarity

A clearly numbered 5-step sequence (search → property search → show → expand → call) with explicit fallback behavior ('if your path is ambiguous the script lists the candidates'); the operation is read-only discovery so no destructive/batch validation loop is required, and the sequence is unambiguous.

3 / 3

Progressive Disclosure

The body is a concise overview that points to a single one-level-deep bundle file (scripts/tessl_api_discover.py, verified to exist) with the exact invocation line, and splits workflow, notes, and helper cleanly into organized sections with no nested-reference chains.

3 / 3

Total

12

/

12

Passed

Description

85%

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, well-scoped description with concrete actions and an explicit when-to-use trigger. The only soft spot is trigger-term coverage, which is narrow to a single phrasing rather than spanning the natural variations a user might say.

Suggestions

Broaden trigger terms beyond 'Tessl REST API endpoint' to natural user phrasings like 'Tessl API call', 'hit a Tessl endpoint', or 'look up the Tessl API' to raise trigger-term coverage.

No change needed for completeness or distinctiveness — both already hit the top anchor.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'discover which endpoint does something', 'learn an endpoint's path, parameters, request body shape, or response shape', and 'actually call the Tessl API' — matching the top anchor for listing several specific concrete actions.

3 / 3

Completeness

It explicitly answers both what the skill does and when to use it via the explicit 'Use this WHENEVER you need a Tessl REST API endpoint' trigger clause, matching the anchor that clearly answers what AND when.

3 / 3

Trigger Term Quality

It offers the natural phrase 'WHENEVER you need a Tessl REST API endpoint', but coverage is limited to the single 'Tessl API / REST API endpoint' phrasing with no common user variations, so it sits at 'some relevant keywords but missing common variations' rather than the broad-coverage anchor.

2 / 3

Distinctiveness Conflict Risk

Scoped tightly to the Tessl API with an explicit 'Reach for this skill INSTEAD OF reading the raw openapi.json spec' disambiguator, giving it a clear niche unlikely to trigger the wrong skill.

3 / 3

Total

11

/

12

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.

Reviewed

Table of Contents