content-decay-refresh-opportunity-scorer@1.0.0
CAUTION· static onlyPublisher claims: "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." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-08 and scored it 67/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Slack webhook URL. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
export SLACK_WEBHOOK_URL="https://hooks.slack.com/services/YOUR/WEBHOOK"Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.No other findings across 403 lines in 2 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim ncreighton: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Slack webhook URL≈ +4 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.