api

Find and call Tessl API endpoints. Use this WHENEVER you need a Tessl REST API endpoint — to discover which endpoint does something, to learn an endpoint's path, parameters, request body shape, or response shape, or to actually call the Tessl API. Reach for this skill INSTEAD OF reading the raw `openapi.json` spec.

1.91x

Quality

89%

Does it follow best practices?

Impact

94%

1.91x

Average score across 2 eval scenarios

Securityby

Low

Low-risk findings worth noting

The canonical home for this skill is tessl/api

Quality

Content

96%Scale 1-5

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

This is an excellent skill that efficiently teaches Claude how to discover and call Tessl API endpoints through a helper script. It respects Claude's intelligence, provides fully executable commands at every step, and structures the workflow as a clear escalation path from cheap search to detailed expansion to actual invocation. The only minor weakness is the inability to verify the referenced helper script exists in the bundle.

Dimension	Reasoning	Score
Conciseness	Every section earns its place. No explanation of what an OpenAPI spec is, no tutorial on REST APIs, no padding. The rationale for the helper (deeply nested JSON:API schemas wasting context) is stated in one sentence and is genuinely useful context Claude wouldn't otherwise know. The notes section is tight and non-obvious.	5 / 5
Actionability	Each workflow step includes a concrete, copy-paste-ready shell command. The final 'Call it' step shows a complete tessl api invocation with heredoc JSON body. Flag usage (--expand, --status, --page, --refresh, --by-property) is demonstrated in context rather than described abstractly.	5 / 5
Workflow Clarity	The workflow is a clear escalation sequence: keyword search → property search → show → expand → call. Each step explains when to use it ('if keyword search misses', 'only if the collapsed view isn't enough') and what output to expect. The process is non-destructive (read-only discovery + CLI-authenticated calls), so destructive-operation validation caps don't apply. The 'if your path is ambiguous the script lists the candidates' note serves as a built-in feedback loop.	5 / 5
Progressive Disclosure	The skill itself is well-structured with clear sections (helper, workflow, notes) and appropriately concise for its scope. It references `scripts/tessl_api_discover.py` which is the main supporting file. However, no bundle files were provided to verify the script exists, and there are no references to additional documentation files. For a skill of this size (~80 lines), the structure is good but the lack of verifiable bundle support prevents a 5.	4 / 5
	Total	19 / 20 Passed

Description

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

This is a strong description that clearly communicates both what the skill does and when to use it, with explicit trigger guidance including an anti-pattern ('INSTEAD OF reading the raw openapi.json'). The specificity of capabilities could be slightly improved by listing more diverse concrete actions beyond API discovery and calling, but the description is well-targeted and distinctive.

Dimension	Reasoning	Score
Specificity	Names the domain (Tessl API endpoints) and describes a few concrete actions (discover endpoints, learn path/parameters/request body/response shape, call the API), but the actions are somewhat repetitive and centered around one general capability rather than listing diverse concrete operations.	3 / 5
Completeness	Clearly answers both 'what' (find and call Tessl API endpoints, discover endpoints, learn paths/parameters/body/response) and 'when' (WHENEVER you need a Tessl REST API endpoint, INSTEAD OF reading the raw openapi.json spec). The 'when' clause is explicit and includes concrete trigger scenarios.	5 / 5
Trigger Term Quality	Includes good natural keywords like 'Tessl API', 'REST API', 'endpoint', 'parameters', 'request body', 'response shape', 'openapi.json'. Missing some variations like 'HTTP request', 'API call', or 'swagger', but covers the most likely trigger terms well.	4 / 5
Distinctiveness Conflict Risk	Highly distinctive — specifically targets Tessl API endpoints and explicitly differentiates itself from reading the raw openapi.json spec. The 'Tessl' brand name and the anti-pattern guidance ('INSTEAD OF reading the raw openapi.json') create a clear, unique niche with minimal conflict risk.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: tesslio/product-plugins
Path: api/skills/api/SKILL.md
Commit: 37f0a21

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.