competitive-pricing-intel

Monitor competitor pricing pages via live web scrape and Web Archive snapshots. Track plan changes, tier restructuring, new pricing models, and feature gating shifts. Produces a pricing comparison matrix and flags when a competitor changes packaging. Use when a product marketing team needs to stay current on competitive pricing or when preparing for a pricing change of their own.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

75%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 highly actionable, well-structured instruction skill with a clear phase workflow and complete output templates. Its main weaknesses are redundancy (duplicated trigger lists, definitions of concepts Claude already knows) and the absence of error-handling checkpoints for fragile scraping steps.

Suggestions

Remove the 'Trigger Phrases' section (or the 'When to Use' section) — the two lists are near-duplicates, so keeping one saves ~10 lines of tokens.

Trim the 2C packaging strategy table to just the strategy names, or cut it entirely — definitions of Good-Better-Best, freemium, and usage-based pricing are concepts Claude already knows.

Add a brief validation step after 1A/1B for handling failed fetches or pages with no usable snapshot (e.g., 'If the live scrape returns no plan data, note it in the matrix as "unavailable" and rely on Web Archive/search results').

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but the 'Trigger Phrases' section duplicates the 'When to Use' list almost verbatim, the 2C table defines packaging strategies (Good-Better-Best, freemium, usage-based) Claude already knows, and the 'Core principle' paragraph is editorial padding. These could be tightened or trimmed without losing guidance.	3 / 5
Actionability	Copy-paste-ready search/fetch query blocks, a complete output markdown template with named sections and filename convention ('pricing-comparison-[YYYY-MM-DD].md'), explicit matrix dimensions, and a concrete cron schedule make the guidance fully executable and cover the common cases.	5 / 5
Workflow Clarity	The Phase 0-3 sequence is clearly ordered with sub-steps (1A-1C, 2A-2D), first-run vs. recurring branching, and a severity-rated change-detection table. However, there are no explicit validation checkpoints for failed scrapes, JS-rendered pages, or empty Web Archive results, which keeps it below 5.	4 / 5
Progressive Disclosure	The single-file body is well organized into clearly headed, navigable sections. The ~80-line output template inlined in a 245-line file could arguably live in a reference file, which is a minor organization gap rather than a structural problem.	4 / 5
	Total	16 / 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 in third-person voice that clearly states concrete capabilities and explicit use conditions with low conflict risk. Its only shortcoming is that the when clause describes scenarios rather than the natural trigger phrases users would actually say.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'Monitor competitor pricing pages via live web scrape and Web Archive snapshots', 'Track plan changes, tier restructuring, new pricing models, and feature gating shifts', 'Produces a pricing comparison matrix', 'flags when a competitor changes packaging' — with comprehensive coverage and no significant gaps.	5 / 5
Completeness	It explicitly answers both what (three capability sentences) and when ('Use when a product marketing team needs to stay current on competitive pricing or when preparing for a pricing change of their own'). The when clause names scenarios rather than concrete user trigger phrases, so it falls just below the 5 anchor.	4 / 5
Trigger Term Quality	Natural terms like 'competitor pricing', 'pricing comparison matrix', and 'pricing change' are present, but common user phrasings such as 'what are competitors charging' or 'price increase' appear only in the body's trigger lists, not the description. Good coverage with a few natural terms missing, matching the 4 anchor.	4 / 5
Distinctiveness Conflict Risk	The description carves a clear niche — ongoing competitor pricing-page monitoring with change detection — with triggers that would not plausibly fire for other skills, matching the 5 anchor of a distinct niche with minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/competitive-intel/composites/competitive-pricing-intel/SKILL.md
Commit: cc3e518

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