CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

social-media-content-calendar

Plan multi-platform social campaigns: briefs to posting.

Quality

73%

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 ./optional-skills/creative/social-media-content-calendar/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a tight, well-sequenced procedure for an instruction-only planning skill: every step carries explicit inputs, named tools, and a 'Done when' completion criterion, and publishing is gated behind explicit approval and verification. Its only weaknesses are mild repetition of the handoff caveat and the absence of a worked example of a brief or calendar format.

Suggestions

Add one compact example (a single filled-out post brief or a small calendar table) so the expected output shape for the common case is unambiguous.

State the drafts-vs-handoff boundary once (step 7 or Pitfalls) instead of repeating it in the intro, procedure, pitfalls, and verification checklist.

DimensionReasoningScore

Conciseness

The body is dense and imperative with per-step 'Done when' criteria and no re-explanation of concepts Claude already knows. It earns 4 rather than 5 because the drafts-vs-published handoff caveat is repeated in the intro, step 7, Pitfalls, and Verification and could be trimmed.

4 / 5

Actionability

Concrete instruction-only guidance: enumerated fields per step (objective, audience, cadence, hook, CTA, asset dimensions...), named tools (read_file, web_extract, humanizer, image_generate, xurl), and explicit dispositions (draft / needs review / approved). It misses 5 only because no example brief or calendar layout is shown for the common case.

4 / 5

Workflow Clarity

A clear 7-step sequence with explicit validation checkpoints: step 6's editorial/risk review with dispositions, the 'do not publish from draft' rule, verified read-back of scheduled time and provider post IDs, and a final verification checklist. This matches the top anchor with checklists and explicit checkpoints for a batch operation.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed; the ~58-line instruction-only body keeps everything appropriately inline with well-organized sections (When to Use, Procedure, Pitfalls, Verification) and no nested or buried references. Per the simple-skill guidance, well-organized sections without external references merit the top score.

5 / 5

Total

18

/

20

Passed

Description

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

The description is concise and names a clear domain with third-person action verbs, but it lacks a 'Use when...' trigger clause and omits the natural vocabulary users would say (notably 'social media' itself, 'content calendar', 'schedule posts'). It communicates what the skill does at a high level but would not reliably surface for the queries it targets.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g., 'Use when the user asks for a social media calendar, a content calendar, or to plan, draft, and schedule a multi-platform campaign.'

Include natural trigger terms users actually say: 'social media', 'content calendar', 'schedule posts', and platform names (X/Twitter, LinkedIn, Instagram, TikTok).

Briefly enumerate the concrete capabilities (campaign structure, platform-specific briefs, approvals, publishing verification) instead of the compressed 'briefs to posting'.

DimensionReasoningScore

Specificity

"Plan multi-platform social campaigns: briefs to posting" names the domain and 1-2 concrete actions (planning, briefs, posting) but is not comprehensive, matching the anchor 'Names domain and 1-2 concrete actions'. It falls short of 4 because it does not list several specific actions with only minor gaps.

3 / 5

Completeness

The description clearly answers 'what' (plan multi-platform social campaigns from briefs to posting) but contains no 'Use when...' clause or equivalent trigger guidance, which the rubric explicitly caps at 3. It is not 2 because the 'what' is clear and specific.

3 / 5

Trigger Term Quality

Relevant keywords exist ("social campaigns", "multi-platform", "briefs", "posting") but common natural phrases users would say are missing: "social media", "content calendar", "schedule posts", and platform names. This fits 'Some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

"Plan multi-platform social campaigns" carves a distinct campaign-planning niche separated from single-post platform skills, with only minor overlap risk against closely related platform/publishing skills. It is not 5 because "posting" leaves some ambiguity with direct-posting skills and no explicit boundary is stated.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/creative/social-media-content-calendar/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.