CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

swot-analysis

Perform a detailed SWOT analysis — strengths, weaknesses, opportunities, and threats with actionable recommendations. Use when doing strategic assessment, competitive analysis, or evaluating a product or business position.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./pm-product-strategy/skills/swot-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 delivers a clear, actionable SWOT workflow with specific output counts and a well-sequenced process, but roughly a third of the content pads rather than teaches: the Metadata section duplicates the frontmatter, the quadrant bullet lists restate factors Claude already knows, and the Notes are generic. Trimming those and adding a compact example output would materially tighten it.

Suggestions

Remove the "Metadata" section — it duplicates the name, description, and triggers already present in the YAML frontmatter.

Trim the four quadrant bullet lists (28 bullets of generic factors such as "Brand recognition or reputation") down to only non-obvious or domain-specific factors, or move them to a reference file — Claude can generate standard SWOT factors unaided.

Add a brief worked example or output template (e.g., a condensed sample SWOT with one strength, cross-reference insight, and recommendation) to make the expected deliverable format concrete, and cut Notes lines that restate common knowledge.

DimensionReasoningScore

Conciseness

The "Metadata" section duplicates the frontmatter, the 28 quadrant bullets ("Brand recognition or reputation", "Resource constraints (budget, team size, skills)") enumerate factors Claude already knows, and "Notes" states the obvious ("SWOT is internal to external assessment"). Multiple padded sections keep it below anchor 4, while the genuinely useful Output Process and Strategic Applications keep it above anchor 2.

3 / 5

Actionability

Concrete, executable guidance throughout: "Identify 5-7 strengths", "Develop 3-5 strategic recommendations", "Prioritize actions and owners", "Identify metrics to track progress", plus specific cross-reference questions. For an instruction-only skill this meets anchor 4; not 5 because there is no worked example or output template showing the expected format.

4 / 5

Workflow Clarity

The "Output Process" is a clearly sequenced numbered 1-8 workflow, with step 5's cross-reference questions ("How do we leverage strengths to capture opportunities?") acting as a synthesis checkpoint. Fits anchor 4 (clear sequence, most checkpoints present); not 5 because there is no explicit validation or output-review step, though no destructive/batch operation exists to trigger the cap.

4 / 5

Progressive Disclosure

Well-organized sections with clear headers and no external references, none of which are strictly needed. Fits anchor 4 (good structure, minor organization gaps): the redundant Metadata section and the generic inlined factor lists are minor placement gaps, and at ~92 lines it does not qualify for the under-50-line simple-skill exception to score 5.

4 / 5

Total

15

/

20

Passed

Description

83%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 strong description: it uses third-person voice, clearly states what the skill does with enumerated components, and includes an explicit "Use when..." clause with concrete triggers. The only gaps are a few missing natural trigger variations (e.g., "SWOT matrix") and slightly broad secondary triggers that overlap with adjacent strategy skills.

DimensionReasoningScore

Specificity

"Perform a detailed SWOT analysis" and "strengths, weaknesses, opportunities, and threats with actionable recommendations" enumerate the concrete components and the output type. Falls between anchor 3 (1-2 concrete actions) and anchor 4 (several specific actions): the S/W/O/T enumeration plus recommendations reads as several deliverables, but they are facets of a single analysis task rather than distinct operations, so not 5.

4 / 5

Completeness

Explicitly answers "what" ("Perform a detailed SWOT analysis — strengths, weaknesses, opportunities, and threats with actionable recommendations") and "when" ("Use when doing strategic assessment, competitive analysis, or evaluating a product or business position") with concrete trigger phrases. Matches the anchor-5 example pattern exactly; anchor 4 would require the when-clause to be less explicit than it is.

5 / 5

Trigger Term Quality

"SWOT analysis", "strategic assessment", "competitive analysis", and "evaluating a product or business position" are phrases a user would naturally say. Matches anchor 4 (good coverage, a few natural terms missing); not 5 because common variations like "SWOT matrix" or a bare "strengths and weaknesses" are absent.

4 / 5

Distinctiveness Conflict Risk

"SWOT analysis" is a distinct named methodology giving a clear niche, but the broader triggers "strategic assessment" and "competitive analysis" create minor overlap risk with adjacent strategy/analysis skills. Fits anchor 4 (mostly distinct, minor overlap); not 5 because those broad triggers could pull requests meant for other skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phuryn/pm-skills

Path

pm-product-strategy/skills/swot-analysis/SKILL.md

Reviewed

Table of Contents

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.