skill-content-pipeline

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/skill-content-pipeline/SKILL.md

Quality

Content

70%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, actionable pipeline with strong validation and error-recovery structure, but it is monolithic and lengthy, inlining extensive template scaffolding that would benefit from being split into reference files.

Suggestions

Move the bulky template scaffolding (Stage 4 anatomy guide format, fill-in-the-blank template, hook library) into reference files under references/ and link to them from SKILL.md to improve progressive disclosure and reduce inline token load.

Remove the redundancy between the ASCII pipeline overview and the per-stage detail, or collapse the overview to a brief stage list pointing into the detailed sections.

Tighten placeholder-heavy tables (e.g., the hook library and pacing tables) to concise schema definitions rather than fully scaffolded rows.

Dimension	Reasoning	Score
Conciseness	Mostly task-relevant templates without explaining concepts Claude already knows, but the ~560-line body is lengthy with redundancy (the ASCII overview restates all six stages that are then re-detailed) and extensive placeholder scaffolding that could be tightened.	3 / 5
Actionability	Provides concrete, copy-paste-ready guidance (security frame wrapper, user prompt templates, output formats, file-naming paths, URL validation rules), though much of it is fill-in placeholder scaffolding rather than fully concrete examples.	4 / 5
Workflow Clarity	Clear six-stage sequence with explicit validation checkpoints (URL validation, fetch-status tracking), error-recovery feedback loops, and a pre-flight checklist; the batch URL fetch includes validation so the batch cap does not apply.	5 / 5
Progressive Disclosure	Section structure and an overview map are good, but the skill is monolithic: ~560 lines of inline template content (output formats, fill-in-the-blank template, hook library) that belongs in separate reference files, and no bundle files exist to offload it.	3 / 5
	Total	15 / 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 conveys a clear purpose and niche but relies on somewhat abstract action verbs and phrases the 'when' as purpose rather than explicit trigger conditions, leaving the most natural user phrasings to the separate trigger field.

Suggestions

Add an explicit 'Use when...' clause listing concrete trigger phrases (e.g., 'Use when the user asks to analyze, deconstruct, or reverse-engineer an article, thread, or post').

Make actions more concrete by naming specific deliverables (e.g., 'generate anatomy guides, hook libraries, and fill-in templates') instead of abstract terms like 'patterns' and 'anatomy'.

Include common user synonyms ('analyze this content', 'break down this post', 'what makes this work') directly in the description rather than only in the trigger field.

Dimension	Reasoning	Score
Specificity	Names the domain (URLs/live pages) and 2-3 actions ('extract patterns', 'extract anatomy', 'reverse-engineer content strategies'), but the action objects are abstract rather than concrete, and coverage is not comprehensive.	3 / 5
Completeness	Provides a clear 'what' but frames the 'when' as purpose ('use to reverse-engineer content strategies from live pages') rather than an explicit 'Use when...' trigger condition, so per the cap guidance it sits at 3.	3 / 5
Trigger Term Quality	Includes relevant keywords (patterns, anatomy, URLs, content strategies, reverse-engineer) but omits the most natural user phrasings ('analyze this article', 'deconstruct', 'break down'), which only appear in the separate trigger field rather than the description.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (content pattern extraction / reverse-engineering content strategies) that is mostly distinct from general research or summarization skills, with only minor overlap risk against adjacent analysis skills.	4 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (590 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: nyldn/claude-octopus
Path: .claude/skills/skill-content-pipeline/SKILL.md
Commit: 6a1fd2b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.