CtrlK
BlogDocsLog inGet started
Tessl Logo

content-refresh-system

Systematic content refresh discipline. Quarterly audits, refresh prioritization (which pieces, when, how deep), refresh-vs-merge-vs-delete decisions, the lifecycle that distinguishes intentional refresh from set-and-forget decay. Builds on the refresh sections of pillar-content-architecture and editorial-qa with a program-level discipline. Triggers on content refresh, content decay, content audit, refresh prioritization, content lifecycle, refresh strategy, traffic decay, ranking drop, content freshness, evergreen content, content maintenance. Also triggers when traffic is eroding silently across an aging content library, when teams cannot decide which pieces to refresh, or when refresh work is happening but the impact is unclear.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is a well-structured, actionable editorial playbook with excellent progressive disclosure and clear workflow sequencing plus feedback loops. Its main weakness is conciseness: it recapitulates its own content across the framework list, reference index, and closing, which could be tightened without losing clarity.

Suggestions

Collapse the redundancy between the intro's suite distinctions and the 'What this skill covers' section so each skill relationship is stated once.

Trim the 12-consideration framework or the closing so they do not re-list what the body sections already detail; consider making the framework a pure checklist of pointers rather than re-explanations.

Fold the per-file summaries in the 'Reference files' index into the in-section 'Detail in...' links (or vice versa) to avoid stating each reference's purpose twice.

DimensionReasoningScore

Conciseness

The body conveys genuine editorial expertise rather than concepts Claude already knows, but it recapitulates itself: suite distinctions appear in both the intro and 'What this skill covers', the 12-consideration framework restates the body sections, and the reference-file index plus closing restate earlier summaries. Not a 1 because the verbosity is self-recapitulation, not padding with basic concepts; not a 3 because the repetition could be tightened without losing substance.

2 / 3

Actionability

Concrete and specific throughout: signal thresholds ('40%+ in a month', '90+ day window'), per-depth time investments ('30-90 minutes', '2-4 hours'), capacity percentages ('5 of 20 slots', '30-40%'), explicit tracking fields, and a 12-item checklist — fully actionable guidance for an instruction-only skill.

3 / 3

Workflow Clarity

Clear sequence (audit -> signals -> prioritization -> depth -> disposition -> execution -> re-promotion -> tracking) anchored by the ordered 12-consideration checklist, with explicit checkpoints (the litmus test) and feedback loops (effectiveness measurement at 30/90 days and the refresh-that-did-not-work review).

3 / 3

Progressive Disclosure

The body is a concise overview that signals nine one-level-deep reference files — each marked 'Detail in [references/...]' at the relevant section and re-indexed in a consolidated 'Reference files' section — and all nine referenced paths resolve to real files in ./references/.

3 / 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.

The description is specific, trigger-rich, complete with explicit what-and-when guidance, and clearly distinct from related skills, all in third person. It is a strong, well-scoped description with no meaningful gaps.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Quarterly audits, refresh prioritization (which pieces, when, how deep), refresh-vs-merge-vs-delete decisions' — matching the anchor for naming several specific actions.

3 / 3

Completeness

Explicitly answers both what (the refresh discipline and its components) and when via the 'Triggers on...' and 'Also triggers when...' clauses, matching the anchor that requires both.

3 / 3

Trigger Term Quality

Strong natural-term coverage via 'Triggers on content refresh, content decay, content audit, refresh prioritization, content lifecycle, refresh strategy, traffic decay, ranking drop, content freshness, evergreen content, content maintenance', terms an editorial lead would actually say.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche by stating it 'Builds on the refresh sections of pillar-content-architecture and editorial-qa with a program-level discipline', distinguishing it from sibling skills and unlikely to trigger for the wrong one.

3 / 3

Total

12

/

12

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.

Validation15 / 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
rampstackco/claude-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.