CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

api-overview

Modern API category — gRPC, SOAP/WSDL, WebSocket, Server-Sent Events. Routing skill: identify the API protocol from the response Content-Type or wire format, then load the matching sub-skill.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/exploit/api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 lean, well-structured routing skill: an efficient protocol table, executable fingerprint commands for all four protocols, and an explicit identify-then-load workflow with a clean sibling pointer. The only notable gap is that the four sub-skills it routes to are named without any load path or command, which slightly weakens both actionability and navigation. It scores highly on conciseness and workflow clarity with no padding or concept over-explanation.

Suggestions

Show the load mechanism for the four sub-skills, e.g. a `load_skill("/skills/api/grpc/SKILL.md")`-style path in the table or one example line, so the routing action is fully executable end-to-end.

Add the concrete sub-skill paths (or a one-line note on where they live) so navigation to the core targets is as explicit as the sibling REST/GraphQL pointer.

DimensionReasoningScore

Conciseness

The ~35-line body is lean and dense: a compact sub-skill table with wire signatures, four short fingerprint commands with minimal comments, and a two-line sibling pointer. It assumes Claude's competence, explains no background concepts, and every token earns its place — matching the top anchor rather than the 'minor trimming' level below.

5 / 5

Actionability

The 'Quick fingerprint' section provides concrete, copy-paste-ready curl commands covering all four protocols (e.g. `curl -sk -I --http2 https://target/svc | grep -i 'application/grpc'`, the ?wsdl probe, the 101 upgrade check). The gap keeping it below fully-executable: the four sub-skills the routing table points to are named but no load path or command is given for them — the `load_skill(...)` pattern is only demonstrated for the sibling REST/GraphQL skill.

4 / 5

Workflow Clarity

This is a simple single-purpose routing skill, and the single action is unambiguous: 'Identify the API protocol then load the matching sub-skill', backed by concrete identification commands per protocol. The routing table plus fingerprint makes the identify-then-load sequence explicit; the destructive/batch validation cap does not apply since no risky operations are involved.

5 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections (Sub-skills, Quick fingerprint, Sibling skills) and the one external reference (`load_skill("/skills/standard/exploit/web/SKILL.md")`) is a clearly signaled one-level path. However, the four sub-skills — the skill's core navigation targets — are referenced by name only, with no paths or load commands, a minor organization gap against the clear-navigation top anchor.

4 / 5

Total

18

/

20

Passed

Description

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

The description clearly states what the skill does (identify API protocol from Content-Type/wire format, then load the matching sub-skill) and names its four protocols with good natural trigger terms. Its main weakness is the missing 'when to use' clause — 'when' is only implied by protocol names — and only two concrete actions are stated. Adding an explicit 'Use when...' clause with common variations (SSE, streaming) would raise completeness and trigger coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the target exposes gRPC, SOAP/WSDL, WebSocket, or Server-Sent Events endpoints, or when the user mentions these protocols' — this directly addresses the missing 'when' that caps completeness at 3.

Include common trigger variations and synonyms such as 'SSE', 'server-push streaming', and 'HTTP/2 RPC' to move trigger term coverage from good to comprehensive.

Optionally add one more concrete action (e.g. 'fingerprint the protocol with curl') so the capability list reads as several specific actions rather than two.

DimensionReasoningScore

Specificity

Names the domain (gRPC, SOAP/WSDL, WebSocket, Server-Sent Events) and two concrete actions ('identify the API protocol from the response Content-Type or wire format', 'load the matching sub-skill'), which matches the anchor for domain plus 1-2 concrete actions. It does not list several specific actions, so it falls short of the level above.

3 / 5

Completeness

The 'what' is clear (a routing skill that identifies the API protocol then loads the matching sub-skill), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'when' is only weakly implied by the protocol names. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

The four protocol names ('gRPC, SOAP/WSDL, WebSocket, Server-Sent Events') are natural terms users would say when they need this skill. Common variations and synonyms such as 'SSE', 'streaming', or file/extension forms are missing, so it does not reach comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The four named modern protocols form a clear, mostly distinct niche separate from REST/GraphQL skills, with distinct triggers. However, the opening phrase 'Modern API category' is broad and could overlap with general API-related skills, preventing a minimal-conflict score.

4 / 5

Total

14

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/exploit/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.