CtrlK
BlogDocsLog inGet started
Tessl Logo

review-public-api

Use this skill when the user asks to review a DuckDuckGo Android public API proposal. If given an Asana task URL, first fetch the task and confirm it is an API proposal before invoking — do not invoke just because a URL was paired with "review". Confirmed signals: the task title contains "API Proposal"; the task belongs to project 1212149061863360 (API Proposals); or the description proposes changes to a -api module. Also invoke for any request to review, evaluate, or give feedback on a proposal pasted inline or provided as a file. Covers phrases like "review my API proposal", "is this API design good?", "check my public interface", "I'm about to submit an API proposal". When the user shares Kotlin code, only invoke if the code is explicitly from or intended for a -api module — do not invoke for impl-only changes or general Kotlin questions. IMPORTANT: Always apply these instructions directly — never delegate or summarise.

92

1.08x
Quality

91%

Does it follow best practices?

Impact

94%

1.08x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

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 tight, highly actionable review workflow with a clear step sequence and explicit validation checkpoints, assuming Claude's competence throughout. The only slight gap is progressive disclosure — the long heuristic list is inline rather than split into a referenced file.

Suggestions

Consider moving the H1–H16 heuristic definitions into a referenced HEURISTICS.md so the SKILL.md body reads as the overview workflow, leaving the core steps and tone guidance inline.

Trim or compress the ASCII diagram template (Step 3) to the minimum scaffold needed, since the surrounding prose already describes each element to include.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence (no explanations of what an API or module is), with tight heuristic definitions; the generous ASCII diagram template and a few bad/good examples are minor extras that mostly earn their place but keep it just short of fully lean.

4 / 5

Actionability

Concrete, executable guidance throughout — exact Asana opt_fields, a copy-paste-ready diagram template, per-heuristic bad/good Kotlin examples, exact module placement rules, and an enumerated exceptions list — fully actionable for an instruction-only skill.

5 / 5

Workflow Clarity

A clear 7-step sequence with explicit validation checkpoints (Step 2's stop-and-ask on unresolved module locations, "Do not proceed...") and a Step 1 understanding checklist; the operation is read-only analysis so the destructive-cap does not apply.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references, but the 16 inline heuristics are substantial content that could optionally live in a one-level-deep reference file; structure is good with a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

95%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 highly specific, well-scoped description that cleanly answers what, when, and how to disambiguate, with strong natural trigger phrases and explicit boundary guidance. Voice is third person throughout, in line with the rubric.

DimensionReasoningScore

Specificity

Names the domain (DuckDuckGo Android public API proposals) and several concrete actions — fetch the Asana task, confirm it is an API proposal via explicit signals, review/evaluate/give feedback — though the emphasis is more on when-to-invoke than a comprehensive action list.

4 / 5

Completeness

Explicitly answers both what (review/evaluate/give feedback on a DuckDuckGo Android public API proposal) and when ("Use this skill when the user asks to review...", "Also invoke for any request to review, evaluate, or give feedback...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Quotes multiple natural phrases users would say ("review my API proposal", "is this API design good?", "check my public interface", "I'm about to submit an API proposal") plus synonyms review/evaluate/feedback, giving comprehensive coverage.

5 / 5

Distinctiveness Conflict Risk

Clear niche anchored to -api modules and a specific Asana project ID, with explicit anti-triggers (do not invoke for impl-only changes or general Kotlin questions), yielding minimal conflict risk.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
duckduckgo/Android
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.