CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

social

When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' 'grow my following,' 'TikTok video,' 'Reels,' 'Shorts,' 'video script,' 'video hook,' 'short-form video,' 'create a reel,' 'social listening,' 'brand mentions,' 'competitor monitoring,' 'top posts to comment on,' 'find people asking for,' 'carousel,' 'slide-by-slide,' or 'document post.' Use this for social content, repurposing, scheduling, video scripts, and listening. Posts avoid AI tells like 'it's not X, it's Y' reveals and broetry. For broader content strategy, see content-strategy. For paid ads, see ad-creative. For earned media, see public-relations.

Quality

90%

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

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 strong, highly actionable body: concrete templates, timing blueprints, and tool names throughout, with well-signaled one-level-deep references and approval/feedback checkpoints in the publishing workflow. The main weaknesses are token efficiency — several sections restate generic social-media knowledge Claude already has and the question lists are duplicated — and a couple of reference-hygiene gaps (one broken nested link, one second-level link).

Suggestions

Trim or move to a reference file the sections that restate knowledge Claude already has (Analytics & Optimization metrics, Quality Comments, Building Relationships, Content Ideas by Situation), keeping only the skill's opinionated specifics inline.

Remove the 'Task-Specific Questions' section or fold it into 'Before Creating Content' — the two question lists substantially overlap.

Fix the broken nested reference: platforms.md points to references/telegram-channels.md, which is not present in the bundle.

DimensionReasoningScore

Conciseness

The high-value sections are dense and non-obvious (hook formulas, the 'No AI Tells' blacklist, content-atom tables, timestamped video structures), but several sections restate knowledge Claude already has: "Metrics That Matter: Impressions, Reach, Follower growth rate", "Quality Comments: Add new insight, not just 'Great post!'", and "Content Ideas by Situation: Document your journey". The 'Task-Specific Questions' section also duplicates the 'Before Creating Content' question list, so the body could be tightened — matching 'mostly efficient but includes some unnecessary explanation'.

3 / 5

Actionability

For an instruction-only skill, the guidance is copy-paste ready: fill-in-the-blank hook templates ("I was wrong about [common belief]."), timestamped video blueprints ("[0-3s] Hook: State the problem... [25-30s] CTA"), concrete caption specs ("MAX 2 lines... 3-5 words per line"), a literal weekly calendar table, and named tools ("Whisper, Descript, or your podcast host's transcription"). Specific examples cover the common cases (posts, threads, carousels, short-form video, repurposing), which is the anchor-5 standard; the few advisory spots ('Test new hooks') are minor relative to the whole.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (6-step podcast workflow, 6-step repurposing workflow, batching checklist) and the publishing workflow has explicit validation checkpoints and a feedback loop: "Create posts as drafts first — the user approves before anything is scheduled. Never auto-publish without an explicit go-ahead" and "Close the loop... feed real engagement data back". It is not a 5 because several other workflows (repurposing, engagement routine) have implicit rather than explicit checkpoints, and steps like "Analyze patterns" are loosely defined — matching 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

The body is well split: eight focused reference files, each signaled with purpose and usage conditions ("For X (Twitter) ranking mechanics... Use it whenever the task involves posting on X"), and all eight referenced paths exist in the bundle. It is not a 5 because of minor organization gaps: platforms.md links to references/telegram-channels.md which does not exist in the bundle, listening.md nests a second-level link to listening-sources-template.md, and some inline sections (short-form video, ~80 lines) arguably belong in references.

4 / 5

Total

16

/

20

Passed

Description

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

An exemplary description: explicit what-and-when structure, an extensive list of natural trigger phrases with synonym coverage, and explicit boundary routing to sibling skills to avoid mis-triggering. Third-person voice is maintained and nothing reads as padded fluff despite the length, since nearly every phrase is a functional trigger.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "creating, scheduling, or optimizing social media content", "social listening and engagement triage", plus repurposing and video scripts — giving comprehensive coverage of the skill's domain. It stays in third person throughout ("When the user wants...", "Use this for..."), so no voice penalty applies; it is not merely at 4 because the action list covers the full workflow (create, schedule, optimize, repurpose, listen) rather than leaving minor gaps.

5 / 5

Completeness

Both halves are explicit: the 'what' ("creating, scheduling, or optimizing social media content... social listening and engagement triage") and the 'when' ("Use when the user mentions..." followed by concrete trigger phrases, plus a summary "Use this for social content, repurposing, scheduling, video scripts, and listening"). This is the anchor-5 pattern of clearly answering what AND when with concrete triggers; it is above 4 because the 'when' is not merely present but itemized.

5 / 5

Trigger Term Quality

Roughly thirty natural trigger phrases users would actually say: "'LinkedIn post,' 'Twitter thread,' 'what should I post,' 'tweet ideas,' 'grow my following,' 'create a reel,' 'top posts to comment on'" — with synonyms covered across platforms ("'TikTok video,' 'Reels,' 'Shorts,' 'short-form video'"). This matches the anchor for comprehensive natural-term coverage including synonyms; a few imaginable variants (e.g. 'Instagram story') are missing but coverage is clearly closer to comprehensive than to 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (organic social content across named platforms) with distinct triggers, and actively routes away conflicts: "For broader content strategy, see content-strategy. For paid ads, see ad-creative. For earned media, see public-relations." Generic words like 'engagement' are embedded in an explicitly social context ("social listening and engagement triage"), keeping conflict risk minimal rather than merely minor.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/social/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.