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

53%

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

40%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 lean, well-sectioned skill that avoids padding, but it stays at a high level of abstraction: capability labels and guardrails rather than executable frameworks, output formats, or a sequenced workflow. It would benefit from concrete analytical structure and worked examples.

Suggestions

Add concrete, actionable guidance: a SWOT template structure, a positioning framework (e.g. axes/attributes), and a go-to-market recommendation output format so Claude can produce consistent deliverables.

Define a light sequence (e.g. review research → SWOT → positioning → timing → GTM recommendations → confidence-qualify) with an explicit checkpoint when research data is insufficient.

Remove the redundancy between the intro paragraph and the '## Skills' list, or have the Skills section expand each item with specifics instead of restating it.

Dimension	Reasoning	Score
Conciseness	The body is short and free of over-explanation, but the '## Skills' list largely restates the intro paragraph and the frontmatter description, creating noticeable redundancy that could be tightened.	3 / 5
Actionability	As an instruction-only skill it gives only high-level labels ('perform SWOT analysis', 'competitive positioning and differentiation strategy') with no framework specifics, output structure, or worked examples, so Claude lacks concrete steps to execute.	2 / 5
Workflow Clarity	The body presents a set of capabilities plus guardrails rather than a sequenced process; there is no step ordering and only soft, implicit checkpoints ('flag when research data is insufficient'), so the workflow is rough with major gaps.	2 / 5
Progressive Disclosure	A short, self-contained skill (under 50 lines) with clearly organized sections (## Skills, ## Guardrails) and no need for external references; the intro/Skills overlap is the only minor organization gap.	4 / 5
	Total	11 / 20 Passed

Description

67%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 specific, well-scoped description that concretely lists its capabilities and includes an explicit 'Use after...' trigger, distinguishing it from sibling skills. It falls short of top marks only because the trigger is workflow-oriented rather than rooted in natural user phrasing, and keyword synonym coverage is incomplete.

Suggestions

Add natural user-facing trigger phrases, e.g. 'Use when the user asks for a SWOT analysis, go-to-market plan, or competitive positioning' rather than only the research-agent workflow dependency.

Include common synonyms users say (e.g. 'market analysis', 'strategy', 'market entry') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the market-strategy domain plus four concrete actions ('SWOT, competitive positioning, market-timing assessment, and go-to-market recommendations'), giving several specific actions with only minor coverage gaps.	4 / 5
Completeness	Clearly states both what it does (the four analyses) and when to use it ('Use after the research-agent has produced market data'), but the 'when' is a workflow dependency rather than concrete user trigger phrases, so it stops short of 5.	4 / 5
Trigger Term Quality	Contains relevant strategy keywords (SWOT, go-to-market, competitive positioning, market timing) but misses common synonyms/variations, and the 'Use after the research-agent' trigger is workflow-tied rather than a phrase a user would naturally say.	3 / 5
Distinctiveness Conflict Risk	Occupies a clear strategy-analysis niche and the explicit research-agent dependency makes triggering fairly distinct, with only minor overlap risk against generic business-analysis skills.	4 / 5
	Total	15 / 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: b600b8a

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.