CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

advocacy-program-designer

Use when the user asks to "design an employee advocacy program", "set up founder-led sharing", or "build a share kit for the team"; produces an advocacy program blueprint in two modes — participation-driven opt-in (default) or top-down assigned with its coercion and authenticity risks flagged — with a voluntary opt-in roster spec submitted as channel-registry proposal events, share kits with mandatory per-person variation, staggered human posting windows plus anti-pod guardrails (no coordinated identical reshares, no engagement rings), per-person material-connection disclosure lines per FTC and 《互联网广告管理办法》, and a Slack/Teams distribution spec. Not for paid creator campaigns — use campaign-planner. 员工倡导/创始人IP分享/内部分享计划/披露合规

Quality

81%

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

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.

The body is a dense, well-structured program-design playbook with genuinely concrete step specs and validation gates, but it is hampered by significant phrase-level repetition of registry/routing boilerplate and total dependence on external templates that are not present in the bundle. Tightening the repeated propose/routing language would raise token efficiency without losing substance.

Suggestions

Reduce redundancy: state the "authorized `operation: propose` request to `registry-events.py`" write path once (e.g., in the Skill Contract or Scope guard) and reference it thereafter instead of repeating the full phrase ~5 times across Instructions and Save Results.

Consolidate routing: route outreach-manager, campaign-planner, and creator-registry/contract-helper once each (Scope guard or a single routing section) rather than restating them in the intro, Contract, Instructions, Reference Materials, and Next Best Skill.

Add one worked micro-example inline — a sample per-person disclosure line and a two-line kit skeleton — so the most consequential deliverables are executable from this file alone, since the referenced template files are not part of this bundle.

DimensionReasoningScore

Conciseness

The body is information-dense (no explanations of concepts Claude already knows) but carries real redundancy: "via an authorized `operation: propose` request to `registry-events.py`" is repeated verbatim ~5 times, and routing/scope rules (outreach-manager ×4, campaign-planner ×3, the propose-only-write rule) are restated across the intro, Scope guard, Skill Contract, Instructions, and Save Results — beyond the 'minor instances' of a 4, though not padded enough for a 2.

3 / 5

Actionability

The 8 steps give concrete, executable guidance — exact roster fields (advocate_ref, disclosure line, opt-in date, voluntary-basis evidence), "3+ distinct angles", posting spread "across 3-7 days", enumerated receipt fields, and "max one no-pressure nudge" — but no example disclosure line, kit skeleton, or handoff summary is shown in-file; those templates live in external files absent from this bundle, leaving minor gaps.

4 / 5

Workflow Clarity

Steps are clearly sequenced with real checkpoints — an explicit "Done when" checklist, rights gating ("block expired/revoked/disputed/unknown rights"), and receipt gating ("no receipt means not posted") — but error-recovery paths when a check fails mid-flow (e.g., gate rejection, rights dispute) are mostly implicit and delegated to external skills, short of the feedback-loop anchor of 5.

4 / 5

Progressive Disclosure

A well-sectioned single file with an annotated, one-level-deep Reference Materials list that clearly signals what each external file provides; however, the bundle contains no files of its own — every template and benchmark it depends on (skill-contract.md, echo-benchmark.md, human-action-control.md, SECURITY.md) lives outside this skill directory and none can be verified here, so it falls short of the fully self-contained-navigation anchor of 5.

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: explicit what-and-when with natural quoted trigger phrases, third-person voice, concrete deliverable enumeration, and explicit out-of-scope routing to adjacent skills. The only gap is a few missing English trigger variations (e.g., "brand ambassador", "staff advocacy").

DimensionReasoningScore

Specificity

The description lists multiple concrete deliverables in third person ("produces an advocacy program blueprint", "voluntary opt-in roster spec", "share kits with mandatory per-person variation", "staggered human posting windows plus anti-pod guardrails", "per-person material-connection disclosure lines", "Slack/Teams distribution spec") with comprehensive coverage of the skill's outputs, matching the top anchor rather than the 'minor gaps' of a 4.

5 / 5

Completeness

It explicitly answers both questions with concrete trigger phrases: an explicit "Use when the user asks to..." clause and a clear "what" ("produces an advocacy program blueprint in two modes — participation-driven opt-in (default) or top-down assigned"), plus a negative boundary ("Not for paid creator campaigns — use campaign-planner"), matching the top anchor exactly.

5 / 5

Trigger Term Quality

Three natural quoted trigger phrases ("design an employee advocacy program", "set up founder-led sharing", "build a share kit for the team") plus Chinese synonyms (员工倡导/创始人IP分享/内部分享计划/披露合规) give good coverage, but common English variations users would naturally say — "brand ambassador program", "staff advocacy", "employee sharing program" — are missing, so it falls just below the comprehensive-synonyms anchor of 5.

4 / 5

Distinctiveness Conflict Risk

A clear employee-advocacy niche with distinct triggers and explicit deconfliction against the nearest neighbors ("Not for paid creator campaigns — use campaign-planner"), so conflict risk is minimal rather than the 'minor overlap risk' of a 4.

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

Warning

referenced_paths_exist

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

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

social/craft/advocacy-program-designer/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.