CtrlK
BlogDocsLog inGet started
Tessl Logo

api

Add or modify API endpoints using TypeSpec. Use when adding new API routes, modifying request/response types, or changing the OpenAPI spec.

70

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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

A highly actionable, well-structured skill body with a clear sequenced workflow, explicit validation checkpoints, and excellent progressive disclosure via the rule index. The main weakness is length: some inline code and explanatory prose could be tightened or externalized.

Suggestions

Move the full Go handler template (Step 3) into a reference file and keep only the structural skeleton inline, to reduce token cost on every invocation.

Tighten the konnect.tsp drift paragraph and the ValidationIssue section to bullet essentials; they currently restate surrounding context.

Condense the AIP rule index table to the handful of rules most tasks need, linking to a full index file for the rest.

DimensionReasoningScore

Conciseness

The body is largely dense and actionable, but at ~365 lines with full inline Go templates and explanatory prose (e.g. the konnect.tsp drift paragraph, the ValidationIssue section) some content could be tightened or moved to reference files.

2 / 3

Actionability

Concrete commands ("make gen-api", "make generate"), exact file paths, type-alias blocks, and full Go handler templates make the guidance copy-paste ready; the <domain>/<Resource> placeholders are explicitly justified template parameters.

3 / 3

Workflow Clarity

A clearly sequenced five-step workflow with explicit validation checkpoints (diff openmeter.tsp konnect.tsp to catch drift, "Check that it completes without errors", review generated output) and feedback loops for error recovery.

3 / 3

Progressive Disclosure

The body is a focused overview that delegates detailed standards to a well-signaled, one-level-deep rule index table, plus cross-references to the /api-filters skill and service-patterns docs, with content appropriately split.

3 / 3

Total

11

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 concisely states what the skill does and gives explicit, natural trigger conditions with good keyword coverage. The only soft spot is specificity, which lists a few actions rather than a comprehensive set.

DimensionReasoningScore

Specificity

"Add or modify API endpoints using TypeSpec" names the domain and a couple of actions, but does not enumerate a broad set of distinct concrete actions as the level-3 anchor requires.

2 / 3

Completeness

It explicitly answers both what ("Add or modify API endpoints using TypeSpec") and when ("Use when adding new API routes, modifying request/response types, or changing the OpenAPI spec").

3 / 3

Trigger Term Quality

Covers natural terms a developer would say — "API endpoints", "API routes", "request/response types", "OpenAPI spec", "TypeSpec" — giving good coverage of likely phrasings.

3 / 3

Distinctiveness Conflict Risk

The TypeSpec-based API-editing niche with OpenAPI/TypeSpec-specific triggers is clearly distinct and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
openmeterio/openmeter
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.