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.
90
88%
Does it follow best practices?
Impact
94%
1.08xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Flow/suspend, Result<T>, and KDoc review
Module diagram present
100%
100%
H7: Flow one-shot violation
100%
100%
H12: Boolean for fallible op
75%
33%
H8: Nullable Intent
30%
70%
H10: Missing KDoc
100%
100%
H10: Incomplete KDoc on triggerSync
100%
87%
Structure check
100%
100%
Three-tier feedback
87%
100%
Verdict present
100%
100%
Specific citations
100%
100%
No generic praise
100%
100%
Method naming, feature flag, and privacy review
Module diagram present
75%
100%
H2: Caller-source method names
100%
100%
H3: shouldAttributeInstall decision
75%
100%
H14: Feature flag in API
50%
100%
H15: Privacy-sensitive name
40%
100%
H8: Nullable token return
50%
37%
Three-tier structure
100%
100%
Specific code citations
100%
100%
Verdict present
100%
100%
No generic praise
100%
100%
Actionable fix suggestions
100%
100%
Module boundary, api-to-api dependency, constants placement
Module diagram present
100%
100%
H4: Repository in public API
100%
100%
H13: api-to-api dependency
57%
100%
H11: Constants in impl
100%
100%
Step 6: Anvil/Dagger in -api
100%
100%
Structure check
100%
100%
Three-tier feedback
100%
100%
Specific code citations
100%
100%
Verdict present
100%
100%
No generic praise
100%
100%
adccd8d
Table of Contents
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.