CtrlK
BlogDocsLog inGet started
Tessl Logo

rest-client-not-found-detection

Use when a REST-backed resource (SCIM group/user, Grafana) fails to soft-delete on 404, or when cxsdk.Code returns Unknown for a status.Error from rest/client.go.

67

Quality

80%

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

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

An exceptionally concise, actionable single-purpose skill that gives executable code and explicitly warns against the matching trap. Its only gap is the absence of an explicit verification step to confirm the not-found branch now fires on a real 404.

DimensionReasoningScore

Conciseness

The body is extremely lean: a single header, Trigger/Fix/Why/Trap sections, and a minimal code block, with every token earning its place and no padding explaining concepts Claude already knows.

5 / 5

Actionability

It gives copy-paste-ready Go for both the client return and the call site, plus the exact API pair (status.Error / status.Code), covering the common case directly.

5 / 5

Workflow Clarity

The Trigger, Fix, Why, and Trap structure gives a clear sequence (identify -> fix -> understand -> avoid the pitfall), but there is no validation or verification step to confirm the 404 branch actually runs after the change.

4 / 5

Progressive Disclosure

For a simple single-purpose skill under 50 lines with no need for external references, the well-organized labeled sections (Trigger/Fix/Why/Trap) fully satisfy progressive disclosure without any bundle files.

5 / 5

Total

19

/

20

Passed

Description

67%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 tight, codebase-specific description that pairs concrete trigger symptoms with the relevant error-handling mismatch. It is clear and distinct but somewhat narrow in natural keyword coverage and uses third person appropriately throughout.

Suggestions

Add natural-language synonyms a user would actually say ('REST client', 'not-found error', '404 handling') alongside the internal symbol names.

Loosen the trigger to apply beyond the exact internal file path so the skill is discoverable without prior knowledge of rest/client.go.

DimensionReasoningScore

Specificity

The description names the concrete resources (SCIM group/user, Grafana) and a precise code symptom ('cxsdk.Code returns Unknown for a status.Error from rest/client.go'), but only sketches one action pair rather than listing several specific actions.

4 / 5

Completeness

It explicitly answers both what (detect 404 soft-delete failures / unknown status codes) and when ('Use when a REST-backed resource fails to soft-delete on 404, or when cxsdk.Code returns Unknown'), though the when clause is narrowly tied to internal code paths.

4 / 5

Trigger Term Quality

It surfaces real tokens users would say ('SCIM group/user', 'Grafana', '404', 'soft-delete'), but it leans on internal symbols (cxsdk.Code, rest/client.go) and omits natural synonyms like 'REST client' or 'not-found handling'.

3 / 5

Distinctiveness Conflict Risk

The niche is quite specific (bare status errors from a hand-rolled REST client vs SDK gRPC clients), making collision with unrelated skills unlikely, though it presupposes a particular codebase context that limits general trigger clarity.

4 / 5

Total

15

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
coralogix/terraform-provider-coralogix
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.