CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pestel-analysis

Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/pestel-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 thorough, well-sequenced PESTEL workbook with concrete templates and per-step quality checks. Its main drawbacks are verbosity (repeated purpose, padded rationale) and broken/unsatisfied file references that undermine progressive disclosure.

Suggestions

Remove the verbatim repeat of the frontmatter intent in the Purpose section and trim the 'Why This Works' bullets to cut padding.

Actually create `template.md` and `examples/sample.md` (or drop the references) so the promised one-level-deep split is real rather than dangling.

Move the six full fill-in template blocks into `template.md`, keeping only a concise overview and the synthesis step inline in SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-structured, but the verbatim repeat of the frontmatter intent under "Purpose", the padded "Why This Works" bullets, and per-factor prose add length that could be trimmed.

3 / 5

Actionability

Each step ships a fill-in markdown template with specific worked examples (EU AI Act, GDPR, CBAM), giving concrete executable guidance with only minor gaps; absence of code is fine for an instruction-only skill.

4 / 5

Workflow Clarity

A clear 9-step sequence (scope → six factors → synthesize → update) with "Quality checks" after each step serving as checkpoints; no error-recovery feedback loop, but none is really applicable to an analysis skill.

4 / 5

Progressive Disclosure

References to `template.md` and `examples/sample.md` are signaled, but neither file exists in the bundle, and the full per-factor templates are inlined in the body rather than split into the referenced file.

3 / 5

Total

14

/

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: concrete domain, explicit "Use when" trigger, and a distinct named framework. The only weak spots are a single repeated verb and minor overlap with sibling strategy skills.

DimensionReasoningScore

Specificity

"Analyze political, economic, social, technological, environmental, and legal forces" names the domain plus six concrete force categories, but the single verb "Analyze" applied across them leaves minor coverage gaps versus a multi-verb anchor.

4 / 5

Completeness

It explicitly states what ("Analyze ... forces") and when ("Use when external market shifts could materially affect a product, roadmap, or strategy") with a concrete trigger clause, matching the top anchor.

5 / 5

Trigger Term Quality

"external market shifts", "product", "roadmap", "strategy" are natural phrases a PM would say, though a few common synonyms (e.g. "regulation", "market entry") are missing.

4 / 5

Distinctiveness Conflict Risk

PESTEL is a named, distinct framework with clear niche triggers, but it sits among related market-intelligence/strategy skills (it cross-references several), creating minor overlap risk rather than zero.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

deanpeters/Product-Manager-Skills

Path

skills/pestel-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.