CtrlK
BlogDocsLog inGet started
Tessl Logo

release-discord-post

Create a Discord-ready Neva release announcement from a GitHub release payload. Use for official Neva Discord release posts.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

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

The body is an exemplary lean, actionable instruction skill with a clear workflow and tidy structure. The only gap is a missing explicit verification step before saving the final output.

Suggestions

Add a validation checkpoint before step 9, e.g. verify the message is under 1800 characters and that the release URL sits alone on the final line, retrying if either fails.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or over-explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Provides a concrete message structure, explicit 1800-character limit, tone guidance, and precise output rules including the file-save instruction; fully actionable for an instruction-only skill.

5 / 5

Workflow Clarity

A clear 9-step sequence is present, but there is no explicit validation checkpoint (e.g. verifying character count or grounding before saving) that would catch errors before output.

4 / 5

Progressive Disclosure

Under 50 lines, well-organized into Workflow and Output Rules sections, with a single clearly signaled one-level reference to .codex/shared/release-markdown.md; appropriate for a simple single-purpose skill.

5 / 5

Total

19

/

20

Passed

Description

71%Weight 40%Scale 1-5

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 concise, concrete, and clearly distinguishes the skill with an explicit trigger clause. Its main weakness is trigger-term breadth, missing common synonyms a user might naturally say.

Suggestions

Broaden trigger terms to include natural phrasings like "release notes", "changelog", or "ship announcement" so users searching those terms land on the skill.

Make the when-clause more situational, e.g. "Use when announcing a Neva release in the Discord news channel after publishing a GitHub release."

DimensionReasoningScore

Specificity

Names a concrete action ("Create a Discord-ready Neva release announcement") and the source ("from a GitHub release payload"), listing several specific facets of the transformation with only minor coverage gaps.

4 / 5

Completeness

Clearly states what the skill does and provides an explicit "Use for..." when-clause; the when could be more specific about the triggering situations.

4 / 5

Trigger Term Quality

Includes relevant natural terms like "Discord", "release announcement", and "release posts", but misses common variations such as "release notes", "changelog", or "ship announcement".

3 / 5

Distinctiveness Conflict Risk

Targets a narrow, well-defined niche (Neva Discord release posts from GitHub payloads) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

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
nevalang/neva
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.