BC Monitor Content Decay & Score Refresh Opportunities Automatically
Analyze content decay patterns and prioritize refresh opportunities by scoring search ranking loss, engagement drop-off, competitor movement, and outdated data. Use when the user needs content audit recommendations, SEO refresh strategy, or audience re-engagement campaigns.
Analyze content decay patterns and prioritize refresh opportunities by scoring search ranking loss, engagement drop-off, competitor movement, and outdated data.
As a process C 58/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, consistency
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
✓ Guard found no suspicious behaviour. 1 matches are attack strings quoted in this security skill's own documentation.
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
name-longname is longer than 64 chars - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 58/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 8 mutating operations with no state check
- 40Consistency. Frontmatter name (Monitor Content Decay & Score Refresh Opportunities Automatically) differs from the folder (content-decay-refresh-opportunity-scorer)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 85Steps. 50 steps, 2 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 3407 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 274: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 50 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.