CtrlK
BlogDocsLog inGet started
Tessl Logo

content-creator-setup

One-time onboarding for the content creator workflow — content pipeline stages, trend expiration, cross-platform cascades, heavy idea parking. After successful setup this skill is excluded from selection until the marker file is deleted.

58

Quality

68%

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-creator-setup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 well-sequenced, highly actionable onboarding workflow with concrete tool calls and clear step structure, held back by some duplicated content and minor template/syntax inconsistencies rather than any structural problem.

Suggestions

De-duplicate the pipeline-stages list — state it once and reference it from AGENTS.md and calibration.md rather than repeating it in prose.

Standardize memory_write argument syntax (use "target:" consistently) and resolve placeholders like "<platforms list>" inline to keep blocks copy-paste-ready.

Add a brief verification step after the initial AGENTS.md write (e.g., memory_read it back) to confirm the project was declared before creating missions.

DimensionReasoningScore

Conciseness

The body is mostly purposeful with concrete code blocks, but the "Their day involves: Morning/Midday/Afternoon/Evening" intro and the repeated pipeline-stages list across the body, AGENTS.md, and calibration.md are padding/duplication that could be tightened.

3 / 5

Actionability

Concrete, copy-paste-ready memory_write and mission_create templates with full content cover the common setup cases, but template placeholders ("<platforms list>", "<today's UTC date>") and inconsistent argument syntax ("target:" vs "target=") are minor execution gaps.

4 / 5

Workflow Clarity

A clear Step 1–6 sequence with an explicit memory_read conditional checkpoint ("If it does, skip to creating the content-pipeline directory"); the setup is non-destructive so no validation cap applies, though there is no explicit verification that writes succeeded before proceeding.

4 / 5

Progressive Disclosure

Well-organized into labeled steps, tables, and code blocks with a single one-level reference to the commitment-setup skill for the full schema; no bundle files exist, and content is appropriately self-contained with minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

58%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 specific and clearly scoped to a content-creator onboarding niche, but it omits an explicit "Use when..." trigger clause and offers limited natural keyword coverage, capping completeness and trigger-term quality.

Suggestions

Add an explicit "Use when..." clause naming natural trigger phrases (e.g., "Use when onboarding a content creator, setting up a publishing pipeline, or configuring cross-platform distribution").

Broaden keyword coverage with synonyms users actually say (e.g., "youtuber", "streamer", "content calendar", "publishing schedule").

Lead with concrete verbs (e.g., "Configures...", "Creates...") instead of feature labels to sharpen the "what".

DimensionReasoningScore

Specificity

Names the domain (content creator onboarding) and several concrete features — "content pipeline stages, trend expiration, cross-platform cascades, heavy idea parking" — giving specific scope rather than generic actions, though they are feature labels more than verb-driven actions.

4 / 5

Completeness

The "what" is clear (one-time onboarding for the content creator workflow), but there is no explicit "when to use" trigger guidance — only a lifecycle note about exclusion after setup — which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

"content creator" is a natural user term, but the description lacks a "Use when..." clause and offers few synonyms or variations users would actually say, leaving common phrasings uncovered.

3 / 5

Distinctiveness Conflict Risk

The content-creator onboarding niche is clearly distinct, with only minor overlap risk against the sibling commitment skills it depends on (commitment-triage, commitment-digest).

4 / 5

Total

14

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
nearai/ironclaw
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.