post-forge-feature

Generate a Twitter/X post highlighting a Forge feature. Use when the user asks to write a tweet, create a Twitter post, or promote a ForgeCode feature on social media. The post always accompanies an attached video demonstrating the feature.

Quality

80%

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

78%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, well-structured instruction skill with an appropriate single reference file and a clear approval-gated workflow. The main opportunity is trimming the redundant video explanation and pulling a single example post inline so the body is self-sufficient for drafting.

Suggestions

Remove or tighten the opening sentence about the video ("The post always accompanies a video, so no need to describe every detail; the video does the showing") since the Key Constraints already state the video rule, avoiding mild redundancy.

Add one short inline example post (or a one-line structure template) so the body gives executable drafting guidance without requiring a round-trip to the style guide.

Make the approval step an explicit feedback loop, e.g. "If tweaks are requested, revise and re-present before finalizing," to strengthen the workflow's validation path.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with no padding of known concepts, but the opening video justification ("so no need to describe every detail; the video does the showing") partly restates the later constraint and could be trimmed, keeping it just short of a 5.	4 / 5
Actionability	Concrete constraints (2-3 sentences, ~280 chars, no em dashes, lead with benefit, end with hashtag) and a clear workflow give actionable guidance, but example posts and the structure template are delegated to the reference rather than covered inline, a minor gap.	4 / 5
Workflow Clarity	A clear 3-step sequence (understand, craft, present for approval) with an explicit approval checkpoint; it lacks an explicit revise-and-re-present feedback loop or inline checklist, which keeps it below 5.	4 / 5
Progressive Disclosure	SKILL.md is a well-organized overview with clearly signaled one-level-deep references; references/style-guide.md exists and holds the promised tone, vocabulary, hashtag, and example content, so navigation is easy.	5 / 5
	Total	17 / 20 Passed

Description

82%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 clearly answers both what the skill does and when to trigger it with natural user phrasing, and it carves out a distinct niche. It is slightly light on enumerating multiple concrete capabilities, which keeps specificity at the midpoint.

Dimension	Reasoning	Score
Specificity	Names the domain (Twitter/X post) and one concrete action ("Generate a Twitter/X post highlighting a Forge feature") but offers only a single action rather than comprehensive coverage, matching the 1-2 concrete actions anchor.	3 / 5
Completeness	Explicitly states what it does ("Generate a Twitter/X post highlighting a Forge feature") and when to use it ("Use when the user asks to write a tweet, create a Twitter post, or promote a ForgeCode feature on social media") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ("write a tweet", "create a Twitter post", "promote a ForgeCode feature on social media"); good coverage with a few synonyms (e.g. "thread", bare "X post") missing, so not a 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (ForgeCode feature promotion on Twitter/X) with distinct, product-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 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: tailcallhq/forgecode
Path: .forge/skills/post-forge-feature/SKILL.md
Commit: 6ed5d37

Reviewed: 24 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.