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.

67

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/competitive-report-structure/SKILL.md

The canonical home for this skill is competitive-report-structure in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 report-assembly skill with clear numbered sequencing and an explicit start gate. Its main weaknesses are minor conceptual redundancy around the brand balance and the absence of explicit inter-section validation checkpoints or a concrete output template.

Suggestions

Consolidate the brand-balance/strategic-tension guidance into one section and reference it from sections 7 and the framing principle to remove redundancy.

Add an explicit validate-then-proceed checkpoint between assembly stages (e.g., confirm the tension plot and matrix are complete before drafting white-space and recommendations).

Provide a short annotated report outline or one-paragraph example excerpt so the abstract structural instructions map to a concrete deliverable.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes domain competence, but the brand-balance/strategic-tension concept is restated across the positioning brief, framing principle, and section 7, and the three guiding questions are echoed between the intro and the Decision framework.

4 / 5

Actionability

Concrete structural instructions throughout (explicit 2x2 axes, matrix row/column layout, two sub-columns instead of averaging, no blended total column, 3-5 takeaways, impact x effort sequencing); minor gap is the lack of a concrete output template or example report excerpt.

4 / 5

Workflow Clarity

Numbered sections 1-8 give a clear assembly sequence with a gated 'When to Activate' precondition and an 'establish first' positioning brief, but inter-section validation checkpoints are mostly implicit rather than explicit validate-then-proceed loops.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers and one-level skill-to-skill pointers (benchmark-methodology, competitive-platform-analysis, brand-discovery) in a Related Skills section; no nested file references, and no bundle files exist to split.

4 / 5

Total

16

/

20

Passed

Description

85%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, specific, well-positioned description that clearly answers what and when and is firmly gated within a multi-skill pipeline. The only relative weakness is that trigger terms are workflow-positioned rather than natural user phrases, though this fits a pipeline-sequenced skill.

DimensionReasoningScore

Specificity

Enumerates six concrete report components (landscape map, competitor profiles, benchmarking matrix, white-space analysis, strategic recommendations, team alignment trigger questions) — comprehensive coverage of the assembly task.

5 / 5

Completeness

Explicitly states both what (assembles a decision-grade report with named sections) and when (use after benchmark-methodology produces scored cards; final step of the three-skill pipeline) with concrete, specific gating.

5 / 5

Trigger Term Quality

Domain keywords (competitor, benchmark, report, pipeline) are present but the 'when' is workflow-positioned ('Use after benchmark-methodology') rather than natural user-uttered phrases, and synonyms/file extensions are absent.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche as the gated final step of a named competitive-analysis pipeline, with a prerequisite-skill trigger that is unlikely to fire for the wrong skill.

5 / 5

Total

18

/

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
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.