devvit-skill-setup
Configure a repo's agent instruction files (AGENTS.md, CLAUDE.md, etc.) to auto-apply Devvit skill guidance. Trigger phrases: "configure skills", "setup skills", "add devvit docs rule".
83
73%
Does it follow best practices?
Impact
100%
1.29xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/devvit-skills-setup/SKILL.mdQuality
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.
The description is well-structured with clear trigger phrases and a distinct niche, making it easy for Claude to select appropriately. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., what content is added, what rules are configured). Overall it is a solid description that effectively communicates purpose and activation conditions.
Suggestions
Expand the capability description to list specific concrete actions, e.g., 'Adds Devvit development guidelines, API references, and coding conventions to AGENTS.md or CLAUDE.md files.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (repo agent instruction files like AGENTS.md, CLAUDE.md) and describes a general action (configure to auto-apply Devvit skill guidance), but doesn't list multiple concrete actions or detail what 'auto-apply Devvit skill guidance' entails. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure repo agent instruction files to auto-apply Devvit skill guidance) and 'when' (explicit trigger phrases provided). The trigger phrases serve as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases ('configure skills', 'setup skills', 'add devvit docs rule') as well as natural keywords like 'AGENTS.md', 'CLAUDE.md', and 'agent instruction files' that users would plausibly say. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — configuring agent instruction files for Devvit skill guidance. The combination of AGENTS.md/CLAUDE.md configuration and Devvit-specific context makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a functional but somewhat loosely specified skill. Its strengths are clear high-level workflow structure and a useful troubleshooting section. Its weaknesses are the lack of concrete tool usage examples (e.g., specific file read/write commands) and a typo ('a close to the top') that reduces clarity. The actionability could be significantly improved with explicit tool calls or code for file operations.
Suggestions
Add concrete tool call examples for checking and modifying instruction files (e.g., using Read/Write file tools with specific paths) rather than abstract directions like 'Check the repo root'.
Add a verification step after inserting the rule block to confirm it was written correctly (e.g., re-read the file and check for the block's presence).
Fix the typo 'Insert the following skill a close to the top' → 'Insert the following block as close to the top as possible'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary explanation (e.g., 'Does basic setup to make a code repository ready to use devvit skills' restates the title) and the embedded markdown block is somewhat verbose, but overall it's reasonably compact. The troubleshooting section is lean and useful. | 2 / 3 |
Actionability | The skill provides a clear sequence of actions (check for skill, insert rule block, create file if needed) and includes the exact text to insert, but lacks concrete executable commands for file manipulation. Steps like 'Check the repo root for common instruction files' and 'Insert the following skill a close to the top' are directional rather than precise (no specific tool calls, no code examples for reading/writing files). | 2 / 3 |
Workflow Clarity | The three-step workflow is clearly sequenced and includes a validation step (calling devvit-docs to verify configuration), but there's no explicit feedback loop for the file insertion step itself—no verification that the rule block was correctly inserted, and the 'skip' path in step 1 could be clearer about what happens next. The troubleshooting section partially compensates but doesn't constitute inline validation checkpoints. | 2 / 3 |
Progressive Disclosure | For a simple skill under 50 lines with no need for external references, the content is well-organized with clear sections (numbered steps, troubleshooting). The structure is appropriate for the complexity level and easy to navigate. | 3 / 3 |
Total | 9 / 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.