keyword-cannibalization@0.1.0
CAUTION· static onlyPublisher claims: "Find and fix keyword cannibalization: queries where two or more of the site's own pages get impressions in Google, which of those splits actually cost traffic, and the fix for each (merge and 301, retarget, canonical, internal links, noindex, or de-optimize). Use when the user mentions cannibalization, two pages competing for the same keyword, pages swapping positions in Search Console, asks which page should rank for a query, or wants to consolidate overlapping content. For mapping a keyword list to pages before they exist, use keyword-clustering instead." 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-16 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. 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
…ere the output goes:** the split table as `keywords/cannibalization-<YYYY-MM-DD>.csv`, with the verdict and fixes at the top of `keywords/cannibalization-<YYYY-MM-DD>.md`. Save it in the project's SEO folder (see `seo-project-setup`); if t…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.No other findings across 175 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
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim winsley-jeune: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.