CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

outreach-manager

Use when the user asks to "write influencer outreach", "follow up with a creator", "pitch a journalist, hunter, or launch partner", or "negotiate partnership terms"; produces personalized pitches, multi-touch follow-up sequences, negotiation scripts with objection handling, and a status pipeline tracker — the shared outreach mechanics engine for creator, media/analyst, launch-partner, and social-selling / advocate-recruitment targets. Not for finalizing signed agreements — use contract-helper; not for media-list tiering, embargo terms, or press-release structure — use press-media-relations. 达人邀约建联/合作谈判话术

Quality

87%

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

81%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 highly actionable with a well-sequenced, heavily validated workflow and properly structured one-level-deep references to real bundle files. Its main weakness is token efficiency: identity/suppression rule blocks are repeated nearly verbatim across the Skill Contract and Procedure sections, and dense protocol prose is inlined rather than referenced.

Suggestions

Deduplicate the identity and suppression rules: state the 'never persist raw locators' list and the decline/stop-contact reason codes once (e.g., in the Skill Contract) and reference them from Steps 1, 3, and 5 instead of repeating them.

Move the multi-paragraph consent/identity protocol (the runtime-resolution prose and the pre-procedure decline handling) into a dedicated reference file, keeping the procedure steps as concise pointers.

Trim the example output section — the abridged example duplicates the template structure already available in references/templates.md.

DimensionReasoningScore

Conciseness

Mostly efficient domain-specific guidance, but noticeably repeated rule blocks pad the body: "Never derive the path from a raw handle" / "Never persist a raw handle, name, profile URL, email, phone, postal address, provider ID, or credential" appears in both the Skill Contract and Step 1, and the suppression reason codes (user-request/unsubscribe/complaint/withdrawal) are stated three times. It is above the 2 anchor because the content is non-obvious project protocol rather than concepts Claude already knows, but below 4 because whole paragraphs could be deduplicated.

3 / 5

Actionability

Fully executable guidance: the consent-runtime bash block is copy-paste ready with explicit failure messages and exit codes, the 5-step procedure each links to a verified fill-in template anchor in references/templates.md, the cadence is concretely specified ("Day 0 / 3-4 / 7-8 / 14, then archive at Day 21"), and a worked example is provided. Matches the 5 anchor 'Fully executable; copy-paste ready code or commands'.

5 / 5

Workflow Clarity

Clear five-step sequence with explicit validation checkpoints for the risky external-side-effect operation: the "Do not send or schedule anything until all of these are true" gate, fail-closed rules ("'Unknown' or missing eligibility fails closed"), live suppression check immediately before dispatch, and NEEDS_INPUT recovery handoffs — matching the 5 anchor with feedback loops and error-recovery paths. Not below 5 because validation is pervasive and explicit.

5 / 5

Progressive Disclosure

Good structure: Quick Start, Skill Contract, Data Sources, a five-step procedure whose bulk detail correctly lives in one-level-deep, well-signaled references ([references/templates.md](references/templates.md), [references/cold-copy-rules.md](references/cold-copy-rules.md)) with real per-step anchors, plus a clear Reference Materials index. Not a 5 because dense protocol prose (the multi-paragraph consent/identity rules) is inlined in the body where a reference file would keep the overview leaner.

4 / 5

Total

17

/

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.

The description is strong: third-person voice, concrete capability list, explicit quoted 'Use when' triggers, and explicit disambiguation against sibling skills. The only gap is modest synonym coverage (e.g., 'reach out', 'sponsorship') in the trigger terms.

DimensionReasoningScore

Specificity

Quotes multiple concrete capabilities: "produces personalized pitches, multi-touch follow-up sequences, negotiation scripts with objection handling, and a status pipeline tracker" — comprehensive coverage of the skill's actions, matching the anchor 'Lists multiple specific concrete actions; comprehensive coverage'. It is not a 4 because coverage spans every major function with no notable gaps.

5 / 5

Completeness

Explicitly answers both halves: "Use when the user asks to..." gives concrete when-triggers and "produces personalized pitches..." states what it does, matching the 5 anchor 'Clearly and explicitly answers both what AND when with concrete trigger phrases'. It is not a 4 because the when-clause is already fully explicit with quoted phrases.

5 / 5

Trigger Term Quality

Natural quoted trigger phrases like "write influencer outreach", "follow up with a creator", "pitch a journalist, hunter, or launch partner", and "negotiate partnership terms" give good keyword coverage; common variations such as "reach out to", "DM", or "sponsorship deal" are missing, so it sits between the 4 and 5 anchors but not at comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche (outreach pitch mechanics) with explicit negative boundaries — "Not for finalizing signed agreements — use contract-helper; not for media-list tiering, embargo terms, or press-release structure — use press-media-relations" — minimizing conflict with sibling skills, matching the 5 anchor 'Clear niche with distinct triggers; minimal conflict 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: 29 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

influencer/activate/outreach-manager/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.