CtrlK
BlogDocsLog inGet started
Tessl Logo

battlecard-generator

Research a specific competitor across their website, reviews, ads, social presence, and pricing — then produce a structured sales battlecard with positioning traps, objection handlers, landmine questions, and win/loss themes. Chains web research, review mining, and ad intelligence. Use when sales needs competitive ammo or when entering a new market with established incumbents.

68

Quality

82%

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

65%

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

A highly actionable, well-structured research-and-template workflow that assumes Claude's competence and avoids concept padding. Its main weaknesses are duplicated trigger sections, absent verification checkpoints in the batch-research flow, and a monolithic structure that keeps a large output template inline.

Suggestions

Merge the 'When to Use' and 'Trigger Phrases' sections to remove the duplicated trigger phrasing and tighten token use.

Add an explicit validation checkpoint between Phase 2 and Phase 3 (e.g. 'Confirm evidence exists for every Win/Lose/Tie claim before drafting the battlecard') to gate the batch-research output.

Extract the full Phase 3 battlecard template into a references/ file (e.g. battlecard-template.md) and link to it from the body, leaving SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient and free of concept-explanation padding, but the 'When to Use' and 'Trigger Phrases' sections duplicate each other and the large output template carries placeholder repetition, so not every token earns its place.

2 / 3

Actionability

Provides copy-paste-ready search strings (e.g. site:g2.com OR site:capterra.com), concrete fetch targets, per-section extraction checklists, and a fully scaffolded battlecard template with sample objection handlers — concrete and executable guidance.

3 / 3

Workflow Clarity

Phases are clearly sequenced (Intake → Research 1A-1E → Analysis → Output), but there is no explicit validation/verification checkpoint before battlecard generation — only an implicit 'Confidence' label — leaving the batch-research workflow without a completeness gate.

2 / 3

Progressive Disclosure

Well-organized with clear headers and no nested references, but it is a monolithic >50-line file with the ~130-line output template inline — content that could reasonably live in a separate reference file rather than the overview.

2 / 3

Total

9

/

12

Passed

Description

100%

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 specific, trigger-rich, and complete, explicitly stating both capability and use-conditions in third person. It is a strong, low-conflict description with no over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — research across website, reviews, ads, social presence, and pricing, then produce a battlecard with positioning traps, objection handlers, landmine questions, and win/loss themes — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (research a competitor and produce a structured battlecard) and when via the 'Use when sales needs competitive ammo or when entering a new market…' clause.

3 / 3

Trigger Term Quality

Uses natural sales vocabulary a rep would actually say — 'battlecard', 'competitor', 'competitive ammo', 'new market', 'incumbents' — giving good coverage rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (sales battlecards against a named competitor) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-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.