CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

competitive-report-structure

Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions. Use when presenting competitive findings to leadership or a board, writing a competitive landscape report, or as the final step of the competitive analysis pipeline.

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

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 high-quality instruction skill: lean, decisive, and concrete about report structure, content selection, and presentation formats, with useful anti-patterns and an explicit prerequisite gate. The main gaps are the absence of an explicit validation checkpoint before delivery and some repeated framing that costs tokens without adding new guidance.

Suggestions

Add an explicit pre-delivery validation step, e.g., "Before delivery, verify every section resolves the three decision questions and every recommendation is checked against the brand balance; revise any that fail."

Consolidate the brand-balance rule into one canonical statement (the positioning brief section) and reference it elsewhere instead of restating it in the framing principle, section 7, and anti-patterns.

Specify the heatmap's scale convention (e.g., a 5-point symbol or color scale and how ties/missing data are shown) so the matrix renders consistently without improvisation.

DimensionReasoningScore

Conciseness

The body is directive and assumes Claude's intelligence (no explanation of what a benchmark matrix or 2×2 is), but there is deliberate reinforcement that could be tightened: the brand-balance rule appears in the positioning brief, framing principle, section 7, and the anti-patterns; "do not add a blended total column" and the three decision questions are each stated twice. Not 5 because these repetitions could be trimmed; not 3 because nothing explains concepts Claude already knows.

4 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: a fixed 8-section structure with per-section specs ("3–5 takeaways, decision-first", heatmap with two sub-columns for dimension 9, no blended total), selection heuristics for deep dives ("best exemplar of the target tension... the cautionary 'one pole only' case"), and verbatim trigger questions. Where flexibility is client-specific (paired axes, 2×2 axes) the substitution is explicitly instructed rather than left vague.

5 / 5

Workflow Clarity

The sequence is clear — establish the positioning brief first, then sections 1–8, ending with the decision framework and trigger questions — and a prerequisite gate exists ("Starting before all profile cards are complete" is an anti-pattern). Not 5 because there is no explicit validation/rework loop, e.g., checking each section against the decision framework and revising before delivery is implied by "the report must resolve these" but never stated as a checkpoint.

4 / 5

Progressive Disclosure

Well-organized sections with no nesting and no buried references; cross-skill dependencies (benchmark-methodology, competitive-platform-analysis) are cleanly signaled in a Related Skills section. Not 5 because no bundle files exist at all, so everything is inline at ~150 lines — a section spec (e.g., the matrix/heatmap conventions or trigger-question bank) could plausibly live in a reference file; not 3 because the structure is clear and nothing is misplaced.

4 / 5

Total

17

/

20

Passed

Description

92%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 description: third-person, concrete, comprehensive on deliverables, and with an explicit and specific "Use when" trigger clause. The only weakness is slightly thin synonym coverage for natural user phrasings of the domain.

Suggestions

Add one or two natural synonyms to the trigger clause, e.g., "writing a competitor analysis or market landscape report", so users who say "competitor analysis" instead of "competitive landscape" still match.

Optionally name the audience-facing artifact format (e.g., "client deliverable") in the trigger list, since that phrasing appears in the body but not the description.

DimensionReasoningScore

Specificity

"Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions" — multiple specific concrete outputs are enumerated, comprehensively covering what the skill produces. Not 4 because coverage of the deliverable list is complete rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both: the "what" is the enumerated report assembly, and the "when" is the concrete "Use when presenting competitive findings to leadership or a board, writing a competitive landscape report, or as the final step of the competitive analysis pipeline" clause. Both are present with concrete trigger phrases, matching the anchor.

5 / 5

Trigger Term Quality

Good natural-phrase coverage: "presenting competitive findings to leadership or a board", "writing a competitive landscape report", "final step of the competitive analysis pipeline". Not 5 because common synonyms a user would naturally say — e.g., "competitor analysis", "market landscape", "benchmarking report" — are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche (final assembly of a competitive analysis pipeline, explicitly dependent on benchmark-methodology's scored profile cards) with distinct triggers around report presentation to leadership. Minimal overlap risk; the pipeline-position framing separates it from general analysis skills.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

affaan-m/ECC

Path

skills/competitive-report-structure/SKILL.md

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.