CtrlK
BlogDocsLog inGet started
Tessl Logo

competitive-intel

Systematic competitor tracking that feeds CMO positioning, CRO battlecards, and CPO roadmap decisions. Use when analyzing competitors, building sales battlecards, tracking market moves, positioning against alternatives, or when user mentions competitive intelligence, competitive analysis, competitor research, battlecards, win/loss, or market positioning.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 strategy skill that assumes Claude's competence and provides concrete templates, thresholds, and role-owner guidance. The only material gap is a dangling reference to a non-existent templates/battlecard-template.md file.

Suggestions

Create templates/battlecard-template.md (or remove both references to it) so the in-body pointer in Layer 4 Output Formats and the References section resolve to a real file.

Add an explicit validation checkpoint in the monthly/triggered cadence (e.g., 'confirm battlecard still matches current pricing before publishing') to lift workflow_clarity from 4 to 5.

Verify references/ci-playbook.md covers the OSINT sources and positioning-map construction promised in the References section, since it is the only bundle file present.

DimensionReasoningScore

Conciseness

Dense, table-driven content that assumes Claude's intelligence (no explaining SWOT or what a battlecard is); every section earns its place with only minor editorial framing.

5 / 5

Actionability

Highly concrete guidance for an instruction-only skill: named OSINT sources per dimension, specific thresholds ($50K ACV, 48 hours, >$20M), a 6-question win/loss script, and copy-paste-ready tables.

5 / 5

Workflow Clarity

The 5-Layer system and monthly/triggered/quarterly cadence give a clear sequence with diagnostic checkpoints (red flags, over/under-tracking signs), but no explicit validate-fix-retry loop — acceptable since the skill is not a destructive or batch operation.

4 / 5

Progressive Disclosure

Clear overview up front with detailed OSINT/positioning content correctly split into references/ci-playbook.md (one level deep), but templates/battlecard-template.md is cited twice yet does not exist — a real, if minor, navigation defect.

4 / 5

Total

18

/

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 strong, third-person description that concisely states the skill's purpose, enumerates concrete actions, and provides explicit 'Use when' triggers with natural keyword synonyms. It scores at the top of every dimension with no vague fluff or over-claims.

DimensionReasoningScore

Specificity

Names the competitive-intel domain and lists multiple concrete actions (tracking, battlecards, positioning, win/loss) across named C-suite consumers, with comprehensive coverage and no vague fluff.

5 / 5

Completeness

Explicitly answers both what ('Systematic competitor tracking that feeds CMO positioning, CRO battlecards, and CPO roadmap decisions') and when ('Use when analyzing competitors... or when user mentions competitive intelligence...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms (competitive intelligence / competitive analysis / competitor research) and specific phrases (battlecards, win/loss, market positioning) users would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers (battlecards, win/loss, competitive positioning) scoped to C-suite consumers, giving minimal overlap with other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-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.