Audit existing content across a site to decide what to keep, update, merge, redirect, or delete. Use this skill whenever the user wants to audit existing content, fix content decay, resolve keyword cannibalization, prune underperforming pages, prioritize content updates, or apply a keep/update/merge/redirect/delete framework to a content library. Triggers on content audit, content decay, content refresh, cannibalization, keyword cannibalization, prune content, delete pages, redirect old pages, content inventory, what to keep, what to update, content scorecard, evergreen refresh. Also triggers when traffic is dropping site-wide and the cause might be content quality, even if 'audit' is not said explicitly.
67
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is an excellent skill description that thoroughly covers specific capabilities, provides extensive natural trigger terms, explicitly states both what the skill does and when to use it, and occupies a clearly distinct niche. The inclusion of an implicit trigger scenario (traffic dropping site-wide) adds additional value. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: audit existing content, decide what to keep/update/merge/redirect/delete, fix content decay, resolve keyword cannibalization, prune underperforming pages, prioritize content updates, and apply a keep/update/merge/redirect/delete framework. | 3 / 3 |
Completeness | Clearly answers both 'what' (audit existing content to decide what to keep/update/merge/redirect/delete) and 'when' (explicit 'Use this skill whenever...' clause with detailed trigger scenarios, plus an additional implicit trigger for traffic drops). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'content audit', 'content decay', 'content refresh', 'cannibalization', 'prune content', 'delete pages', 'redirect old pages', 'content inventory', 'what to keep', 'what to update', 'content scorecard', 'evergreen refresh'. Also includes the implicit trigger of traffic dropping site-wide. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around content auditing and the keep/update/merge/redirect/delete framework. The specific terminology like 'keyword cannibalization', 'content decay', 'content scorecard', and 'prune content' make it highly distinct and unlikely to conflict with other content-related skills like content creation or SEO keyword research. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-organized content audit skill with a strong decision framework, clear workflow sequencing, and useful failure patterns. Its main weaknesses are verbosity (the 5-action signals section is lengthy) and lack of truly executable/actionable artifacts like scripts, formulas, or tool-specific commands. The referenced bundle files don't exist, undermining the progressive disclosure structure.
Suggestions
Add executable artifacts: a Python or shell script for pulling Search Console data, sample spreadsheet formulas for scoring, or a concrete CSV template rather than just describing columns.
Condense the 5-action framework signals into a single comparison table (Action | Key Signals | Typical Metrics) to reduce token count by ~40% in that section.
Ensure the referenced files (references/audit-template.md, references/cannibalization-resolution.md) actually exist in the bundle, or inline their critical content if the bundle is not available.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is generally well-structured and avoids explaining basic SEO concepts, but it's verbose in places—the 5-action framework section repeats signal patterns that could be condensed into a table, and the 'When to use' / 'When NOT to use' sections add moderate overhead. The scoring inputs table and decision matrix are efficient, but overall the skill could be tightened by ~30%. | 2 / 3 |
Actionability | The framework, decision matrix, and scoring table provide concrete guidance on what to evaluate and how to decide. However, there are no executable code snippets, no specific tool commands (e.g., Screaming Frog export commands, GSC API queries, spreadsheet formulas), and the workflow steps remain at a procedural description level rather than copy-paste ready. The output format is well-specified but not templated with actual formulas or scripts. | 2 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with logical progression from inventory through measurement. It includes validation checkpoints (re-crawl after each batch, 30/60/90 day measurement), batch processing guidance, and the failure patterns section serves as an effective error-recovery checklist. The decision tree provides an explicit branching logic for classification. | 3 / 3 |
Progressive Disclosure | The skill references two supporting files (audit-template.md and cannibalization-resolution.md) which is good structure, but no bundle files were provided, meaning those references are broken. The main body is quite long (~200+ lines) and some sections like the detailed 5-action framework signals could be moved to a reference file, keeping the SKILL.md as a leaner overview. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
8e70d03
Table of Contents
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.