Diagnose and reverse traffic loss on existing pages using decay triage framework.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add calm-north/seojuice-skills --skill recover-contentCompatible with
Supported agents
Composite decay scoring across five weighted signals (traffic decline, position drops, CTR decline, content freshness, competitive displacement) prioritizes which pages need action most urgently
Decision tree guides whether to refresh, consolidate, redirect, or retire each decaying page based on topic relevance, intent shifts, and content staleness
Refresh playbooks tailored to content type (blog posts,
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrecover-contentExecute the skills CLI command in your project's root directory to begin installation:
epx add calm-north/seojuice-skills --skill recover-contentFetches recover-content from calm-north/seojuice-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/recover-content
Restart Cursor to activate recover-content. Access via /recover-contentin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
douyin-viral-content
vickyhan924/self-media-script · Marketing · tag: content
linkedin-content
inference-sh/skills · Marketing · tag: content
content-quality-auditor
aaron-he-zhu/seo-geo-claude-skills · Marketing · tag: content
ai-social-media-content
inferen-sh/skills · AI/ML · tag: content
caveman-commit
JuliusBrussee/caveman · Marketing · same category
seo-geo
resciencelab/opc-skills · Marketing · same category
I recommend recover-content for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
recover-content reduced setup friction for our internal harness; good balance of opinion and flexibility.
recover-content has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: recover-content is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for recover-content matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: recover-content is focused, and the summary matches what you get after install.
We added recover-content from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
recover-content fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in recover-content — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
recover-content fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 41