SKILLEMALL.ai
GitHub ↗ RU Sign in

AF competitive-analysis

Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations. For a one-off teardown of a single rival use competitor-teardown; for a recurring market briefing use competitive-intelligence-monitor.

mohitagw15856/pm-claude-skills Agent Skills author: mohitagw15856 MIT 4 files body ≈ 1 603 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations.

As a process F 49/100 · Will not run — References files that are not bundled: ../professional-brain/SKILL.md

AnalyzerMarketingWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
81
Run on models
none yet
Process rating
F
49/100
Will not run
References files that are not bundled: ../professional-brain/SKILL.md
Tools and files w 18
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: competitive-analysis (mohitagw15856/pm-claude-skills)

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../professional-brain/SKILL.md

Process rating: all ten parameters 49/100

Will not run. References files that are not bundled: ../professional-brain/SKILL.md
  • 0Tools and files. 1 referenced file(s) missing: ../professional-brain/SKILL.md
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 39 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1603 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 605: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 39 items
  • +3Output format is stated explicitly
  • +4Reference files are cited in the instructions (1 of 2)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.