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.

69

Quality

85%

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.

An actionable, well-sequenced skill body with executable commands and an explicit validation step. The main gaps are a verbose optional TweetClaw subsection and a missing validate-fix-retry feedback loop.

Suggestions

Tighten the 'Optional X/Twitter evidence packet' subsection — move the use-case enumeration and credential-storage detail into a reference file or condense to a one-line pointer, keeping only the install command inline.

Add an explicit feedback loop after step 4: 'If validation fails, review the error, fix schedule.json, and re-run `socialclaw validate` before publishing.'

Consider splitting the Supported Providers table and/or the security guidance into a reference file so SKILL.md stays a lean overview, which would push progressive_disclosure toward anchor 5.

DimensionReasoningScore

Conciseness

Mostly lean commands and a compact providers table, but the 'Optional X/Twitter evidence packet' subsection over-explains plugin install, use-case enumeration, and credential storage; fits anchor 4 (efficient with minor trimmable instances) rather than 5.

4 / 5

Actionability

Copy-paste-ready commands cover the full workflow (accounts list/connect, assets upload, validate, apply, status) with complete schedule.json examples and concrete expected outputs, matching the fully-executable anchor.

5 / 5

Workflow Clarity

A clear 6-step sequence with an explicit validation checkpoint (step 4); the batch-operation cap at 3 does not apply because validation is present, but no explicit validate->fix->re-validate feedback loop keeps it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear sections and no nested references; the under-50-line 5-exception does not apply, and the absence of any bundle/reference files leaves it at good-structure anchor 4 rather than the one-level-deep-references anchor 5.

4 / 5

Total

17

/

20

Passed

Description

87%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, well-structured description that clearly states both capability and activation triggers with concrete platform names. Minor improvements would be trimming the 'agent-driven' filler and adding common synonyms like 'Twitter'.

DimensionReasoningScore

Specificity

Lists several concrete actions (scheduling, publishing, managing campaigns, uploading media, monitoring delivery status) across 13 platforms; stops short of anchor 5 because 'agent-driven' is mild fluff and coverage leans on trigger phrasing rather than fully enumerated capabilities.

4 / 5

Completeness

Explicitly answers both what (cross-platform scheduling/publishing via SocialClaw) and when via a concrete 'Use when the user wants to publish to ... or when managing campaigns, uploading media, or monitoring post delivery status' clause.

5 / 5

Trigger Term Quality

Strong natural keyword coverage with platform names plus publish/schedule/manage/upload/monitor verbs; not 5 because common synonyms such as 'Twitter' for 'X' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (multi-platform social publishing and scheduling via a named tool) with distinct platform-specific triggers and minimal conflict risk even against related skills like x-api.

5 / 5

Total

18

/

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.

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.