CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean and highly actionable with a clear six-step workflow, but it stops short of an explicit error-recovery loop around validation and keeps all reference material inline in a single file. These two gaps hold it below the top of the scale.

Suggestions

Add a feedback loop after `socialclaw validate`: instruct the agent to review validation errors, fix schedule.json, and re-run validate before proceeding to `apply`, making the validate→fix→retry cycle explicit for this batch publishing workflow.

Make the validation gate explicit in the Core Workflow (e.g., 'Only proceed to publish when validation passes') so the validate→publish boundary is unambiguous.

Move the Supported Providers table and the TweetClaw evidence-packet detail into reference files (e.g., references/PROVIDERS.md, references/TWEETCLAW.md) linked one level deep from SKILL.md so the overview stays lean and navigation is clear.

DimensionReasoningScore

Conciseness

The body is lean and command-driven (bash snippets, a providers table, a schedule.json example) with no concept-explanation filler; it assumes Claude's competence and every major section earns its place.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands (accounts list, assets upload, validate, apply, status) plus a complete schedule.json template, matching the executable-guidance anchor.

3 / 3

Workflow Clarity

The Core Workflow is a clear numbered sequence with an explicit 'Validate before publishing' step, but it lacks a validate→fix→retry feedback loop for a batch publishing operation, which the rubric caps at 2.

2 / 3

Progressive Disclosure

The body is well-sectioned, but at ~123 lines with no bundle files and no one-level-deep references, content such as the providers table and the TweetClaw detail is inline rather than split into reference files, falling short of the split-with-navigation anchor.

2 / 3

Total

10

/

12

Passed

Description

100%

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 concrete, trigger-rich, and complete, naming 13 platforms and several actions with an explicit 'Use when' clause. It is third-person and distinct from neighboring skills, so it scores at the top of the scale.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'scheduling and publishing of social media posts', 'managing campaigns, uploading media, or monitoring post delivery status' — matching the multi-action anchor rather than the vague or partial anchors.

3 / 3

Completeness

Explicitly states what the skill does (scheduling/publishing across 13 platforms via SocialClaw) and includes an explicit 'Use when the user wants to publish...' trigger clause, satisfying both the what and the when.

3 / 3

Trigger Term Quality

Covers natural platform names a user would say ('X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, or Pinterest') plus common action verbs (publish, schedule, upload, monitor), giving broad natural-term coverage.

3 / 3

Distinctiveness Conflict Risk

A clear niche (multi-platform social publishing via SocialClaw) with distinct named-platform triggers makes overlap with other skills unlikely; it is not generic like the lower anchors.

3 / 3

Total

12

/

12

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.

Validation15 / 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.