crosspost

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/crosspost/SKILL.md

Quality

Content

75%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.

A well-structured, lean instruction skill with a clear workflow, concrete per-platform guidance, security handling for untrusted source material, and a closing quality gate. The main gap is the lack of an explicit pre-publish confirmation/validation loop for what is fundamentally a batch, hard-to-reverse outward-facing operation.

Suggestions

Add an explicit pre-publish checkpoint to the workflow (e.g. 'Before posting: confirm target accounts and timing with the user; treat publication as irreversible') to turn the Quality Gate into a true validate→fix→retry feedback loop.

Tighten the platform rule lists by deduplicating the repeated 'keep it concise/readable/direct' cadence into a single shared constraint, then list only what differs per platform.

Dimension	Reasoning	Score
Conciseness	The body is lean throughout — short bullets, no explaining of what X/LinkedIn/Threads are, no library tutorials — and assumes Claude's competence; it is efficient rather than maximally trimmed, with a few list items ('keep it readable and direct', 'preserve the author's cadence') that restate the same idea across platforms.	4 / 5
Actionability	Concrete, specific guidance for an instruction-only skill: explicit tool handoffs ('Run brand-voice first', 'Use content-engine first'), a delete-and-rewrite Banned Patterns list, and per-platform rules like 'lead with the sharpest claim or artifact'; some platform rules remain abstract directives ('keep it compressed') rather than testable criteria, keeping it at 4.	4 / 5
Workflow Clarity	A clear three-step sequence (primary version → voice fingerprint → adapt by platform) plus a terminal 'Quality Gate' that functions as a validation checkpoint before delivery; because this is a batch, outward-facing operation, an explicit pre-publish confirmation/feedback loop would push it to 5, and its absence is the main gap.	4 / 5
Progressive Disclosure	Single-file skill with well-organized, clearly headed sections (When to Activate, Core Rules, Untrusted Source Material, Workflow, Posting Order, Banned Patterns, Output Format, Quality Gate, Related Skills) and no nested references; no bundle files exist to verify, so structure is good but not the exemplar split-file case that defines a 5.	4 / 5
	Total	16 / 20 Passed

Description

75%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.

A solid, third-person description that states both what the skill does and when to use it, with a distinctive multi-platform niche. It falls just short of top marks because the 'when' clause is a single trigger phrase and lacks the natural verb synonyms ('crosspost', 'post everywhere') users would likely say.

Suggestions

Expand the trigger clause to mirror the body's natural phrasing, e.g. 'Use when the user says crosspost, post this everywhere, or wants to distribute a launch/essay/update across social platforms.'

Sharpen the action verbs from 'distribution'/'adapts' toward concrete outcomes (e.g. 'generates platform-specific versions that preserve one voice') for a more specificity-5 phrasing.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete behaviors — 'Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky', 'Adapts content per platform', 'Never posts identical content cross-platform' — but the verbs (distribute, adapt) are slightly more abstract than the rubric's 'extract, fill, merge' exemplars, so it sits just below a 5.	4 / 5
Completeness	Both 'what' (multi-platform distribution + per-platform adaptation + no-identical-copy rule) and 'when' ('Use when the user wants to distribute content across social platforms') are explicitly present; the 'when' is concrete but single-phrased rather than the multi-trigger listing of the 5-anchor example, so 4 rather than 5.	4 / 5
Trigger Term Quality	The single trigger clause 'Use when the user wants to distribute content across social platforms' plus platform names gives good natural coverage, but it omits common verb synonyms a user might actually say (e.g. 'crosspost', 'post this everywhere', 'post to multiple platforms') that appear only in the body.	4 / 5
Distinctiveness Conflict Risk	The named four-platform niche plus 'Never posts identical content cross-platform' carves a clear, distinct trigger space; minor overlap risk remains with the referenced sibling skills (content-engine, brand-voice) which could be confused at the trigger stage.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/crosspost/SKILL.md
Commit: ca185ef

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.