CtrlK
BlogDocsLog inGet started
Tessl Logo

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. 达人邀约建联/合作谈判话术

72

Quality

92%

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

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body with a clear sequenced workflow, explicit pre-ship validation, and clean progressive disclosure to two real reference files. The main weakness is token redundancy from repeated sibling-skill listings across three sections.

Suggestions

Consolidate the sibling/related skill links into a single section — they currently appear in Reference Materials, Next Best Skill, and Related Skills — to remove redundant tokens.

Tighten the Skill Contract 'Reads/Writes/Promotes' block, which is dense relative to the rest of the overview; consider moving full detail into a reference and keeping a one-line summary inline.

DimensionReasoningScore

Conciseness

The body is mostly lean and free of basic-concept padding, but sibling skills are listed three times (Reference Materials, Next Best Skill, Related Skills) and the Skill Contract section is dense, so it could be tightened; not score 3 because of that redundant cross-referencing, and not score 1 because it never explains concepts Claude already knows.

2 / 3

Actionability

Gives concrete cadence timing (Day 0 / 3-4 / 7-8 / 14, archive Day 21), per-step template anchors, specific memory paths, and a worked example — copy-paste-ready guidance; not the level below because instructions are specific and executable rather than abstract.

3 / 3

Workflow Clarity

A 5-step numbered sequence with an explicit pre-ship checkpoint ('Apply the hard copy rules in references/cold-copy-rules.md before any message ships') and a 'Done when' checklist; not the level below because validation checkpoints are explicit, not implicit.

3 / 3

Progressive Disclosure

The body is an overview pointing to real one-level-deep bundle files (references/templates.md and references/cold-copy-rules.md, both present) with anchor-based navigation; not the level below because references are clearly signaled and content is appropriately split rather than inlined.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 pairs concrete capabilities with natural-language triggers and explicit negative-boundary exclusions against sibling skills. It cleanly answers both what the skill does and when to use it with minimal fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'personalized pitches, multi-touch follow-up sequences, negotiation scripts with objection handling, and a status pipeline tracker' — matching the score-3 anchor for multiple specific concrete actions; not the level below because it goes well beyond naming a domain and a few actions.

3 / 3

Completeness

Explicitly answers both what ('produces personalized pitches…pipeline tracker') and when ('Use when the user asks to…'), with explicit triggers; not the level below because the 'when' is stated outright rather than merely implied.

3 / 3

Trigger Term Quality

Uses natural phrasings a user would actually say — 'write influencer outreach', 'follow up with a creator', 'pitch a journalist, hunter, or launch partner', 'negotiate partnership terms' — giving good coverage; not the level below because these are common user-spoken variations rather than jargon or a single keyword.

3 / 3

Distinctiveness Conflict Risk

Clear niche (outreach pitch mechanics) reinforced by explicit 'Not for…' exclusions pointing to contract-helper and press-media-relations, making wrong-skill triggering unlikely; not the level below because the exclusions remove the main overlap risk.

3 / 3

Total

12

/

12

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.

Validation12 / 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: 25 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

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.