CtrlK
BlogDocsLog inGet started
Tessl Logo

competitive-analysis

Operator-first competitive analysis workflow for competitor profiling, pricing and packaging comparisons, positioning maps, SWOTs, and strategic recommendations. Use for prompts like "analyze our competitors", "benchmark our pricing", "map the market", "who are we up against", or "build a SWOT". Best when you have a company or product, ideal customer profile, and competitor set or permission to discover it. Optional Open Brain search and capture can pull prior notes and store the final brief.

74

Quality

93%

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

86%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, token-efficient instruction-only skill with a clear sequenced process, strong evidence/judgment rules, and good organization. The main gap is the absence of an explicit validation checkpoint or worked example to push actionability and workflow clarity to the top.

Suggestions

Add a short worked example (e.g., a sample positioning map or one-row comparison table) to make the Output section copy-paste-ready and lift actionability.

Insert an explicit validation step in the Process — e.g., 'Review findings against Evidence rules before drafting the brief' — to add a feedback checkpoint to the workflow.

Clarify how to label confidence on the competitor set (the Process mentions 'label confidence' but does not specify a convention), so the guidance is fully executable.

DimensionReasoningScore

Conciseness

Lean and efficient; assumes Claude's competence with no padding or re-explanation of known concepts. Every section (Problem, Audience, When/When Not, Required Context, Process, Evidence rules, Output, Notes) earns its place.

5 / 5

Actionability

Concrete, specific guidance — named comparison dimensions, explicit evidence rules ('Never invent pricing...', 'Label inference explicitly'), and a structured default output with role labels — but lacks a worked example, leaving a minor gap versus fully copy-paste-ready instruction.

4 / 5

Workflow Clarity

A clearly sequenced 6-step process with sub-bullets per step and judgment-discipline rules ('Distinguish facts, inferences, and open questions'), but no explicit validation/feedback-loop checkpoint, so it stops short of the top anchor.

4 / 5

Progressive Disclosure

A self-contained skill with no bundle files and clean, well-labeled section headers; under the simple-skill exception, well-organized structure without external references scores the top mark.

5 / 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 tight, third-person description that names concrete capabilities, provides multiple natural trigger phrases, and explicitly covers both what the skill does and when to use it. Distinctiveness is strong with clear scope boundaries.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'competitor profiling, pricing and packaging comparisons, positioning maps, SWOTs, and strategic recommendations' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (the analysis workflow and its outputs) and 'when' ('Use for prompts like...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Quotes natural trigger prompts users would say ('analyze our competitors', 'benchmark our pricing', 'map the market', 'who are we up against', 'build a SWOT') with synonym coverage.

5 / 5

Distinctiveness Conflict Risk

A clear competitive-analysis niche with distinct triggers; the body differentiates it from sibling skills (research-synthesis, deal-memo-drafting), keeping conflict risk minimal.

5 / 5

Total

20

/

20

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
NateBJones-Projects/OB1
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.