CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

performance-analyzer

Use when the user asks to "analyze influencer campaign performance", "compare influencers", or "find what content worked"; produces metric scorecards vs target and benchmark, platform/influencer/content rankings, engagement-quality and sentiment reads, conversion-attribution breakdowns, and ranked learnings. Not for dollar-level return math — use roi-calculator. 达人营销效果分析/投放复盘

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/report/performance-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-sequenced, dependency-aware analysis workflow with genuinely concrete anchors (exact connector command, fixed decision vocabulary, real per-step templates) and strong validation discipline. It is held back by duplicated Retro Card gating passages, overlong contract sentences, and a reference web whose out-of-bundle paths are unverifiable and internally inconsistent.

Suggestions

State the Retro Card gating conditions once (e.g., in the Skill Contract) and have Step 8 and the follow-on paragraphs reference that single statement instead of re-deriving it three times.

Fix the STAR benchmark reference inconsistency (link text says references/star-benchmark.md while the href points to ../../../references/star-benchmark.md) and consolidate or prune the out-of-bundle cross-references that cannot be resolved from the bundle.

Break the 60+ word Skill Contract bullets into short scannable sub-bullets so the writes/promotes/done-when rules are readable at a glance.

DimensionReasoningScore

Conciseness

There is no generic-concept padding, but the Retro Card gating conditions are stated three times (Skill Contract "Done when", Step 8, and the following paragraph, which also repeats the "not a STAR/SQS verdict" caveat at line 82), and contract bullets run 60+ words each. This matches 'mostly efficient but could be tightened' rather than anchor 4's 'minor instances of over-explanation', since whole duplicated passages could be cut.

3 / 5

Actionability

Concrete anchors abound: an exact command ("python3 \"${CLAUDE_PLUGIN_ROOT}/scripts/connectors/youtube.py\" videos @creator --limit 20"), an exact save path pattern, per-step pointers to the real references/analysis-templates.md, and a fixed decision vocabulary (renew | retest | retire | unknown). It stops short of anchor 5 because several steps rely on judgment phrasing ("state observed differences", "surface purchase-intent signals") without concrete criteria or worked mechanics.

4 / 5

Workflow Clarity

Eight sequenced steps with an explicit cross-step dependency ("run Step 7 before populating or publishing Step 2 Conversions") and validation fallbacks (Unknown/NEEDS_INPUT/NOT_RANKED, comparability and significance bars) go beyond anchor 4's 'most checkpoints'. It is not anchor 5 because each step is one dense sentence with embedded caveats, which obscures the sequence, and error-recovery loops are implicit rather than spelled out.

4 / 5

Progressive Disclosure

The one in-bundle reference (references/analysis-templates.md, verified present with all eight step templates) is well signaled and one level deep, but 8+ other referenced paths (../../../references/skill-contract.md, measurement-protocol.md, state-model.md, star-benchmark.md, ../../../CONNECTORS.md, ../roi-calculator/SKILL.md, scripts/connectors/README.md) resolve outside the provided bundle and are unverifiable, and the STAR link text (references/star-benchmark.md) contradicts its href (../../../references/star-benchmark.md). Structure exists but navigation is uncertain, matching anchor 3 rather than anchor 4's 'references mostly clear'.

3 / 5

Total

14

/

20

Passed

Description

92%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: explicit quoted trigger phrases, a concrete five-part deliverables list, and a negative routing boundary against roi-calculator. The only gap is coverage of a few natural synonym phrasings (e.g., campaign recap, post-campaign review), which keeps trigger-term quality just below the top anchor.

DimensionReasoningScore

Specificity

"produces metric scorecards vs target and benchmark, platform/influencer/content rankings, engagement-quality and sentiment reads, conversion-attribution breakdowns, and ranked learnings" lists five concrete deliverables spanning the whole analysis flow. This matches the comprehensive-coverage anchor rather than anchor 4, which expects minor gaps in coverage.

5 / 5

Completeness

Both halves are explicit: "Use when the user asks to…" gives concrete trigger phrases, and the "produces…" clause enumerates what the skill does, plus a negative boundary ("Not for dollar-level return math — use roi-calculator"). This clearly matches the anchor requiring explicit what AND when with concrete triggers, not the weaker 'when could be more specific' anchor.

5 / 5

Trigger Term Quality

Explicitly quoted natural triggers — "analyze influencer campaign performance", "compare influencers", "find what content worked" — are phrases users would actually say. It falls between anchors 4 and 5: strong coverage but common variations like "campaign recap", "post-campaign review", or "creator performance" are missing, so it does not reach the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The influencer-campaign-performance niche is distinct and the description actively disambiguates the nearest neighbor ("Not for dollar-level return math — use roi-calculator"), minimizing wrong-skill triggering. It matches the clear-niche/minimal-conflict anchor, not anchor 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

19

/

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: 25 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/report/performance-analyzer/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.