Individual skill
content-pruning-review
Remove redundant or unsupported page content.
skills/content-pruning-review/SKILL.md
Source commit 9922fa0af0aea32443cf7365ef5024dc7797382d
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 137
- Repository last updated
- Oct 22, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- accessibility Repository topic
- codex Repository topic
- codex-skills Repository topic
- frontend Repository topic
- motion Repository topic
- nextjs Repository topic
- react Repository topic
- tailwind Repository topic
- web-design Repository topic
- agent-skills Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,106 bytesSKILL.mdcore · 1,106 bytesagents/openai.yamlasset · 264 bytesreferences/content-pruning-review-guide.mddoc · 2,662 bytes
Read excerpt
# Content Pruning Review
Use this skill to make the page sharper by deleting what dilutes the main decision path.
## Workflow
1. Inspect the requested copy/content, intended action, source facts and brand conventions; expand to IA, forms or metadata only if affected.
2. Read [Content Pruning Review Guide](references/content-pruning-review-guide.md) before changing headings, sections, CTAs, metadata, labels, or UI copy.
3. Draft from evidence: real product/service facts, proof, objections, user tasks, and constraints.
4. Replace generic claims with specific language or remove them.
5. When implementing copy, inspect its affected rendered desktop/mobile states for wrapping and clarity. Copy-only output does not require site changes.
## Scoped execution
