CtrlK
BlogDocsLog inGet started
Tessl Logo

content-engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/content-engine/SKILL.md
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 tight, opinionated instruction skill: concrete platform rules, an explicit banned-phrase list, and a sequenced repurposing workflow capped by a quality gate. It stays lean and actionable; the main gaps are a missing example transformation, no failure-recovery loop after the quality gate, and some redundant cross-references.

Suggestions

Add one short before/after example (a source claim transformed into an X post and a LinkedIn post) to make the platform adaptation rules concrete.

Extend the Quality Gate with an explicit recovery loop: if any gate item fails, revise the draft and re-check before delivering.

Consolidate the brand-voice guidance scattered across 'Source-First Workflow', 'Voice Handling', and 'Related Skills' into a single section to remove redundancy.

DimensionReasoningScore

Conciseness

Lean imperative bullets with no explanation of concepts Claude already knows, but the brand-voice guidance repeats across three sections ('Source-First Workflow', 'Voice Handling', 'Related Skills') and the Hard Bans partially duplicate the Quality Gate, so not every token earns its place.

4 / 5

Actionability

Concrete, specific instruction-only guidance ('Extract 3 to 7 atomic claims', exact ban phrases to delete, per-platform rules, a deliverables checklist), but no worked before/after example of a draft that would make the guidance fully copy-paste ready.

4 / 5

Workflow Clarity

The Repurposing Flow is a clear 7-step numbered sequence ending in an explicit validation step ('Run the quality gate') backed by a Quality Gate checklist, but there is no explicit fail -> fix -> re-check loop if a gate item fails.

4 / 5

Progressive Disclosure

Well-organized sections with clear headers, one-level references to related skills, and no nested or buried references; content sits appropriately inline for a ~120-line skill, with only minor organizational gaps such as the split brand-voice coverage.

4 / 5

Total

16

/

20

Passed

Description

82%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 description with an explicit 'Use when' clause, natural trigger terms, and a distinct niche. The main weakness is that capability coverage is phrased as one broad action over a platform list rather than several distinct concrete actions.

Suggestions

Enumerate the concrete operations (e.g., 'draft posts and threads, script short-form video, build content calendars, adapt one source asset across platforms') instead of the single phrase 'create platform-native content systems'.

Add common trigger synonyms users would actually say, such as 'repurpose', 'cross-post drafts', or 'launch announcement post'.

DimensionReasoningScore

Specificity

Names the domain and platforms ('platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters') with 1-2 concrete actions ('create... campaigns', 'repurposed'), but does not enumerate several specific operations like the anchor-4 example does.

3 / 5

Completeness

Clearly answers both what ('Create platform-native content systems... repurposed multi-platform campaigns') and when ('Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms') with concrete trigger phrases, matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Includes natural user phrases ('social posts, threads, scripts, content calendars') plus 'repurposed multi-platform campaigns', but misses a few common variations such as 'repurpose', 'LinkedIn post', or 'YouTube script'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — multi-platform social content creation and repurposing — with platform names and repurposing triggers that are unlikely to fire for unrelated skills.

5 / 5

Total

17

/

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.

Validation — 15 / 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.