CtrlK
BlogDocsLog inGet started
Tessl Logo

sales-enablement-kit

Use when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch — battle cards vs each named alternative (where we win / where they win / trap questions, every fact traceable), a sales talk track derived from the PR-FAQ spine, an objection-handling table (objection → response → evidence), internal FAQ + CS macros, and an internal launch announcement with embargo discipline. Not for the external message house — use message-house-builder; not for competitor tracking itself — use competitor-tracker or competitor-analysis; not for outbound sequences — use cold-outbound-sequencer. 销售赋能/battle card/销售叙事/异议处理/内部FAQ

77

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 tightly structured instruction skill: lean body assuming competence, a concrete 8-step procedure with explicit validation gates and 'Done when' criteria, and well-organized one-level-deep references. The only minor tightening opportunity is the duplicated scope-guard paragraph.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what a battle card or talk track is, and every section (Skill Contract, Data Sources, Instructions, Save Results) earns its place; the only minor redundancy is the 'does not write external messaging' scope guard appearing in both the intro and the Instructions block, but it does not rise to verbosity.

3 / 3

Actionability

An 8-step procedure with concrete per-step deliverables and formats — 'objection → response → evidence pointer', 'Measured / User-provided / Estimated' labels, explicit memory paths, and authorized 'operation: propose' requests — is highly actionable; per the rubric's instruction-only note, the absence of code is not penalized because the guidance is concrete and specific.

3 / 3

Workflow Clarity

Steps are clearly sequenced 1–8 with explicit validation checkpoints: a 'Done when' gate enumerating traceability and embargo conditions, embargo discipline keyed to the launch-registry, and 'ask before writing' prompts for memory writes, matching the score-3 anchor of clear sequence with explicit validation steps.

3 / 3

Progressive Disclosure

No bundle files exist, so the skill is self-contained; the body is well-organized into clear sections and points outward to one-level-deep references (Reference Materials list) rather than nesting, satisfying the score-3 anchor for a clean overview with well-signaled single-level references.

3 / 3

Total

12

/

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, well-scoped description: it states concrete deliverables, gives natural trigger phrases, includes an explicit 'Use when' clause, and disambiguates from three sibling skills. Written in third person.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'battle cards vs each named alternative (where we win / where they win / trap questions)', 'sales talk track', 'objection-handling table (objection → response → evidence)', 'internal FAQ + CS macros', and 'internal launch announcement' — matching the score-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

It explicitly answers both 'what' ('produces the internal enablement kit...') and 'when' with an explicit 'Use when the user asks to...' clause, satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

The quoted triggers — "build battle cards", "prep the sales team for launch", "write the internal launch FAQ" — are natural phrases a user would say, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Explicit 'Not for... use message-house-builder / competitor-tracker / cold-outbound-sequencer' disambiguation carves out a clear niche unlikely to trigger the wrong skill.

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

Warning

referenced_paths_exist

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

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.