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

81%

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

67%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-structured, operationally serious skill body: clear step sequence with dependency ordering and decision gates, a real executable connector command, and correct delegation of templates to a well-organized reference file. Its main weaknesses are redundancy (key boundary rules repeated 3-5 times across sections) and a large fraction of cross-references that point outside the shipped bundle.

Suggestions

State each boundary rule once in the Skill Contract and reference it from the steps instead of repeating it: the ROI/ROAS non-computation rule appears five times and the Retro Card gating conditions three times — consolidating these would materially reduce token cost without losing fidelity.

Trim the dense nested clauses in the Skill Contract 'Reads'/'Promotes' bullets (e.g. the tracker-state and creator_ref provenance rules) into the referenced skill-contract.md, keeping only the operative one-line rule in SKILL.md.

Make bundle-relative references resolvable: within the shipped bundle only references/analysis-templates.md exists, so either inline or bundle the frequently cited shared files (skill-contract.md, measurement-protocol.md, state-model.md) or note that they live in the parent repository.

DimensionReasoningScore

Conciseness

There is no educational filler, but the same governance rules are restated repeatedly: the ROI/ROAS non-computation boundary appears in Reads, Promotes, step 4, the STAR paragraph, and Next Best Skill, and the Retro Card gating conditions are stated three times (Done-when, step 8, and the 'For the Retro Card' paragraph). This matches 'mostly efficient but could be tightened' rather than score 2, since every sentence is operational rather than padded explanation of known concepts.

3 / 5

Actionability

Concrete guidance is present: eight numbered steps each mapped to a named template step, an executable connector command (python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/youtube.py" videos @creator --limit 20), and a worked example with a filled-in output table. It falls short of fully copy-paste-ready (anchor 5) because much of the executable fill-in detail is deferred to the external templates and several steps are stated as prohibitions rather than executable actions.

4 / 5

Workflow Clarity

The eight steps are clearly sequenced with an explicit dependency rule ("run Step 7 before populating or publishing Step 2 Conversions, Revenue...") and validation gates (measurement-protocol comparability bars, the renew/retest/retire decision gate, Unknown/NEEDS_INPUT fallbacks for missing data). It misses anchor 5 because the dependency flow is convoluted (build the Step 2 shell, then back-fill) and there are no error-recovery feedback loops beyond the fallback labels.

4 / 5

Progressive Disclosure

The body is a genuine overview that correctly delegates the eight fill-in templates to the real one-level-deep references/analysis-templates.md, with a labeled Reference Materials section describing each link. It stops short of anchor 5 because most cross-references (../../../references/skill-contract.md, ../../../references/measurement-protocol.md, scripts/connectors/README.md, and sibling SKILL.md paths) do not resolve within the actual bundle, which contains only references/analysis-templates.md.

4 / 5

Total

15

/

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: concrete capability list, explicit 'Use when' triggers in the user's natural phrasing, a clear negative boundary against the sibling ROI skill, and bilingual trigger terms. The only gap is a few missing English synonyms (recap/retro/report) that users might naturally say for a post-campaign review.

DimensionReasoningScore

Specificity

The description lists five concrete capabilities ("metric scorecards vs target and benchmark, platform/influencer/content rankings, engagement-quality and sentiment reads, conversion-attribution breakdowns, and ranked learnings") with comprehensive coverage of the skill's outputs. It matches the anchor for multiple specific concrete actions rather than the score-4 anchor, which expects minor gaps in coverage.

5 / 5

Completeness

It explicitly answers both questions: what it does ("produces metric scorecards vs target and benchmark... ranked learnings") and when to use it ("Use when the user asks to..."), with concrete trigger phrases and an explicit negative boundary ("Not for dollar-level return math — use roi-calculator"). This clearly matches the top anchor rather than the score-4 anchor where the 'when' could be more specific.

5 / 5

Trigger Term Quality

Natural quoted trigger phrases ("analyze influencer campaign performance", "compare influencers", "find what content worked") plus Chinese synonyms ("达人营销效果分析/投放复盘") give good coverage, but common English variations users might say — e.g. campaign recap, retro, post-mortem, or report — are absent. This sits between the good-coverage (4) and comprehensive-synonyms (5) anchors, closer to 4.

4 / 5

Distinctiveness Conflict Risk

The influencer-campaign-performance niche is clearly staked with distinct triggers, and the explicit de-confliction pointer ("Not for dollar-level return math — use roi-calculator") minimizes overlap risk with the closest sibling skill. It matches the clear-niche anchor, not the score-4 anchor with minor overlap risk.

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.