CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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. 达人营销策划/种草方案/活动追踪与关账

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./influencer/target/campaign-planner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 well-sequenced, heavily validated planning and tracking workflow with real one-level-deep references, but it pays for that rigor in token cost: governance rules are repeated across sections and dense run-on paragraphs burden the context window. Consolidating the repeated authorization/NEEDS_INPUT stipulations into a single stated-once rule would materially improve it.

Suggestions

State each governance rule once: the never-invent/NEEDS_INPUT, opaque-ref, and exact-authorization stipulations currently recur across the Skill Contract, Data Sources, and Instructions — consolidate them into one canonical location and reference it.

Split the ~350-word 'Writes' bullet into short scannable sub-bullets (save paths, artifact kinds, ID reuse, opacity rules) instead of a single run-on sentence.

Move the tracker control-artifact governance detail (paragraphs on publication receipts, close authorization, late events) into references/templates.md §10 or a dedicated reference file, keeping the SKILL.md body at overview altitude.

DimensionReasoningScore

Conciseness

Noticeably verbose: the 'Writes' contract bullet is a ~350-word run-on sentence, and the same governance rules (never invent/NEEDS_INPUT, opaque refs, exact authorization, raw locators stay transient) are restated across the Skill Contract, Instructions, and tracker paragraphs. No basic-concept over-explanation, but several padded and redundant sections.

2 / 5

Actionability

Concrete, executable guidance throughout — mode-selection rules, exact save paths (memory/influencer/campaign-planner/YYYY-MM-DD-<topic>.md), the campaign-<UUIDv4> ID format, and nine sequenced steps each bound to a template block. Not fully copy-paste-ready since the worked example is deferred to references and much of the guidance is constraint-shaped rather than constructive.

4 / 5

Workflow Clarity

Clear mode-first sequencing with extensive explicit validation — lock verification, NEEDS_INPUT returns on missing bindings, close gates, and 'PARTIAL CHECKPOINT COVERAGE — NOT CLOSE-ELIGIBLE' states. The tracker workflow's steps are distributed across the Skill Contract, Instructions, and templates §10, requiring the reader to assemble the linear flow.

4 / 5

Progressive Disclosure

Good structure: both bundle references (templates.md, influencer-tiers.md) exist, are one level deep, and are clearly signaled with content descriptions, and cross-skill links are navigational. However, the body inlines extensive tracker control-artifact governance detail that belongs in the reference tier.

4 / 5

Total

14

/

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 is strong: it pairs an explicit 'Use when' clause with concrete quoted trigger phrases (in both English and Chinese) and proactive exclusion routing to sibling skills. Its only weaknesses are a generic 'the plan' capability statement and slightly jargon-heavy tracker terminology, plus a few missing natural synonyms.

DimensionReasoningScore

Specificity

Names several concrete actions — 'produces the plan and, when requested, a non-canonical evidence tracker with scoped identity, publication, reconciliation, close, and reopen receipts' — but 'the plan' is generic and the receipt enumeration is jargon-dense, leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both what ('produces the plan and... a non-canonical evidence tracker with... receipts') and when (an explicit 'Use when...' clause with concrete quoted trigger phrases), matching the top anchor exactly.

5 / 5

Trigger Term Quality

Four natural quoted trigger phrases ('plan an influencer campaign', 'build a campaign blueprint', 'track or close a creator campaign', 'record a late campaign correction') plus Chinese synonyms (达人营销策划/种草方案), but common variations like 'influencer marketing plan' or 'creator program' are missing.

4 / 5

Distinctiveness Conflict Risk

Explicit not-for routing ('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') carves out a clear niche with minimal conflict risk.

5 / 5

Total

18

/

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.

Validation — 13 / 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

Path

influencer/target/campaign-planner/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.