CtrlK
BlogDocsLog inGet started
Tessl Logo

battle-card-builder

Research and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.

67

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 well-structured, highly actionable workflow skill with a complete card schema and clear steps. It loses points for rhetorical padding and for referencing template/example bundle files that are not actually present in the skill bundle.

Suggestions

Trim thematic flavor text (e.g., "this skill exists because of what it costs a rep when one of those turns out wrong," "is a liability wearing a logo") to tighten conciseness without losing the instruction.

Add an explicit final validation checkpoint — e.g., "Before the Final Step, confirm every Say/Ask/Watch-Out claim has a matching row in the Evidence Table with a URL and label" — to close the workflow's verification gap.

Either include the referenced bundle files (template.md, examples/sample.md, examples/sample-industrial.md) or remove the links so the one-level-deep navigation lands on real content.

DimensionReasoningScore

Conciseness

Largely instruction-dense and skill-specific, but threaded with thematic flavor text ("this skill exists because of what it costs a rep," "a liability wearing a logo") that adds tokens without adding executable guidance.

2 / 3

Actionability

Provides a complete, copy-paste-ready card schema marked "do not reorder," numbered executable steps, an example invocation, and a concrete trap-question example — concrete and specific throughout.

3 / 3

Workflow Clarity

Steps are clearly numbered with a search-plan gate ("Continue unless revised") and an assumption fallback, but there is no explicit final checkpoint verifying the card satisfies its own rules (every claim labeled/sourced, every talking point in the evidence table) before the Final Step.

2 / 3

Progressive Disclosure

The body is well organized and signals one-level-deep references to template.md and examples/sample.md, but those bundle files are not present, so the promised deeper content is unreachable — navigation points to missing files.

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.

A strong, concise description that hits what, when, and distinctiveness in two sentences with concrete actions and natural trigger terms. No fluff or over-claims; third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "Research and draft a competitive battle card," "every claim labeled and sourced" — covering research, drafting, labeling, and sourcing rather than a single vague verb.

3 / 3

Completeness

Explicitly answers both what ("Research and draft a competitive battle card... every claim labeled and sourced") and when ("Use when a rep needs a field-action card"), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Uses natural terms a rep or PM would actually say — "battle card," "competitive," "field-action card" — with a clear negative trigger ("not a research report") that sharpens intent.

3 / 3

Distinctiveness Conflict Risk

The "field-action card, not a research report" framing carves a clear niche distinct from adjacent competitive-research skills, making misfires unlikely.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 3 missing, 10 suspicious

Warning

Total

14

/

16

Passed

Repository
deanpeters/Product-Manager-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.