CtrlK
BlogDocsLog inGet started
Tessl Logo

competitive-report-structure

Use after benchmark-methodology has produced scored competitor profile cards. Assembles findings into a decision-grade report: landscape map, competitor profiles, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions. Final step in the three-skill competitive pipeline.

70

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The content is highly actionable and well-sequenced with explicit validation checks, and it is appropriately self-contained with clear organization. The only meaningful weakness is mild redundancy of the organizing thesis (strategic tension, brand balance, the three questions) across several sections.

Suggestions

Consolidate the strategic-tension and brand-balance framing into a single authoritative section and have later sections back-reference it ('per the positioning brief') instead of restating the definitions.

State the three driving questions once (intro) and reference them rather than re-deriving them in the 'Decision framework' section.

DimensionReasoningScore

Conciseness

The body is dense and directive with no padding of concepts Claude already knows, but the strategic-tension/brand-balance framing and the three organizing questions are restated across the positioning brief, framing principle, section 7, decision framework, and trigger questions, so it could be tightened.

2 / 3

Actionability

Gives concrete, specific structural guidance throughout — '3–5 takeaways', 'at minimum a 2×2', 'Rows = competitors… columns = the nine benchmark dimensions', 'Do not add a blended total column', 'Sequence by impact × effort' — which is fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

Clear sequence (establish positioning brief first, then eight numbered sections, then trigger questions) with explicit preconditions in 'When to Activate' and validation checks such as 'Confirm whether the target quadrant is genuinely open' and 'flag any that would shift [brand balance]'.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the body is well-organized into clearly delineated sections with a 'Related Skills' pointer to prerequisites, and there is no content that would clearly benefit from being split into separate files.

3 / 3

Total

11

/

12

Passed

Description

85%

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, complete, and well-differentiated, naming concrete report components and an explicit use trigger. Its main weakness is trigger-term quality: the trigger is framed as pipeline sequencing rather than natural keywords a user would actually say.

Suggestions

Add a natural-language 'Use when...' trigger with user-facing terms, e.g. 'Use when the client needs a competitive analysis report, a competitor benchmarking deliverable, or a white-space/market-positioning report.'

Surface common phrasings users would say ('competitor report', 'benchmarking matrix', 'market landscape map') so the skill triggers on natural requests, not only on pipeline state.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'landscape map, competitor profiles, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions' — rather than vague language.

3 / 3

Completeness

Clearly states what it does (assembles a decision-grade report with named components) and gives an explicit when-trigger ('Use after benchmark-methodology has produced scored competitor profile cards'), satisfying both what and when.

3 / 3

Trigger Term Quality

Contains relevant domain keywords (competitor profiles, benchmarking matrix, white-space analysis) but frames the trigger as pipeline sequencing ('Use after benchmark-methodology...') rather than natural user-facing terms a client would say.

2 / 3

Distinctiveness Conflict Risk

'Final step in the three-skill competitive pipeline' plus a pipeline-positioned trigger gives it a clear niche unlikely to fire for the wrong skill.

3 / 3

Total

11

/

12

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
affaan-m/ECC
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.