competitive-matrix

Build competitive analysis matrices with scoring and gap analysis. Usage: /competitive-matrix <analyze> [options]

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/competitive-matrix/SKILL.md

Quality

Content

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

The body is lean and shows the input format and CLI usage, but it lacks an executable workflow with validation checkpoints for what is a batch scoring operation, and its external references point into another skill's directory rather than a local, well-signaled bundle.

Suggestions

Add a sequenced workflow with a validation checkpoint, e.g. "1. Load and validate competitors.json schema; 2. Run competitive_matrix_builder.py; 3. Verify dimension weights sum and inspect gap output."

Provide an inline minimal example of invoking the builder script with expected output rather than only pointing to the script path.

Clarify the cross-skill reference: either inline the essential details or link to a local reference file inside this skill's own bundle.

Dimension	Reasoning	Score
Conciseness	The body is short and avoids explaining concepts Claude already knows; the only mild padding is the redundant "## Examples" block that repeats the usage line, keeping it just above the efficient midpoint.	4 / 5
Actionability	It gives the input JSON shape and CLI invocations but the actual builder logic is deferred to an external script path; guidance is concrete for input but incomplete for execution, matching the anchor with concrete guidance that has gaps.	3 / 5
Workflow Clarity	The "analyze" operation is a batch/scoring task but there is no sequenced process and no validation step (e.g. verify input schema, confirm scores sum correctly); per guideline a batch skill without validation caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Sections exist and a script reference is signaled, but the referenced path points to a "Skill Reference" under another skill's directory (product-team/skills/competitive-teardown/) rather than a local bundle file, so navigation is unclear and one-level-deep references are not cleanly established.	3 / 5
	Total	13 / 20 Passed

Description

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

The description states the domain and a couple of concrete capabilities concisely but lacks an explicit "when to use" trigger clause, which caps its completeness. Trigger term coverage is adequate but not comprehensive.

Suggestions

Add an explicit trigger clause, e.g. "Use when comparing your product against competitors, building competitive matrices, or performing gap analysis."

Broaden trigger terms to include natural user phrasings like "compare competitors", "market positioning", and "feature comparison".

List more concrete actions (e.g. "weight dimensions, compute scores, identify gaps") to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ("competitive analysis matrices") and two concrete actions ("scoring and gap analysis") but stops there, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	The "what" is clear but the "when" is absent; the appended "Usage: /competitive-matrix <analyze> [options]" is invocation syntax, not a trigger clause, so per guideline a missing "Use when..." caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant terms ("competitive analysis", "scoring", "gap analysis") appear but common natural variations users would say ("compare competitors", "market analysis", "positioning") and synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	The phrase "competitive analysis matrices with scoring and gap analysis" carves a clear niche that would not collide with unrelated skills, with only minor overlap risk against general analysis skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/competitive-matrix/SKILL.md
Commit: 19392f7

Reviewed: ~3 hours ago

Table of Contents

Discovery Implementation Validation

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.