release-tweets

Release tweets: draft/copy/post from changelog, tags, npm/appcast, artifacts.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

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

The body is a tight, highly actionable instruction-only skill: concrete formats and character budgets, explicit validation in the Quality Pass, and clean section navigation. It assumes Claude's competence throughout and avoids concept padding.

Dimension	Reasoning	Score
Conciseness	The body is lean and high-signal — tight bullets, no explanation of what tweets/changelogs are, and every line earns its place (e.g. "Tone: high-signal, compact, confident, a little dry when earned. Not corporate.").	3 / 3
Actionability	It gives concrete, executable guidance: exact character caps (under 280; follow-ups 160-220), a specific tweet shape, commands ("use pbcopy on macOS", "prefer the local bird/xurl workflow"), and copy-paste-ready example templates.	3 / 3
Workflow Clarity	The process is phased (Ground The Copy -> Launch Tweet Shape -> special cases -> Threads -> Posting -> Quality Pass) with explicit validation checkpoints: "Count final raw characters before presenting it as ready to post" and the Quality Pass checklist verifying version, URL, and unverified claims.	3 / 3
Progressive Disclosure	The skill is self-contained and well-organized under clear headers with easy navigation; at ~107 cohesive lines there is no content that warrants splitting into separate bundle files, so the single well-sectioned file is appropriate.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 concrete and distinct, naming specific actions and input sources, but it omits an explicit use-when trigger clause and the fuller set of natural trigger terms. Adding a "Use when..." clause with launch/X-announcement/thread phrasings would raise completeness and trigger coverage.

Suggestions

Append an explicit trigger clause such as "Use when the user asks for a release tweet, launch tweet, X/Twitter announcement, or release thread" to satisfy completeness and add common trigger variations.

Expand the trigger terms beyond "Release tweets" to include natural phrasings like "launch tweet", "X announcement", and "social copy" that users are likely to say.

Keep the concrete action list (draft/copy/post) and source list (changelog, tags, npm/appcast, artifacts) as-is, since they already support strong specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	The phrase "draft/copy/post from changelog, tags, npm/appcast, artifacts" lists multiple concrete actions (draft, copy, post) tied to specific input sources, matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	It clearly states what the skill does but lacks any explicit "Use when..." trigger clause, so per the judging guidelines completeness is capped at 2 with the "when" only implied.	2 / 3
Trigger Term Quality	"Release tweets" is a strong natural term and "changelog"/"tags"/"npm/appcast" are relevant, but the description omits common variations a user would say (launch tweet, X announcement, release thread, social copy) that the body itself enumerates.	2 / 3
Distinctiveness Conflict Risk	"Release tweets" plus specific release-artifact inputs carves out a clear niche that is unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: steipete/agent-scripts
Path: skills/release-tweets/SKILL.md
Commit: bb36883

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.