CtrlK
BlogDocsLog inGet started
Tessl Logo

swot-analysis

Build an evidence-cited SWOT of one company — yours or a competitor's — from public sources, ending with the S-O/W-T crossings. Use for strategy reviews, board prep, or competitor depth.

76

Quality

96%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

A dense, well-sequenced evidence-cited SWOT workflow with a copy-paste schema, explicit validation checkpoints, and a pitfalls checklist. Progressive disclosure is well-designed but the referenced bundle files (template.md, examples/*.md) are absent from the bundle.

Suggestions

Ship the missing bundle files referenced in the body — `template.md`, `examples/sample.md`, and `examples/sample-industrial.md` are linked but absent from the bundle, so progressive-disclosure navigation breaks.

Alternatively, remove those links until the files exist so the skill carries no dangling references.

DimensionReasoningScore

Conciseness

Dense and substantive with no basic-concept padding — it assumes Claude knows what a SWOT is and spends tokens on protocol, discipline, and a copy-paste schema rather than explanation.

3 / 3

Actionability

Provides a copy-paste output schema, a numbered 4-step procedure, per-quadrant ranking rules (max 5, ranked by defensibility/exploitability), a 4-option Final Step menu, and a do-not-invent list — concrete and executable.

3 / 3

Workflow Clarity

Clear 4-step Application sequence with explicit checkpoints — the search-plan gate ('Continue unless revised'), quadrant reclassification on disguised strategies, and the decision-support sentence as a pass/fail test — plus a pitfalls checklist.

3 / 3

Progressive Disclosure

Well-signaled one-level-deep references (template.md, examples/sample.md, examples/sample-industrial.md) with annotated links, but none of these bundle files actually exist in the bundle, so the disclosure path is broken — caps this at 2.

2 / 3

Total

11

/

12

Passed

Description

100%

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 tight, third-person description that states the concrete deliverable, its evidence-cited provenance, and the distinctive crossings, then gives an explicit 'Use for' trigger clause. All four dimensions hit the top anchor.

DimensionReasoningScore

Specificity

Lists concrete actions — 'Build an evidence-cited SWOT of one company...from public sources, ending with the S-O/W-T crossings' — naming the deliverable and its distinctive crossings rather than vague abstraction.

3 / 3

Completeness

Explicitly answers both what ('Build an evidence-cited SWOT...ending with the S-O/W-T crossings') and when ('Use for strategy reviews, board prep, or competitor depth') with an explicit 'Use for' trigger clause.

3 / 3

Trigger Term Quality

Natural user-facing terms — 'SWOT', 'strategy reviews', 'board prep', 'competitor depth' — are exactly what a user would say when reaching for this skill.

3 / 3

Distinctiveness Conflict Risk

The 'evidence-cited SWOT of one company' niche with S-O/W-T crossings and distinct triggers (SWOT, board prep) is unlikely to collide with other skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 missing, 13 suspicious

Warning

Total

14

/

16

Passed

Repository
deanpeters/Product-Manager-Skills
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.