devvit-logs
Stream Devvit logs for an installed app (trigger phrases: "devvit logs", "stream logs", "check logs", "show logs"). Requires the user to provide the target subreddit.
74
91%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
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, focused description for a narrow-scope skill. It clearly identifies the action, provides explicit trigger phrases, and specifies a prerequisite. The main weakness is that it only describes a single action, so if the skill has additional capabilities (e.g., filtering logs, searching logs), those are not mentioned.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Devvit logs) and a specific action (stream logs for an installed app), but only describes one action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | Clearly answers 'what' (stream Devvit logs for an installed app) and 'when' (trigger phrases are explicitly listed), plus includes a prerequisite (user must provide target subreddit). The trigger phrases serve as explicit 'Use when' guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases ('devvit logs', 'stream logs', 'check logs', 'show logs') that users would naturally say, providing good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Devvit app logs for a subreddit — with distinct trigger terms that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%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-crafted, focused skill that efficiently teaches Claude how to stream Devvit logs. It excels in conciseness and actionability with concrete commands, clear arguments, and example output. The only notable weakness is the reference to `./scripts/devvit-logs.cjs` without the script being present in the bundle, which slightly undermines progressive disclosure and completeness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose—no unnecessary explanations of what logs are or how CLIs work. The skill assumes Claude's competence and focuses on the specific wrapper behavior and arguments. | 3 / 3 |
Actionability | Provides fully executable commands with concrete arguments, example invocations, and a clear JSON output schema. The examples are copy-paste ready and the arguments are well-documented with specific format examples like `--since=30m`. | 3 / 3 |
Workflow Clarity | For this simple single-task skill, the workflow is clear: ask for subreddit, run the command, present results. The 'How It Works' section provides a clean sequence, and 'Present Results to User' gives explicit guidance on handling edge cases (no subreddit, no logs). The auto-exit after 5 seconds is a smart validation/safety checkpoint for a streaming command. | 3 / 3 |
Progressive Disclosure | The content is well-organized into logical sections (Usage, Output, Troubleshooting), but everything is inline in a single file. The bundle has no supporting files listed, yet the skill references `./scripts/devvit-logs.cjs` which isn't provided in the bundle. For a skill of this size (~60 lines), inline content is acceptable, but the missing bundle file is a concern for completeness. | 2 / 3 |
Total | 11 / 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.