CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fit-scorer

Use when the user asks to "score this influencer", "rank these creators for our campaign", or "tell me which influencer is the best fit"; produces the typed STAR Suitability (S) read plus a separately labeled campaign-fit ranking without mixing campaign-specific commercial fit into the Suitability read. Not for finding new influencers — use influencer-discovery; not for sending outreach — use outreach-manager. 达人适配度评分/创作者筛选排名

Quality

80%

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 ./influencer/scout/fit-scorer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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 a genuinely rigorous, well-sequenced workflow with explicit validation gates and good externalization of bulky templates, but its token efficiency is poor: core rules are repeated across nearly every section and skill routing is stated three times, which buries the actionable core. Tightening the redundancy would materially raise quality without losing any substance.

Suggestions

State the creator_ref opacity rule and the "commercial matrix never enters the SQS" boundary once in the Skill Contract and reference them from the instruction steps instead of restating both in ~6 sections each.

Merge the overlapping Next Best Skill, Related Skills, and Skill Contract routing lists into a single routing section; competitor-tracker, outreach-manager, influencer-discovery, and audience-mapper are each listed 2–3 times.

Condense the Campaign Retro Card handling (evidence_refs as pointers, hypothesis as zero-weight test constraint) into one short subsection rather than repeating it in the contract, Instructions 1/2/6/7, and the example.

DimensionReasoningScore

Conciseness

Noticeably verbose through pervasive redundancy rather than unfamiliar-concept padding: the creator_ref opacity rule is restated in ~6 places (Skill Contract Reads/Writes/Done-when, Instructions 1 and 8, the example), "never enters the SQS" in ~6, the Retro Card zero-weight rule in ~5, and sibling routing appears in three overlapping sections (Skill Contract, Next Best Skill, Related Skills). Not score 3 because the repetition is pervasive across nearly every section rather than a few tightenable spots, and not 1 because it never explains concepts Claude already knows.

2 / 5

Actionability

Provides mostly concrete, executable guidance: one real command (python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/youtube.py" videos @handle --limit 10), exact save paths (memory/influencer/fit-scorer/YYYY-MM-DD-<topic>.md), exact state labels (Pass/Partial/Fail/Unknown/N/A), a NEEDS_INPUT failure path, and a worked example. Not 5 because the core S1–S10 pass/fail criteria and the actual table layouts live in referenced files outside the bundle and the connector example covers only YouTube, leaving minor gaps.

4 / 5

Workflow Clarity

The 8-step Instructions sequence is clearly ordered (lock identity → freeze evidence → score → qualify controls → record read → build matrix → rank → persist) with explicit validation checkpoints and feedback loops: missing typed fields return NEEDS_INPUT with identity preserved for resume, Unknown prevents a Suitability read, Fail requires qualifying evidence and holds outreach, and saves require exact authorization, plus a "Done when" checklist. Not 4 because there are no material validation gaps; the readability cost of the dense caveats is charged to conciseness, not to the checkpoint structure.

5 / 5

Progressive Disclosure

The bulky table layouts are correctly externalized to the real, well-structured references/scoring-templates.md (verified present, 386 lines matching the body's description), and every reference is listed with a one-line description of its content. Not 5 because ~8 of the referenced paths (star-benchmark.md, skill-contract.md, state-model.md, CONNECTORS.md, scripts/connectors/README.md, and the sibling SKILL.md links) point outside the bundle where they cannot be followed, and the routing content is duplicated across three sections that should be consolidated.

4 / 5

Total

15

/

20

Passed

Description

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

A strong description with exemplary natural-language trigger phrases, explicit when/what coverage, and explicit disambiguation from sibling skills. The main weakness is that the capability statement leans on internal framework jargon ("typed STAR Suitability (S) read") that a general user cannot decode, limiting how concretely the what reads.

DimensionReasoningScore

Specificity

Names the domain and roughly two concrete deliverables ("produces the typed STAR Suitability (S) read plus a separately labeled campaign-fit ranking") but wraps them in internal jargon ("typed STAR Suitability (S) read") and does not list the several specific actions of the anchor-4 example. Not score 2 because the actions named are concrete rather than generic, and not 4 because coverage of what the skill actually does is limited to producing two labeled outputs.

3 / 5

Completeness

Explicitly answers "when" with concrete trigger phrases ("Use when the user asks to 'score this influencer'...") and "what" with the two named outputs and their separation rule. Both halves are explicit with concrete triggers, matching the anchor-5 example pattern; not 4 because the when-clause is maximally explicit rather than merely adequate.

5 / 5

Trigger Term Quality

Includes three quoted natural user phrasings ("score this influencer", "rank these creators for our campaign", "tell me which influencer is the best fit") covering the score/rank/best-fit verbs, plus influencer/creator synonyms and a bilingual trigger tail. Comprehensive natural-term coverage with synonyms; only marginal variations like "compare" or "evaluate" are absent, which does not drop it below the anchor-5 bar.

5 / 5

Distinctiveness Conflict Risk

States explicit negative boundaries ("Not for finding new influencers — use influencer-discovery; not for sending outreach — use outreach-manager") alongside distinct scoring/ranking triggers, giving a clear niche with minimal conflict risk. Not 4 because the disambiguation against the two most confusable sibling skills is already explicit rather than merely implied.

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: 27 suspicious

Warning

referenced_paths_exist

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

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

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