Draft high-signal social posts from real work — auto-researches the current PR, recent commits, or working tree to capture the essence, then writes concise, human, builder-first posts for X/Twitter (and optionally Reddit).

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/tweet/SKILL.md

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 skill is highly actionable with a clear, validated research-to-draft workflow and no concept fluff, but the Constraints section duplicates earlier steps and the validate.py reference path does not match the bundle layout. Tightening redundancy and fixing the script path would raise the two weaker dimensions.

Suggestions

Fix or relativize the validate.py path so it matches the bundled script location (e.g. reference scripts/validate.py relative to the skill root rather than a hard-coded .agents/skills/tweet/... install path).

Remove the redundant Constraints entries that restate Steps 1, 3, and Validation, keeping only constraints that add new information (e.g. 'Do not ask for clarification if enough signal already exists').

Consider moving the rewrite-examples or tone-modes tables into a reference file if the SKILL.md grows further, keeping the body as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and free of concept-over-explanation, but the Constraints section largely restates earlier points ('Always research the real work before drafting', 'Always validate post length', 'Always ask about visuals') which duplicates Steps 1, 3, and Validation — matching 'mostly efficient but includes some... could be tightened'. Not a 3 due to this redundancy; not a 1 because there is no padding explaining things Claude already knows.	2 / 3
Actionability	Provides copy-paste-ready commands ('git diff --stat', 'git log --oneline -20', 'gh pr view --json ...'), concrete validate.py invocations, and four before/after rewrite pairs — matching 'fully executable code/commands; specific examples; copy-paste ready'. Not a 2 because guidance is concrete and complete rather than pseudocode.	3 / 3
Workflow Clarity	A clear Step 1–4 sequence (gather → extract essence → ask visuals → draft) is followed by an explicit Validation section with a feedback loop ('If a draft exceeds the tweet limit, tighten it'), matching 'clear sequence with explicit validation steps; feedback loops'. Not a 2 because checkpoints are explicit, not merely listed.	3 / 3
Progressive Disclosure	Sections are well-organized and the only external reference is the one-level-deep validate.py script, but the referenced path '.agents/skills/tweet/scripts/validate.py' does not match the actual bundle location (./scripts/validate.py), so the reference is not cleanly signaled against the real bundle structure — matching 'references present but not clearly signaled'. Not a 3 because the path mismatch undermines clean navigation; not a 1 because there is no deep reference nesting.	2 / 3
	Total	10 / 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 specific and clearly niche-scoped, but lacks an explicit 'Use when...' trigger clause and misses common natural phrasings like 'tweet' or 'thread'. Adding explicit trigger guidance would lift the two capped dimensions.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks to tweet/post about their work, write a release or PR announcement, or share what they just built on X/Twitter or Reddit.'

Surface natural trigger terms users actually say — 'tweet', 'thread', 'ship of theseus / launch tweet', 'post about my PR' — alongside 'social posts'.

Drop or soften jargon like 'high-signal' and 'builder-first' in favor of plain phrasing that a user would naturally utter.

Dimension	Reasoning	Score
Specificity	Quotes 'Draft high-signal social posts', 'auto-researches the current PR, recent commits, or working tree', and 'writes concise, human, builder-first posts for X/Twitter (and optionally Reddit)' list multiple concrete actions (research, essence extraction, drafting), matching the 'lists multiple specific concrete actions' anchor; it is not a 2 because the actions are comprehensive rather than partial. Voice is third person/imperative (no first/second person), so no penalty applies.	3 / 3
Completeness	The 'what' is clearly stated (research real work then draft posts), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the guidelines completeness caps at 2 ('has what, but when is missing or only implied'). Not a 1 because the what-side is strong and the when is at least implied by 'from real work'.	2 / 3
Trigger Term Quality	Includes 'social posts', 'X/Twitter', and 'Reddit' which are natural, but phrases like 'high-signal' and 'builder-first' are jargon and common variations such as 'tweet', 'thread', or 'post about my work' are missing, matching 'some relevant keywords but missing common variations'. Not a 3 because coverage of natural user phrasings is incomplete.	2 / 3
Distinctiveness Conflict Risk	The niche — turning engineering work (PRs/commits/tree) into builder-first social posts — is clearly distinct and unlikely to trigger for unrelated skills, matching 'clear niche with distinct triggers'. Not a 2 because it is far more specific than generic posting 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: gridaco/grida
Path: .agents/skills/tweet/SKILL.md
Commit: 8d2d05e

Reviewed: 3 days 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.