CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/crosspost/SKILL.md
SKILL.md
Quality
Evals
Security

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-crafted, lean instruction-only skill: concrete per-platform rules, literal banned-phrase examples, an untrusted-content section, and a quality-gate checklist give it strong actionability and clear workflow. Its residual gaps are minor — a small amount of rule repetition, no worked example of an adapted variant, and workflow steps that assume external skills (brand-voice, content-engine) without fallback guidance.

Suggestions

Add one compact worked example (source line → X variant → LinkedIn variant) to the Output Format section; concrete before/after examples would push actionability toward anchor 5.

State what 'brand-voice' and 'content-engine' return (or the fallback if unavailable) at the workflow steps that invoke them, closing the workflow_clarity gap — e.g. 'if brand-voice is not present, derive a minimal voice profile from the source directly'.

Dedupe the identical-copy rule: it appears as Core Rule 1, in the frontmatter description, and again in the Quality Gate — keeping it in the Core Rules and the Quality Gate alone would trim tokens without losing the constraint.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout — short bullets, no concept explanations Claude already knows, no filler ('keep it compressed', 'do not write fake hyper-casual creator copy'). Minor redundancy keeps it from anchor 5: 'Do not publish identical copy across platforms' appears as Core Rule 1 and is restated in the Quality Gate ('no copy is duplicated verbatim across platforms') and in the frontmatter description. Well above anchor 3 — there is no unnecessary explanation to trim, just repetition.

4 / 5

Actionability

Concrete, executable instruction-only guidance: literal banned phrases to delete ('Excited to share', 'Here's what I learned', 'link in bio'), specific per-platform do/don't rules, a defined output format, and an explicit workflow. Per the rubric's scoring notes, absence of code is not penalized for instruction-only skills. It falls short of anchor 5 only because there is no worked example of an adapted variant or a note on what changed — the guidance covers the rules but not a concrete before/after case.

4 / 5

Workflow Clarity

A clear three-step sequence (pick primary version → capture voice fingerprint via brand-voice → adapt by platform) followed by posting order and an explicit pre-delivery validation checklist ('Before delivering: each version reads like the same author...'). This is not a destructive or batch operation, so the validation cap does not apply. Anchor 4 rather than 5 because the middle steps depend on external skills (brand-voice, content-engine) without stating what they return or what to do if they are unavailable — a minor checkpoint gap.

4 / 5

Progressive Disclosure

A single, self-contained SKILL.md (~110 lines) with well-organized sections, no nested references, and related skills clearly signaled in a dedicated 'Related Skills' section. No bundle files exist (no references/, scripts/, or assets/ directories), so all content lives appropriately in one file. Anchor 4 rather than 5: the body exceeds the under-50-lines simple-skill exception, and the per-platform constraint blocks plus Banned Patterns are candidates that could split into a reference file if the skill grows.

4 / 5

Total

16

/

20

Passed

Description

70%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 strong description: explicit what-and-when structure, named platforms, and natural trigger terms. Its main weakness is that it under-describes the skill's concrete actions and borrows its 'what' partly from another skill (content-engine) rather than stating its own capability list. The 'when' clause is present but could quote the trigger phrases users actually say.

Suggestions

Enumerate 2-3 more concrete actions in the description, e.g. 'Creates platform-specific variants, preserves the author's voice across platforms, and staggers posting order' — this would lift specificity from anchor 3 toward anchor 4-5.

Replace the generic 'across social platforms' trigger with concrete phrases users would actually say, e.g. 'Use when the user says crosspost, post this everywhere, or adapt this for X and LinkedIn'.

Drop or soften 'using content-engine patterns' — it describes an implementation dependency and creates distinctiveness overlap with the content-engine skill rather than describing what this skill itself does.

DimensionReasoningScore

Specificity

Names the domain and all four platforms ('Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky') and gives 1-2 concrete actions ('Adapts content per platform', 'Never posts identical content cross-platform'), but never enumerates what the skill actually does — creating variants, preserving voice, producing an output format. Matches anchor 3: concrete but not comprehensive; it falls short of anchor 4's 'several specific actions' and is clearly above anchor 2's minimal/generic actions.

3 / 5

Completeness

Answers both: the 'what' ('Multi-platform content distribution... Adapts content per platform') and an explicit 'Use when the user wants to distribute content across social platforms' clause, so the missing-trigger cap does not apply. The 'when' is explicit but generic — no concrete trigger phrases like 'crosspost' or 'adapt this for X and LinkedIn' — matching anchor 4 ('when' could be more specific) rather than anchor 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'distribute content', 'cross-platform', 'social platforms', plus all four platform names users would name. A few natural phrases are missing — 'crosspost' itself, 'post this everywhere', 'repost' — so it fits anchor 4 rather than anchor 5's comprehensive synonym coverage, and is well above anchor 3's partial keyword set.

4 / 5

Distinctiveness Conflict Risk

A clear niche — cross-platform adaptation to four named platforms — with distinct triggers, giving minimal conflict with unrelated skills. However 'Adapts content per platform using content-engine patterns' creates minor overlap risk with the closely related content-engine skill, matching anchor 4 rather than anchor 5's 'minimal conflict risk'.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.