CtrlK
BlogDocsLog inGet started
Tessl Logo

campaign-planner

Use when the user asks to "plan an influencer campaign", "build a campaign blueprint", "track or close a creator campaign", or "record a late campaign correction"; produces the plan and, when requested, a non-canonical evidence tracker with scoped identity, publication, reconciliation, close, and reopen receipts. Not for individual creator briefs — use brief-generator; not for overall product launches without creators — use launch-tier-planner; not for sending, publishing, amplifying, or paying — use the owning execution workflow. 达人营销策划/种草方案/活动追踪与关账

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

Well-structured, highly actionable, and properly progressive-disclosed with strong validation gates. The main weakness is conciseness: dense contractual prose with repeated qualifiers inflates token cost without proportional clarity.

Suggestions

Collapse the repeated scope/contract/identity/checkpoint/receipt/close phrasing across the Skill Contract and Instructions into a single canonical statement, referencing it rather than restating it each time.

Break the longest sentences in the Reads/Writes/Done-when bullets into shorter, declarative clauses to cut tokens and aid parsing.

Move the dense §10 close-gate and late-event mechanics (currently inline in Instructions) entirely into references/templates.md §10, keeping only the entry condition and the NEEDS_INPUT/PARTIAL-COVERAGE signals in the body.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: very long qualifier-stacked sentences in the Skill Contract and §10 prose, with scope/contract/identity/checkpoint/receipt/close phrasing restated across the Instructions rather than stated once. It avoids explaining concepts Claude already knows but is still heavily padded.

2 / 5

Actionability

Gives a concrete 9-step sequence, explicit mode selection, exact identifiers (campaign-<UUIDv4>, NEEDS_INPUT, NOT_VERIFIED), per-step template-block references, and a worked example/output shape. Minor gaps remain because the fill-in templates and executable specifics live in references/templates.md rather than inline.

4 / 5

Workflow Clarity

Clear sequenced workflow with explicit validation checkpoints ('if any binding is missing...return NEEDS_INPUT', 'PARTIAL CHECKPOINT COVERAGE — NOT CLOSE-ELIGIBLE') and feedback loops for close/reopen/late-event correction, satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

The body is an overview that delegates bulk detail to clearly signaled one-level-deep references (templates.md, influencer-tiers.md, both verified to exist), each annotated with what it contains, giving easy navigation.

5 / 5

Total

16

/

20

Passed

Description

95%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, third-person description that clearly states both capability and explicit trigger phrases with thorough negative-scope disambiguation. Its only soft spot is specificity, where the action list leans on abstract receipt categories rather than fully concrete operations.

DimensionReasoningScore

Specificity

Lists several concrete actions ('produces the plan', 'non-canonical evidence tracker with scoped identity, publication, reconciliation, close, and reopen receipts') with only minor gaps, though the actions are framed as operational receipt categories rather than the crisp tangible operations of the top anchor.

4 / 5

Completeness

Explicitly answers both what ('produces the plan and...evidence tracker') and when ('Use when the user asks to...') with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Quotes multiple natural phrases a user would say ('plan an influencer campaign', 'build a campaign blueprint', 'track or close a creator campaign', 'record a late campaign correction') plus Chinese synonyms, giving comprehensive coverage with natural variations.

5 / 5

Distinctiveness Conflict Risk

Defines a clear creator-campaign niche and explicitly redirects overlapping cases to brief-generator, launch-tier-planner, and execution workflows, minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation13 / 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: 19 suspicious

Warning

Total

13

/

16

Passed

Repository
aaron-he-zhu/aaron-marketing-skills
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.