strategy-agent

Market strategy analyst performing SWOT, competitive positioning, market-timing assessment, and go-to-market recommendations from research findings. Use after the research-agent has produced market data.

Quality

60%

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 ./modules/skills/src/main/resources/META-INF/skills/strategy-agent/SKILL.md

Quality

Content

45%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 short and cleanly sectioned but hollow: it names capabilities rather than telling the agent how to execute them. There is no workflow ordering, no output format, and no worked example, so an agent reading it would know what it is supposed to produce but not how to produce it.

Suggestions

Add a numbered workflow that sequences the deliverables — e.g., 1. review research findings, 2. build the SWOT from cited data, 3. derive positioning and timing conclusions, 4. issue go-to-market recommendations each qualified with a confidence level — so the multi-step task has an explicit order.

Define concrete output artifacts, such as the structure of the SWOT table, a positioning statement template, and how confidence levels should be expressed (e.g., high/medium/low with a one-line justification).

Remove the redundant restatement of the same four capabilities across the intro paragraphs and the 'Skills' list; state them once and spend the saved tokens on the workflow and output format.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept over-explanation, but the same four capabilities are restated three times ('You perform SWOT analysis, competitive positioning, and go-to-market strategy' … '- SWOT analysis (strengths, weaknesses, opportunities, threats)'), which is trimmable redundancy. Not 5 because not every token earns its place.	4 / 5
Actionability	The guidance is descriptive rather than instructive — 'You perform SWOT analysis', 'Qualify recommendations with confidence level' — with no steps, output format, or example deliverables. This is the 'minimal concrete guidance; high-level hints' anchor; not 3 because there is no concrete partial procedure at all.	2 / 5
Workflow Clarity	No sequence of any kind is given for producing the SWOT, positioning, timing, and go-to-market deliverables; even a rough ordering is absent. The simple-skill exception does not apply since this is a multi-part analysis task, matching the 'steps missing; no sequence' anchor.	1 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references (no bundle files exist), and is organized into clear headed sections (intro, Skills, Guardrails), which per the rubric guideline earns full marks for a single-file skill.	5 / 5
	Total	12 / 20 Passed

Description

75%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 solid description: third-person voice, four concrete capability statements, and an explicit use condition. Its main limitation is that the trigger guidance is oriented to pipeline orchestration ('after the research-agent') rather than the natural phrases a user would say when needing this skill.

Dimension	Reasoning	Score
Specificity	The description lists four named concrete actions in third person — 'performing SWOT, competitive positioning, market-timing assessment, and go-to-market recommendations' — matching the 'several specific actions, minor gaps' anchor. Not 5 because 'competitive positioning' leans framework jargon and coverage of the strategy domain is not exhaustive.	4 / 5
Completeness	Both 'what' (the four analysis activities) and 'when' ('Use after the research-agent has produced market data') are explicitly stated. Not 5 because the 'when' is a pipeline-ordering condition rather than concrete user trigger phrases like 'when the user asks for a SWOT analysis'.	4 / 5
Trigger Term Quality	Natural user keywords are present ('SWOT', 'competitive positioning', 'go-to-market'), giving good coverage, but common synonyms like 'competitive analysis', 'market entry strategy', or 'strategic planning' are missing, and the trigger leans on internal pipeline phrasing ('after the research-agent') rather than user-natural requests.	4 / 5
Distinctiveness Conflict Risk	It carves a clear market-strategy niche and the sequencing note ('after the research-agent') further distinguishes it, but there is minor overlap risk with sibling business-analysis or research-agent skills.	4 / 5
	Total	16 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: Atmosphere/atmosphere
Path: modules/skills/src/main/resources/META-INF/skills/strategy-agent/SKILL.md
Commit: 1c968d5

Reviewed: 2 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.