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

81%

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

87%

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

The content is concise, actionable, and well-structured for a simple single-purpose skill; the main gap is the absence of an explicit verification checkpoint before saving the output.

Suggestions

Add an explicit validation step before saving: confirm the post is under 1800 characters, the release URL is alone on the final line, and no wrapper text was added.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with no padding or explanation of concepts Claude already knows; every line earns its place.

3 / 3

Actionability

For an instruction-only skill it gives concrete, copy-ready guidance: explicit line structure with examples ('Neva vX.Y.Z'), a 4-8 bullet range, a 1800-character limit, and file-output rules.

3 / 3

Workflow Clarity

The 9-step sequence is clearly ordered, but there is no explicit validation checkpoint (e.g. verify the message is under 1800 characters and the URL is on its own line before saving).

2 / 3

Progressive Disclosure

A simple, well-organized skill under 50 lines with clearly labeled Workflow and Output Rules sections and a single clearly-signaled external reference (.codex/shared/release-marketing.md).

3 / 3

Total

11

/

12

Passed

Description

75%

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 clear and complete with an explicit trigger clause and a well-scoped niche, but it describes a single action and its trigger-term coverage is adequate rather than broad.

Suggestions

Broaden trigger terms to natural phrasings a user would say, e.g. 'Use when announcing a Neva release on Discord or posting release notes to a Discord channel'.

Name a second concrete action (e.g. 'format release notes into scannable bullets') to lift specificity toward the multi-action anchor.

DimensionReasoningScore

Specificity

It names one concrete action ('Create a Discord-ready Neva release announcement from a GitHub release payload') but does not list multiple specific concrete actions as the anchor-3 example does.

2 / 3

Completeness

It explicitly states what the skill does and includes an explicit 'Use for official Neva Discord release posts' trigger clause, answering both what and when.

3 / 3

Trigger Term Quality

Relevant natural terms appear (Discord, release, announcement, post) but 'payload' is jargon and common variations a user might say are not well covered.

2 / 3

Distinctiveness Conflict Risk

The Neva-specific Discord release-post niche is distinct and unlikely to trigger for unrelated skills.

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

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.