CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

social-media-content-calendar

Load to plan a social media campaign, build a content calendar, or adapt existing material into post drafts.

Quality

71%

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

Quality

Content

57%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 short, well-structured, boundary-conscious skill body with an excellent draft-state/approval-gate model and commendable restraint about what it will not do. Its executional substance is thin: no calendar template or example, and the workflow that would carry the actual process is a dead reference, leaving the reader with concepts but not a runnable procedure.

Suggestions

Ship workflows/plan-campaign.md in the bundle (or inline a minimal 5-step planning→draft→handoff sequence in SKILL.md), since the body's main workflow currently resolves to a missing file.

Add a concrete example — a sample calendar table row or CSV schema with columns for date, platform, state, and links — so draft production has an executable template.

Remove or relocate the kendex comment scaffolding and provenance/licence text to reduce token overhead that does not aid execution.

DimensionReasoningScore

Conciseness

The core body is lean and assumes competence — "This skill stops at draft handoff. It sends no post, upload, comment or message, and creates no scheduled job" earns its place — but the kendex HTML-comment scaffolding and the Source and licence section are trimmable overhead that does not help execution, matching the level-4 'minor instances that could be trimmed' anchor rather than the every-token-earns-its-place level 5.

4 / 5

Actionability

There is some concrete guidance ("Keep the calendar, claim inventory, copy and asset briefs as Markdown or CSV files", a fully specified draft-state table) but key execution details are missing — no example calendar row or file template, and the main workflow is delegated to "Follow [Plan a campaign](workflows/plan-campaign.md)" which does not exist in the bundle — matching the level-3 'some concrete guidance but incomplete' anchor.

3 / 5

Workflow Clarity

The draft-state lifecycle (draft → needs review → approved) with an approval-gate checkpoint and a re-review rule ("A changed piece returns to `needs review`") provides an explicit validation loop, but the actual step sequence for planning a campaign and producing drafts is only reachable via the missing workflows/plan-campaign.md, so the sequence is present only implicitly with gaps — the level-3 anchor fits better than level 4 (no complete in-body sequence) or level 2 (checkpoints and boundaries are clearly defined).

3 / 5

Progressive Disclosure

The body is well organized into short sections with a clearly signaled one-level reference ("Follow [Plan a campaign](workflows/plan-campaign.md) for campaign planning and draft handoff"), but neither that file nor the referenced LICENSE exists in the bundle, so the primary detailed content is a broken link and navigation fails — better than the buried/inlined reference problems of level 2, but below the level-4 anchor where references actually resolve.

3 / 5

Total

13

/

20

Passed

Description

75%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 concise, third-person description that names three concrete, natural-sounding capabilities with an explicit load-trigger folded into the purpose clause. Its main weaknesses are the absence of a distinct 'Use when...' trigger clause and missing common variations such as platform names or 'repurpose/schedule' phrasing.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a social media campaign plan, content calendar, or wants to turn articles/videos into platform post drafts."

Include common user phrasings and platforms (e.g. "schedule posts", "repurpose content", Instagram/LinkedIn/X) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names three concrete actions — "plan a social media campaign", "build a content calendar", "adapt existing material into post drafts" — which goes beyond the 1-2 actions of a score-3 anchor, but coverage has minor gaps (no mention of platforms, scheduling, or the approval/draft-review capability the body documents), so it falls short of the comprehensive level-5 anchor.

4 / 5

Completeness

The "what" is explicit (plan campaigns, build calendars, adapt material into drafts) and "Load to plan a social media campaign" functions as explicit trigger guidance, so the missing-'Use when' cap at 3 does not apply; however the trigger is folded into a purpose clause rather than a distinct, specific trigger phrase, matching the level-4 anchor where 'when' could be more explicit.

4 / 5

Trigger Term Quality

"social media campaign", "content calendar", and "post drafts" are phrases users would naturally say, giving good keyword coverage; a few natural terms are missing (platform names like Instagram/LinkedIn, "schedule posts", "repurpose content"), which keeps it below the level-5 synonym-and-extension coverage anchor.

4 / 5

Distinctiveness Conflict Risk

The "content calendar" / "post drafts" framing carves a clear niche with distinct triggers, but there is minor overlap risk with closely related social-copywriting and general writing skills (no disambiguating boundary in the description itself), matching the level-4 rather than the minimal-conflict level-5 anchor.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

vanillagreencom/kendex

Path

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