CtrlK
BlogDocsLog inGet started
Tessl Logo

release-tweets

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

66

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/release-tweets/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

96%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 a tight, highly actionable instruction skill with explicit validation checkpoints and ready-to-use examples; the only minor gap is that progressive disclosure rests entirely on in-body sections with no external reference structure, which is appropriate but keeps it just off the top mark.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout, with no padding or explanation of concepts Claude already knows; every line ("One joke max", "Put the release/changelog URL at the end", "Count final raw characters before presenting") earns its place.

5 / 5

Actionability

Concrete, executable guidance throughout: exact character budgets (280, 160-220), a format template, named tooling (pbcopy, bird/xurl), and three copy-paste-ready example tweets covering launch, beta, and hotfix cases.

5 / 5

Workflow Clarity

Sequenced grounding → shape → variants → threads → posting flow with an explicit Quality Pass validation checklist (char count, exact version, no unverified claims) and verification steps (verify posted URL, count chars before presenting).

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and easy navigation; at ~100 lines it exceeds the under-50 simple-skill threshold, so it sits just below a 5 rather than qualifying for the auto-5.

4 / 5

Total

19

/

20

Passed

Description

62%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 specific and distinctive about its release-tweet niche, but it lacks an explicit 'Use when' trigger clause and relies on a single trigger term, omitting the synonyms the body later introduces.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases like 'release tweet', 'launch tweet', 'X announcement', or 'release thread'.

Include common synonyms/file-channel terms in the description (e.g., 'X/Twitter announcement', 'social copy', 'changelog-to-tweet') to broaden trigger-term coverage.

Expand 'draft/copy/post' into slightly more concrete verbs (e.g., 'draft, copy, and post release announcements') to lift specificity from 4 to 5.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("draft/copy/post") plus concrete sources ("changelog, tags, npm/appcast, artifacts"), but the verbs are somewhat compressed and generic, leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is clear (draft/copy/post release tweets from release artifacts), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

"Release tweets" is a natural phrase users would say, but the description omits common synonyms and variations (X announcement, launch tweet, thread, social copy) that appear only in the body.

3 / 5

Distinctiveness Conflict Risk

"Release tweets" carves out a clear, narrow niche (social copy for shipped releases) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

15

/

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
steipete/agent-scripts
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.