pestel-delta-monitor

Quarterly re-scan of a prior PESTEL analysis. Use when checking which macro factors moved, which assumptions broke, and what's new — turning PESTEL from a workshop artifact into a radar.

Quality

86%

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

Quality

Content

88%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 well-structured, highly actionable instruction-only skill with a clear sequenced workflow, explicit validation gates, and an exact output schema. The main weakness is minor: recurring motivational prose and local referenced files that cannot be verified in the bundle.

Suggestions

Trim the repeated motivational refrains ('workshop artifact into a radar', 'catching the two that moved, not re-debating the twenty') to a single statement to tighten token efficiency.

Ensure the referenced local files (template.md, examples/sample.md, examples/sample-industrial.md) ship alongside SKILL.md so the one-level-deep references resolve for the reader.

Consider folding the schema's per-field label guidance (Fact/Inference, cite) into the inline schema once rather than restating it across Key Concepts and Common Pitfalls.

Dimension	Reasoning	Score
Conciseness	Mostly lean and well-organized with dense, load-bearing sections (Key Concepts, the exact schema, pitfalls); a few motivational refrains ('turning PESTEL from a workshop artifact into a radar', 'catching the two that moved') recur and could be trimmed without loss, sitting just below the fully-lean anchor.	4 / 5
Actionability	Provides a concrete 5-step Application sequence, an exact copy-paste output schema with field-by-field labels, a 4-option Final Step with explicit accept tokens ('1', '1 and 2', 'Verbose Mode'), and worked examples — fully actionable, copy-paste ready guidance for an instruction-only skill.	5 / 5
Workflow Clarity	Clear sequenced workflow with explicit validation gates — prerequisite check (no baseline / scope change → stop), a search-plan gate with 'Continue unless revised' feedback, and a bounded 2-question budget — matching the explicit-checkpoint anchor; not a destructive/batch skill so no cap applies.	5 / 5
Progressive Disclosure	Clean overview structure with one-level-deep, well-signaled references (template.md for the fill-in schema, examples/sample.md and examples/sample-industrial.md for worked runs, plus sibling skills), but the referenced local bundle files (template.md, examples/) are not present in the bundle to verify, a minor organization gap keeping it below the top anchor.	4 / 5
	Total	18 / 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 that states a concrete purpose and an explicit 'Use when' trigger with natural domain terms. It is clearly distinguishable from sibling PESTEL skills and answers both what and when without padding.

Dimension	Reasoning	Score
Specificity	Names the domain ('prior PESTEL analysis') and several concrete actions — 're-scan', 'checking which macro factors moved', 'which assumptions broke', 'what's new' — with only minor coverage gaps, fitting the 'several specific actions' anchor above the 1-2-action midpoint.	4 / 5
Completeness	Explicitly answers both what ('Quarterly re-scan of a prior PESTEL analysis') and when ('Use when checking which macro factors moved, which assumptions broke, and what's new') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural terms a user would say ('PESTEL analysis', 'macro factors moved', 'assumptions broke', 'quarterly') map closely to the listed scenarios; a few common phrasings like 'what's moved since' are implied rather than spelled out, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The 're-scan / delta' framing carves a clear niche distinct from the baseline pestel-analysis sibling, with only minor overlap risk against that closely related skill.	4 / 5
	Total	17 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 missing, 9 suspicious	Warning

	Total	14 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/pestel-delta-monitor/SKILL.md
Commit: a03af68

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