CtrlK
BlogDocsLog inGet started
Tessl Logo

release-changelog-discord-message

Write the Discord announcement for a stable Paperclip release from the release changelog. Use when a release issue needs a copy-pasteable dotta-voice Discord post or refreshed discord_announcement document.

72

Quality

88%

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

77%

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

The body is highly actionable and the workflow is clearly sequenced with validation checkpoints, but it carries significant token weight from three full inlined verbatim example announcements. Pulling the examples into a references file and keeping one inline would improve both conciseness and progressive disclosure without losing the voice ground-truth.

Suggestions

Move two of the three verbatim example announcements into a references file (e.g. references/examples.md) and keep one inline as the canonical voice sample, reducing body length and improving progressive disclosure.

After extracting examples, verify the remaining prose stays tight — the Language tips and Format sections are already lean, so preserve them as-is rather than summarizing.

Consider a one-line pointer near the 'Verbatim previous examples' section noting that the canonical examples now live in the references file, so the voice ground-truth remains discoverable.

DimensionReasoningScore

Conciseness

The prose sections (Output, Format, Language tips, Workflow, Review checklist) are lean and directive and assume Claude's competence, but three full verbatim example announcements (~190 lines) make the body heavy; trimming to two examples with a pointer would tighten it without losing the voice reference.

2 / 3

Actionability

Provides complete, copy-paste-ready API request bodies for document and case upserts, a fill-in template, an emoji-code mapping, explicit guardrails, and verbatim ground-truth examples — fully executable guidance rather than vague direction.

3 / 3

Workflow Clarity

An 8-step numbered workflow with a closing review checklist and a baseRevisionId fetch-then-update gate that prevents silent overwrites, giving explicit validation checkpoints for the document/case upsert operations the rubric flags as risky.

3 / 3

Progressive Disclosure

Sections are clearly signaled and well-organized, but the skill is a ~450-line single file with three full verbatim examples inlined that could instead live in a one-level-deep references file, which the anchor treats as content that should be separate being inline.

2 / 3

Total

10

/

12

Passed

Description

100%

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 third-person, concise, and explicitly pairs a concrete capability statement with a 'Use when...' trigger clause covering what and when. It is specific and well-scoped to the release-announcement niche, with minimal conflict risk. No changes needed.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Write the Discord announcement', 'from the release changelog', 'copy-pasteable dotta-voice Discord post', 'refreshed discord_announcement document' — matching the anchor that lists several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (write the announcement from the changelog) and when via a clear 'Use when a release issue needs a copy-pasteable dotta-voice Discord post or refreshed discord_announcement document' trigger clause, matching the score-3 anchor exactly.

3 / 3

Trigger Term Quality

Includes natural terms a user or release routine would actually reference — 'release issue', 'Discord post', 'discord_announcement document', 'stable Paperclip release' — giving good coverage rather than only technical jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — the Discord announcement for a stable Paperclip release — explicitly distinguished from the sibling changelog skill and tied to release-issue-specific triggers, making overlap with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
paperclipai/paperclip
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.