CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-content-pipeline

Extract patterns and anatomy from URLs — use to reverse-engineer content strategies from live pages

56

Quality

63%

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 ./.claude/skills/skill-content-pipeline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete templates, validation rules, and a clearly sequenced workflow including checkpoints and error loops, but it is monolithic and somewhat verbose, keeping all detail inline rather than offloading it to reference files.

Suggestions

Move the large anatomy-guide output template and hook library into a reference file (e.g., references/anatomy-template.md) and link to it, leaving SKILL.md as a lean overview.

Remove or condense the ASCII pipeline diagram since the same stage sequence is immediately restated as headed sections.

Add an explicit merge/validation step between Stage 3's parallel subagents and Stage 4 so conflicting analyses are reconciled before synthesis.

DimensionReasoningScore

Conciseness

Mostly structured and avoids explaining known concepts, but the large ASCII pipeline diagram duplicates the stage list that follows and the verbose fill-in-the-blank template scaffolding could be tightened.

2 / 3

Actionability

Provides concrete, copy-paste-ready prompt templates, explicit output formats, specific validation rules (HTTPS only, no localhost/private IPs, Twitter->FxTwitter, max 2000 chars), and exact artifact save paths.

3 / 3

Workflow Clarity

Six stages are clearly sequenced with arrows, plus explicit validation checkpoints in Stage 1, error-recovery feedback loops, an analysis-conflicts section, and a pre-flight checklist.

3 / 3

Progressive Disclosure

Well-organized into clear sections but monolithic: all content (large anatomy template, hook library) lives inline in one ~560-line file with no bundle files or one-level-deep references to split the detail.

2 / 3

Total

10

/

12

Passed

Description

50%

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 third-person with a clear niche, but it relies on somewhat abstract terms and a general 'use to' clause rather than concrete, natural trigger phrasings, leaving what/when only partially explicit.

Suggestions

Replace abstract terms like 'patterns and anatomy' with concrete actions users would recognize (e.g., 'analyze articles, threads, and newsletters to extract structure, hooks, and persuasion techniques').

Add an explicit 'Use when the user wants to reverse-engineer or study a piece of content, or asks to analyze articles, tweets, newsletters, or LinkedIn posts' trigger clause enumerating common phrasings.

List the supported content types directly in the description to sharpen distinctiveness from generic web-research skills.

DimensionReasoningScore

Specificity

Names the domain and a couple of actions ('Extract patterns and anatomy from URLs', 'reverse-engineer content strategies') but 'patterns and anatomy' is abstract and not a comprehensive list of concrete actions.

2 / 3

Completeness

States what it does and includes a 'use to...' clause, but the trigger guidance is a general purpose statement rather than explicit user-facing trigger situations, leaving the 'when' only partially answered.

2 / 3

Trigger Term Quality

Contains some relevant keywords ('URLs', 'content strategies', 'live pages') but misses natural user phrasings ('analyze this article', 'reverse-engineer this tweet') and leans on jargon like 'anatomy'.

2 / 3

Distinctiveness Conflict Risk

The content-strategy extraction niche is fairly specific, but 'extract patterns from URLs' could still overlap with general web-research or analysis skills.

2 / 3

Total

8

/

12

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

skill_md_line_count

SKILL.md is long (561 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
nyldn/claude-octopus
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.