CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

social-publisher

Agent-driven scheduling and publishing of social media posts across 13 platforms via SocialClaw. Use when the user wants to publish to X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, or Pinterest — or when managing campaigns, uploading media, or monitoring post delivery status.

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, well-sequenced skill body with executable commands at every step, an explicit validation step, and a thoughtful human-approval gate plus untrusted-content handling before publishing. Main gaps are missing error-recovery loops after validation failure, repeated version pins, and the awkwardly placed TweetClaw subsection.

Suggestions

Add a feedback loop after step 4: what to do when 'socialclaw validate' fails (read the error, fix schedule.json, re-validate) before proceeding to apply.

Mention the socialclaw version pin once (e.g., in the Source section) and drop the duplicate in Setup to reduce time-sensitive detail.

Move the 'Optional X/Twitter evidence packet' subsection out of the build-schedule step — e.g., into its own section after Core Workflow or into Related Skills — so the numbered workflow stays uncluttered.

DimensionReasoningScore

Conciseness

The body is efficient — commands, a compact provider table, and short security bullets with no explanations of concepts Claude already knows. It falls short of the score-5 anchor ('every token earns its place') due to repeated time-sensitive version pins ('socialclaw@0.1.12' appears twice, 'openclaw plugins install npm:@xquik/tweetclaw@1.6.31') that the guidelines say should penalize conciseness outside a deprecation section, plus the tangential TweetClaw evidence-packet paragraph.

4 / 5

Actionability

Every step is copy-paste ready: 'socialclaw accounts list --json', 'socialclaw assets upload --file ./image.png --json', a complete schedule.json example with expected outputs ('→ { "run_id": "..." }'). This matches the score-5 anchor — fully executable commands covering the common cases — and exceeds score 4, which allows minor gaps.

5 / 5

Workflow Clarity

The six-step Core Workflow has a clear sequence with an explicit validation checkpoint (step 4 'Validate before publishing') and a strong approval gate before apply ('show the user every post... and get explicit approval'). It stops short of the score-5 anchor, which requires feedback loops for error recovery — there is no 'if validation fails, fix and re-validate' instruction.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so all content lives in a single well-sectioned SKILL.md at overview level, with nothing that clearly demands a separate file. It matches the score-4 anchor ('good structure; most content appropriately placed; minor organization gaps') rather than 5 because the 'Optional X/Twitter evidence packet' subsection sits oddly inside the build-schedule step and slightly breaks the otherwise clean navigation.

4 / 5

Total

17

/

20

Passed

Description

92%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: concrete actions, an explicit and specific 'Use when...' trigger clause, and a distinct multi-platform publishing niche anchored to a named tool. The only gap is synonym coverage ('Twitter', 'social media', 'schedule a post') that would make triggers fully comprehensive.

Suggestions

Add common synonyms to the trigger list — e.g. 'or Twitter' alongside X, and phrases like 'schedule posts' or 'post to social media' — to lift trigger term coverage to fully comprehensive.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'scheduling and publishing of social media posts', 'managing campaigns, uploading media, or monitoring post delivery status' — covering the skill's full capability set comprehensively. It matches the score-5 anchor ('Lists multiple specific concrete actions; comprehensive coverage') and is clearly above score 4, which would require minor gaps in coverage.

5 / 5

Completeness

It explicitly answers 'what' ('Agent-driven scheduling and publishing of social media posts across 13 platforms via SocialClaw') and 'when' with a concrete 'Use when...' clause enumerating specific triggers. This matches the score-5 anchor exactly; score 4 would require the 'when' clause to be less explicit or specific.

5 / 5

Trigger Term Quality

Platform names ('publish to X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, or Pinterest') plus 'campaigns', 'uploading media', and 'monitoring post delivery status' give good natural keyword coverage. It falls short of the score-5 anchor ('comprehensive coverage of natural terms including synonyms') because common synonyms like 'Twitter' for X, 'post to social media', or 'schedule a post' as a spoken phrase are absent.

4 / 5

Distinctiveness Conflict Risk

The SocialClaw tool name, 'workspace' scoping, and enumerated platforms establish a clear niche with distinct triggers, matching the score-5 anchor. It is above score 4: overlap risk with a direct X/Twitter API skill is minimal because publishing is explicitly routed 'via SocialClaw' across a multi-platform workspace.

5 / 5

Total

19

/

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

Path

skills/social-publisher/SKILL.md

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.