CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

influencer-discovery

Use when the user asks to "find influencers", "build an influencer list", or "discover creators in [niche]"; produces a multi-platform candidate pool, per-influencer evidence profiles, authenticity red-flag screening, and a Fit-readiness queue without action ranking. Not for STAR scoring or ranking a known shortlist — use fit-scorer. 达人挖掘/找达人/创作者名单

Quality

82%

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

73%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 delivers an exceptionally well-sequenced six-step workflow with explicit stop conditions, refresh loops, and checklists, plus genuinely executable keyless/measured data recipes. Its main cost is token weight: authorization, identity-ref, and no-ranking rules are repeated across sections in very long sentences, and many referenced paths fall outside the shipped bundle, which weakens navigation certainty.

Suggestions

State the creator_ref/identity, exact-authorization, and no-ranking rules once in a single section (or move them to a reference file) instead of repeating them across the Skill Contract, Steps 2, 4-5, and the closing paragraph — this alone would cut a large share of the body's tokens.

Break the ~200-word single-sentence "Writes" bullet into short sub-bullets so each rule (opaque refs, transient-only locators, identity_status handling, registry-event authorization) is scannable instead of buried in a run-on.

Either ship or prune the out-of-bundle references (scripts/connectors/youtube.py and README, skill-contract.md, state-model.md, CONNECTORS.md, star-benchmark.md): each unverifiable link dilutes the otherwise excellent one-level-deep navigation of the three references that do exist.

DimensionReasoningScore

Conciseness

There is no basic-concept filler (no "what is an influencer" padding) and the body is information-dense, but the creator_ref/identity, authorization, and no-ranking rules are repeated nearly verbatim across the Skill Contract, Steps 4-5, and the closing paragraph, and the ~200-word single-sentence "Writes" bullet is a run-on. This matches anchor 3 ("mostly efficient... could be tightened") rather than anchor 4, where over-explanation would be only minor.

3 / 5

Actionability

Concrete copy-paste-ready material is present: keyless oEmbed endpoints per platform, "python3 \"${CLAUDE_PLUGIN_ROOT}/scripts/connectors/youtube.py\" channel @handle" with quota figures ("10,000 units/day; one channel check ≈ 1–3 units"), and verified fill-in step templates in references/templates.md. Not anchor 5: the core search and screening steps rest on ~~connector placeholders and descriptive guidance, and the worked example is summarized rather than shown inline.

4 / 5

Workflow Clarity

Six numbered steps are clearly sequenced with explicit validation checkpoints and feedback loops: "If any required criterion is missing, stop with NEEDS_INPUT", stale/unknown fields force "triage_state: NEEDS_REFRESH, ranking_status: NOT_RANKED, and NEEDS_INPUT" until refreshed, plus a "Done when" checklist and termination chain rules. This matches anchor 5's explicit validation steps, error-recovery loops, and checklists; despite being a batch-style operation, validation is pervasive so no cap applies.

5 / 5

Progressive Disclosure

The three local references (templates.md, platform-vetting.md, creator-dossier.md) are real, one level deep, and well-signaled with what/when descriptions, and templates.md verifiably contains all six step blocks and the worked example. Not anchor 5: six-plus referenced paths lie outside the bundle and are unverifiable here (scripts/connectors/youtube.py, scripts/connectors/README.md, ../../../references/skill-contract.md, state-model.md, CONNECTORS.md, star-benchmark.md, sibling SKILL.mds), and a large share of contract detail is inlined in SKILL.md that could live in a reference.

4 / 5

Total

16

/

20

Passed

Description

87%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 explicitly answers both what and when with concrete, naturally-spoken trigger phrases, adds a rare explicit negative boundary pointing to the sibling scorer skill, and includes bilingual synonyms. The only weaknesses are internal family jargon ("Fit-readiness", "STAR") and a few missing common trigger variations such as "KOL" or "creator research".

DimensionReasoningScore

Specificity

"produces a multi-platform candidate pool, per-influencer evidence profiles, authenticity red-flag screening, and a Fit-readiness queue without action ranking" lists several concrete deliverables, matching anchor 4. It falls short of anchor 5 because internal jargon ("Fit-readiness", "STAR scoring") slightly obscures the capability for a reader outside this skill family.

4 / 5

Completeness

Both what ("produces a multi-platform candidate pool... Fit-readiness queue") and when ("Use when the user asks to 'find influencers'...") are explicit with concrete trigger phrases, matching the anchor-5 example. It even adds an explicit when-not-to-use boundary, which the anchor example lacks.

5 / 5

Trigger Term Quality

Quoted natural triggers "find influencers", "build an influencer list", "discover creators in [niche]" plus bilingual synonyms "达人挖掘/找达人/创作者名单" give good keyword coverage, matching anchor 4. Not anchor 5: common variations such as "KOL", "creator research", "brand ambassadors", or platform-specific phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

"Not for STAR scoring or ranking a known shortlist — use fit-scorer" is an explicit disambiguation boundary, and "without action ranking" separates this from ranking skills. This is a clear niche with distinct triggers and minimal conflict risk, matching anchor 5; anchor 4 would require some residual overlap ambiguity that is not present.

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 23 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 missing, 1 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

influencer/scout/influencer-discovery/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.