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

69

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

75%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.

A well-structured, actionable enablement skill body with concrete memory-path targets, strong validation discipline, and clean progressive disclosure. Main improvement would be de-duplicating the repeated scope-guard text.

Suggestions

Consolidate the scope guard: it is restated nearly verbatim in the intro, the Instructions trailing guard, and implicitly in Reference Materials — keep one authoritative guard and cross-reference it.

Add an explicit completion checklist mirroring the 'Done when' criteria so a reviewer can verify each named alternative's battle card, talk-track fact provenance, and objection-table evidence pointers in one pass.

For steps 3 and 5, make the validation action a hard checkpoint (e.g., 'stop and surface open loop before packaging') rather than a soft flag, to tighten the feedback loop for the batch/destructive-adjacent routing.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concept-explanation padding, just contract, steps, and references — though the scope guard is restated three times (intro, after instructions, in the final guard) which could be trimmed.

4 / 5

Actionability

Concrete enumerated steps specify exact memory paths (memory/launch/sales-enablement-kit/, memory/events/claims.ndjson), explicit operation labels (operation: propose via registry-events.py), and Quick Start examples, with only minor gaps in copy-paste-ready commands.

4 / 5

Workflow Clarity

An 8-step numbered sequence carries explicit validation/feedback gates (route [needs source] lines to claims, 'mark the row blocked rather than improvising terms', embargo keyed to launch-registry), with minor validation gaps where issues are flagged as open loops rather than hard-verified.

4 / 5

Progressive Disclosure

Clear section structure (Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with one-level-deep, well-signaled links; no bundle files exist, but external references are cleanly organized for navigation.

4 / 5

Total

16

/

20

Passed

Description

100%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 highly specific, well-triggered description with concrete deliverables, explicit when-to-use guidance, and clear boundary exclusions against sibling skills. It is comprehensive and concise without fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete deliverables — 'battle cards vs each named alternative (where we win / where they win / trap questions)', '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' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers 'what' (enumerated enablement-kit deliverables) and 'when' ('Use when the user asks to...') with concrete trigger phrases, hitting the top anchor.

5 / 5

Trigger Term Quality

Quotes natural user phrases ('build battle cards', 'prep the sales team for launch', 'write the internal launch FAQ') plus synonyms and Chinese keywords (销售赋能/battle card/销售叙事/异议处理/内部FAQ), giving comprehensive coverage.

5 / 5

Distinctiveness Conflict Risk

Three explicit 'Not for...' exclusions naming sister skills (message-house-builder, competitor-tracker/competitor-analysis, cold-outbound-sequencer) carve a clear niche with minimal conflict risk.

5 / 5

Total

20

/

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.

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.