CtrlK
BlogDocsLog inGet started
Tessl Logo

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").

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, actionable, and concise, with a clear multi-step workflow that includes validation and retry feedback. Bundle references are one level deep and clearly signaled.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, never explaining what Devvit, git, or sparse checkout are; each section (constraints, steps, flags, output fields, troubleshooting) earns its place.

3 / 3

Actionability

Provides a fully executable command with documented flags and copy-paste-ready examples (e.g. `node ./scripts/ensure-docs.cjs --force`), and the referenced script exists in the bundle.

3 / 3

Workflow Clarity

An explicit 8-step sequence includes a retry feedback loop (step 6 reruns with `--force`), per-run checkout verification, a fallback (step 7), and a Troubleshooting section covering failure modes.

3 / 3

Progressive Disclosure

A single overview file references one clearly-signaled bundle script (`./scripts/ensure-docs.cjs`, verified present) one level deep, with well-organized sections and no nested referencing.

3 / 3

Total

12

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 strong, concrete description with explicit "Use when" triggers and good natural keyword coverage. The only weakness is that it names a single action (look up docs) rather than enumerating multiple concrete capabilities.

DimensionReasoningScore

Specificity

"Look up Devvit documentation from the reddit/devvit-docs repository" names a concrete domain and one specific action, but lists only a single action rather than multiple concrete actions.

2 / 3

Completeness

Explicitly answers what ("Look up Devvit documentation from the reddit/devvit-docs repository") and when ("Use when the user asks about Devvit APIs, patterns, configuration, or examples") with explicit triggers.

3 / 3

Trigger Term Quality

Includes natural trigger phrases users would say ("how do I", "devvit docs", "show me the docs", "API reference") alongside topic terms like APIs, patterns, configuration, and examples.

3 / 3

Distinctiveness Conflict Risk

"Devvit" is a narrow, specific niche (Reddit's app framework) with Devvit-scoped triggers, making it unlikely to fire for unrelated skills.

3 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
reddit/devvit-skills
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.