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.

Highly actionable and workflow-safe content: executable gating code, explicit validation with fail-closed behavior, and a clean per-step template structure. The main weakness is token efficiency — the identity/consent policy is repeated across multiple sections rather than stated once and referenced.

Suggestions

State the opaque creator_ref / never-persist-raw-locator rules once (e.g., in the Skill Contract) and reference that statement from Step 1 and the Procedure preamble instead of restating them in four places.

Enumerate the suppression reason-code mapping (user-request/unsubscribe/complaint/withdrawal) once and link to it from Steps 3 and 5 rather than repeating the full list three times.

Move the 25-line bash runtime-verification block into the already-referenced runtime-invocation.md (or a scripts/ helper) and keep only the invocation and fail-closed rules inline.

DimensionReasoningScore

Conciseness

The body teaches nothing Claude already knows, but it restates the opaque creator_ref / never-persist-raw-locator rules in at least four places (Contract Reads, Contract Writes, Procedure preamble, Step 1) and enumerates the same suppression reason codes (user-request/unsubscribe/complaint/withdrawal) three times. Mostly efficient but needs tightening through deduplication; not 2 because there is no padded concept explanation, only internal repetition.

3 / 5

Actionability

Fully executable guidance: a copy-paste-ready 25-line bash gate with explicit file checks and JSON verification of the suppression result, a concrete cadence (Day 0 / 3-4 / 7-8 / 14, archive at Day 21), per-step template links with resolvable anchors (verified against references/templates.md), a worked example, and quick-start invocations.

5 / 5

Workflow Clarity

A five-step numbered procedure, each step bound to a template, with explicit validation checkpoints (runtime bundle verification, live is-suppressed query before every dispatch, fail-closed Unknown eligibility) and error-recovery feedback loops (NEEDS_INPUT consent-check handoff, stop-and-exit on suppressed results). A done-when checklist closes the loop.

5 / 5

Progressive Disclosure

The bulk how-to (templates for all five steps, cold-copy rules) is correctly offloaded to real one-level-deep reference files with descriptive link text, and both referenced files exist with matching anchors. Not 5 because the inlined bash gate and the repeated identity/consent policy prose — material also covered by the bundle's runtime-invocation.md and registry-event-protocol.md Runtime Reads — could largely be referenced out, and the sprawling sibling-skill link lists blur navigation.

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.

A strong description: concrete deliverables, explicit quoted trigger phrases, and explicit boundary redirects to sibling skills. The only gap is modest synonym coverage of natural trigger terms (e.g., reach out, collab, sponsorship).

DimensionReasoningScore

Specificity

Lists multiple concrete deliverables — "personalized pitches, multi-touch follow-up sequences, negotiation scripts with objection handling, and a status pipeline tracker" — covering the skill's full capability surface with no vague filler. Not 4 because there are no coverage gaps; every named action is a specific, concrete output.

5 / 5

Completeness

Explicitly answers both questions: the "what" is the deliverables list, and the "when" is the leading "Use when the user asks to..." clause with concrete quoted trigger phrases. Not 4 because the when-clause is explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

Quotes natural phrases users would actually say: "write influencer outreach", "follow up with a creator", "pitch a journalist, hunter, or launch partner", "negotiate partnership terms". Not 5 because common variations such as "reach out to", "collab", or "sponsorship" are absent; not 3 because several natural multi-word triggers are present and well-chosen.

4 / 5

Distinctiveness Conflict Risk

Establishes a clear niche (outreach pitch mechanics) and actively redirects adjacent intents: "Not for finalizing signed agreements — use contract-helper; not for media-list tiering, embargo terms, or press-release structure — use press-media-relations". 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.