---
name: webops-content-pruning
description: "Use when reviewing obsolete or redundant content for keep, refresh, merge, redirect, or retire proposals."
---

# Webops Content Pruning

## Purpose

Use this skill for reviewing obsolete or redundant content for keep, refresh, merge, redirect, or retire proposals. Its primary sources are ContentGraph, accuracy review, measured providers, backlinks, and business context.

## Workflow

1. Identify redundancy, invalidity, obsolete purpose, maintenance burden, and unique value.
2. Check search, analytics, backlinks, links, conversions, and non-traffic utility when available.
3. Model destination and redirect implications before recommending removal.
4. Require approval and migration proof for ACT.

## Required Output

- pruning candidates.
- retain/refresh/merge/redirect/retire rationale.
- risk and destination plan.

Every output must name target/scope, evidence class, retrieval or run time,
unavailable checks, permission mode, and comparison baseline where applicable.

## Boundaries

Never recommend deletion solely because traffic is low. Preserve OBSERVE/PROPOSE/ACT boundaries, provider cost and credential
limits, stable finding identity, and the distinction among finding,
recommendation, action, and outcome. Never store credentials or fabricate
provider data, rankings, indexing, citations, compliance, or causation.

## Verification

Validate source artifacts with their owning tool before interpretation. Run
the current repository's WebOps cross-reference validation when agent, skill,
tool, capability, or workflow mappings change.