CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

content-hunter

Use when creating social media content ideas, hunting for viral references, adapting content formulas from other niches/countries, or planning content calendars. Generates hook variations, writes caption drafts, curates cross-niche reference swipe files, scores references with STEPPS framework, produces complete content briefs, and builds weekly posting schedules — all grounded in brand and offer data. Integrates with Brand Studio (positioning, narrative, voice) and Offer Studio (promise, audience psychology). Triggers: 'contenido', 'content', 'ideas de contenido', 'reel', 'carrusel', 'post', 'viral', 'qué publico', 'dame ideas', 'inspiración', 'referencia', 'steal like an artist', 'calendario de contenido', 'qué posteo', 'ideas para Instagram', 'ideas para TikTok', 'content hunting'.

77

Quality

97%

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

SKILL.md
Quality
Evals
Security

Quality

Content

96%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 strong, highly actionable workflow document: five gated phases with explicit validation checkpoints, concrete thresholds, and a genuinely instructive worked example. The main defects are progressive-disclosure leaks — an uncited, conflicting saturation-signals reference and inline hook/arc lists that duplicate reference files — which also cost some token efficiency.

Suggestions

Replace the inline '6 saturation signals' at line 140 with a pointer to references/saturation-signals.md, and reconcile the two lists — the body's signals (competitor usage, hook similarity, engagement drop >40%) conflict with the reference file's signals (engagement decay, copy explosion, CTR decline, negative sentiment, algorithm deprioritization, parody emergence).

Collapse the inline '7 hook types' and '8 content arcs' enumerations to a count plus a pointer to references/virality-frameworks.md sections 2-3, keeping the body as an overview rather than duplicating reference detail.

In Phase 2 Layer 2, add the missing citation to references/saturation-signals.md so the orphaned bundle file is reachable from the SKILL.md navigation path.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific operational rules Claude does not intrinsically know (gates, thresholds, STEPPS/SCAMPER mappings) and avoids explaining general concepts, but it inlines compressed duplicates of reference material: the '6 saturation signals' at line 140, the '7 hook types', and the '8 content arcs' all restate content that lives expanded in references/saturation-signals.md and references/virality-frameworks.md. This fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the score-5 every-token-earns-its-place anchor, but it is well above the noticeably-verbose score-3 anchor.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact tool assignments per phase ('Tools: WebSearch, WebFetch'), specific file paths to read, numeric thresholds ('Only advance references scoring >= 10/18', 'Minimum 5 references from at least 2 different niches AND 2 different countries', 'Apply 2-3 SCAMPER operations per reference (minimum 2)'), an explicit Phase 1 gate ('industry, voice_tone, 2+ pain_points, 1+ platform, 1+ objective'), and a worked end-to-end example with exact Spanish hook text. This matches the 'fully executable... specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

The five phases are explicitly sequenced with mode-detection routing entry points, HARD GATE checkpoints between phases, and validation with feedback loops at every stage: STEPPS threshold filtering, a user-confirmation gate, the 5-check validation with 'If any check fails, apply corrective SCAMPER operation or discard', and a final 10-point checklist. This matches the score-5 anchor (clear sequence, explicit validation, error-recovery loops); no destructive/batch cap applies.

5 / 5

Progressive Disclosure

Structure is good: each phase signals its reference file ('Reference: references/adaptation-engine.md'), all cited files exist and are one level deep. However, references/saturation-signals.md is never cited from the body — its content is instead inlined (with a conflicting signal list) at line 140 — and the hook-type/arc enumerations duplicate references/virality-frameworks.md sections 2-3. These orphaned/duplicated placements fit 'good structure; most content appropriately placed; references mostly clear; minor organization gaps' rather than the score-5 clean-overview anchor.

4 / 5

Total

18

/

20

Passed

Description

96%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.

An excellent description: concrete, comprehensive action coverage paired with an explicit bilingual trigger list and clear Brand/Offer Studio integration context, all in third person. The only weakness is a handful of very generic single-word triggers that could over-fire on unrelated content requests.

Suggestions

Qualify the generic single-word triggers (e.g., 'content', 'post', 'viral', 'inspiración') into phrases that imply idea generation or adaptation (e.g., 'ideas para post', 'contenido viral de referencia') to reduce overlap with sibling content/design skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Generates hook variations, writes caption drafts, curates cross-niche reference swipe files, scores references with STEPPS framework, produces complete content briefs, and builds weekly posting schedules" — with comprehensive coverage of the skill's outputs, matching the 'multiple specific concrete actions; comprehensive coverage' anchor. It exceeds the score-4 anchor because there are no meaningful gaps in the action coverage.

5 / 5

Completeness

It explicitly answers both questions: 'what' via the concrete action list (hook variations, caption drafts, swipe files, STEPPS scoring, briefs, schedules) and 'when' via the opening 'Use when creating social media content ideas, hunting for viral references, adapting content formulas from other niches/countries, or planning content calendars' plus the dedicated Triggers list. Both are concrete and explicit, matching the score-5 anchor.

5 / 5

Trigger Term Quality

The explicit trigger list — 'contenido', 'content', 'ideas de contenido', 'reel', 'carrusel', 'post', 'viral', 'qué publico', 'dame ideas', 'inspiración', 'referencia', 'steal like an artist', 'calendario de contenido', 'qué posteo', 'ideas para Instagram', 'ideas para TikTok', 'content hunting' — comprehensively covers the natural phrases a user (in both Spanish and English) would actually say, including synonyms and platform-specific variants like 'dame ideas' and 'qué publico'. This matches the comprehensive-coverage anchor rather than the score-4 'a few natural terms missing' anchor.

5 / 5

Distinctiveness Conflict Risk

The niche is clear and method-bound (STEPPS/SCAMPER-based cross-niche adaptation grounded in Brand Studio and Offer Studio data), which distinguishes it from generic writing skills. However, bare single-word triggers like 'content', 'post', 'viral', 'reel', and 'inspiración' are broad enough to fire on many content-adjacent requests, creating minor overlap risk with sibling skills — fitting the 'mostly distinct; minor overlap risk' anchor rather than the minimal-conflict score-5 anchor.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alpacapurpura/luana-method

Path

claude/skills/content-hunter/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.