devvit-docs
Look up Devvit documentation from the reddit/devvit-docs repository. Use when the user asks about Devvit APIs, patterns, configuration, or examples (trigger phrases: "how do I", "devvit docs", "show me the docs", "API reference").
89
84%
Does it follow best practices?
Impact
98%
2.22xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent completeness and distinctiveness. It clearly identifies when to trigger and targets a very specific niche (Devvit documentation). The main weakness is that the 'what' portion is somewhat thin — it only mentions 'look up' as an action without elaborating on specific capabilities like searching code examples, explaining API usage, or finding configuration patterns.
Suggestions
Expand the capability description with more specific actions, e.g., 'Look up and explain Devvit APIs, find code examples, retrieve configuration patterns, and search documentation from the reddit/devvit-docs repository.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Devvit documentation from reddit/devvit-docs) and one action (look up documentation), but doesn't list multiple concrete actions like searching, extracting code examples, or explaining API patterns. | 2 / 3 |
Completeness | Clearly answers both 'what' (look up Devvit documentation from the reddit/devvit-docs repository) and 'when' (explicit 'Use when' clause with specific trigger phrases and topic areas). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'Devvit APIs', 'patterns', 'configuration', 'examples', plus explicit trigger phrases like 'how do I', 'devvit docs', 'show me the docs', 'API reference' — these are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific repository (reddit/devvit-docs) and a specific platform (Devvit). Very unlikely to conflict with other documentation or coding skills due to the narrow niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that provides clear, actionable instructions for looking up Devvit documentation. Its main strengths are token efficiency and concrete executable guidance with a well-defined output schema. The primary weakness is the lack of explicit validation/error-handling steps in the workflow—particularly around verifying the script output before proceeding to search and present results.
Suggestions
Add a validation step after running ensure-docs.cjs: verify that docsRoot exists and contains files before searching, with a fallback action if it doesn't.
Include a brief step for handling the case where the search within docsRoot yields no relevant results (beyond the 'Present Results' bullet), creating a clearer feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what Devvit is, what documentation lookup means, or other concepts Claude already knows. Every section serves a clear purpose—constraints, usage, output schema, troubleshooting—with no padding. | 3 / 3 |
Actionability | Provides concrete, executable bash commands with flags, a specific JSON output schema showing exactly what to expect, and clear examples. The workflow from running the script to citing results is fully specified and copy-paste ready. | 3 / 3 |
Workflow Clarity | The four-step workflow in 'How It Works' is clearly sequenced, and the 'Present Results to User' section provides output guidance. However, there's no explicit validation checkpoint—e.g., what to do if the JSON output is malformed, if docsRoot doesn't exist, or if the search yields no results before presenting to the user. The troubleshooting section partially compensates but doesn't create a feedback loop. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but no bundle files were provided to verify the referenced script path (./scripts/ensure-docs.cjs). The skill is appropriately sized for a single file, but the lack of verifiable references to supporting files (the script itself) limits confidence in navigation accuracy. | 2 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- reddit/devvit-skills
- Commit
8e99162
- 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.