CtrlK
BlogDocsLog inGet started
Tessl Logo

desktop-den-sync-review

Flag desktop<->den contract drift introduced by this diff. High findings gate Warden clearance; medium findings are advisory only.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.warden/skills/desktop-den-sync-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is an excellent instruction-only review skill: dense, actionable, and well-sequenced with explicit verification checkpoints and a precise reporting format, with no wasted tokens. The only minor gap is the use of bold lead-ins instead of markdown headers, which slightly hurts navigation.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanation of what a diff, route, or zod schema is); every line states operational rules Claude would not already know, such as repo paths and the Warden-clearance gating model.

5 / 5

Actionability

It gives concrete executable guidance: exact contract-surface paths, an explicit grep-before-reporting instruction, a fixed severity mapping, enumerated HIGH/MEDIUM conditions, and an ordered phased-rollout fix to prescribe per finding.

5 / 5

Workflow Clarity

The review procedure is clearly sequenced with explicit verification checkpoints (grep desktop surfaces before reporting a HIGH, check and address contrary evidence, report nothing for a clean diff) and a structured per-finding reporting checklist including a "Clear when:" condition.

5 / 5

Progressive Disclosure

The single self-contained file is appropriately scoped with no external references needed and clear topical sections, but it uses bold lead-in phrases rather than proper markdown section headers, which slightly reduces scannability and navigation.

4 / 5

Total

19

/

20

Passed

Description

57%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 is distinctive and names a concrete, well-scoped action, but it lacks an explicit "Use when..." trigger clause and relies on internal jargon without natural synonyms, capping completeness and trigger-term quality. Adding explicit trigger guidance and a couple of plain-language synonyms would materially raise the score.

Suggestions

Add an explicit trigger clause, e.g. "Use when reviewing a diff that touches desktop or den API contract surfaces (routes, response fields, request fields, enums, shared den schemas)."

Include natural trigger synonyms users might say, such as "desktop-den API drift", "den route or field removal", or "backward-compatibility check for published desktop builds."

Broaden specificity by naming one or two more concrete actions, e.g. "grep desktop/client surfaces for usage of the changed route or field and prescribe a phased rollout fix."

DimensionReasoningScore

Specificity

The description names the domain and one concrete action ("Flag desktop<->den contract drift introduced by this diff") but offers only a single action plus severity-gating behavior, so it is not comprehensive enough for a 4.

3 / 5

Completeness

It states a clear "what" (flag contract drift) but the "when" is only weakly implied by "introduced by this diff", and there is no explicit "Use when..." trigger clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Terms like "contract drift", "diff", and "Warden clearance" are relevant but largely internal jargon, and no natural synonyms or variations a user would actually say are provided.

3 / 5

Distinctiveness Conflict Risk

The desktop<->den contract-drift niche with Warden-clearance gating is highly specific and extremely unlikely to trigger for any other skill.

5 / 5

Total

14

/

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
different-ai/openwork
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.