Name: arn-spark-stress-competitive
Rating: 74.4 (1 reviews)
Author: AppsVortex

arn-spark-stress-competitive

This skill should be used when the user says "competitive analysis", "gap analysis", "competitive gap", "stress competitive", "compare competitors", "feature comparison", "competitive stress test", "market comparison", "competitor analysis", or wants to stress-test a product concept by conducting deep competitive gap analysis with feature comparison, gap identification, and positioning assessment. Produces a competitive report with a feature matrix, per-competitor analysis, and recommended concept updates.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%Weight 40%Scale 1-3

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

A well-structured orchestration skill with concrete paths, agent invocations, and parameters, a clear sequenced workflow with prerequisite validation and error-recovery loops, and properly split one-level references. Its only weakness is procedural verbosity in the verbatim message template and repeated option lists.

Suggestions

Tighten the Step 7 user-facing summary: describe the required summary fields concisely instead of reproducing the full verbatim message, letting Claude phrase it naturally.

Condense the three AskUserQuestion fallback cascades (data-availability fallback plus the two error-handling cases) into a shared reference pattern rather than restating full option lists each time.

Trim the introductory 3-stage process summary, which partly restates the Workflow steps that immediately follow.

Dimension	Reasoning	Score
Conciseness	It avoids explaining concepts Claude already knows and uses tables efficiently, but the verbatim user-facing summary template in Step 7 and three restated AskUserQuestion option-lists are procedural verbosity that could be tightened, fitting the 'mostly efficient but could be tightened' anchor rather than the every-token-earns-its-place level 3.	2 / 3
Actionability	Gives fully concrete, executable guidance for an orchestration skill — exact reference paths, the agent name 'arn-spark-market-researcher' with deep-analysis mode and model-parameter source, exact output path, and specific categorization schemes (Core/Differentiating/Table-Stakes; Yes/No/Partial/Planned/Unknown) — so it is not penalized for lacking code.	3 / 3
Workflow Clarity	A clear 7-step sequence is preceded by an explicit prerequisite validation gate ('Do not proceed without it', Data Availability table) and followed by error-recovery feedback loops (retry with broader terms, simplified-prompt retry, AskUserQuestion fallbacks), matching the clear-sequence-with-validation-and-feedback anchor.	3 / 3
Progressive Disclosure	The body is an overview/workflow that signals two one-level-deep references ('Load the gap analysis framework and report template') at paths that resolve to real files in ./references/, with the framework and template appropriately split out rather than inlined.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 that explicitly states what the skill does, when to use it via natural trigger phrases, and occupies a distinctive niche. It hits the top anchor on every dimension with concrete actions and explicit trigger guidance.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and outputs — 'feature comparison, gap identification, and positioning assessment' and 'a competitive report with a feature matrix, per-competitor analysis, and recommended concept updates' — matching the anchor for multiple specific concrete actions rather than the domain-only level 2.	3 / 3
Completeness	Answers both 'what' (deep competitive gap analysis producing a report with matrix/per-competitor analysis/updates) and 'when' with an explicit trigger clause ('This skill should be used when the user says...'), so it is not capped at 2 by the missing-trigger guideline.	3 / 3
Trigger Term Quality	Provides broad coverage of natural phrases a user would say ('competitive analysis', 'gap analysis', 'competitive gap', 'compare competitors', 'feature comparison', 'market comparison', 'competitor analysis'), matching the good-coverage anchor rather than the some-keywords-missing level 2.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (competitive stress-test of a product concept) with distinctive triggers like 'competitive stress test' and 'stress competitive', making conflict with other skills unlikely rather than the overlapping level 2.	3 / 3
	Total	12 / 12 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: AppsVortex/arness
Path: plugins/arn-spark/skills/arn-spark-stress-competitive/SKILL.md
Commit: 7f87870

Reviewed: 14 days 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.