automated-seo-aeo-anysite@1.1.0
CAUTION· install onlyPublisher claims: "A Claude skill that runs an automated, honest SEO + AEO + GEO content program for any website." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-14 and scored it 75/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: README links to a committed installer. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
<summary><b>Do the scripts send my data anywhere?</b></summary> No. They run locally, read and write files in your workspace and make no network requests.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.console.log(`Wrote ${path.join(out, "llms.txt")} and ${posts.length} Markdown copies in ${path.join(out, "md")}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."llms-txt": "Write llms.txt and clean Markdown copies of every post",Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.` npx ${SKILL_NAME} init --name "Acme Gardens" --url https://acme.example --year 2027`,Fix: Pin versions and sources; vendor anything fetched at install time.// Command-line entry point: `npx automated-seo-aeo-anysite <command> [options]`.Fix: Pin versions and sources; vendor anything fetched at install time.dist/automated-seo-aeo-anysite.zipFix: Pin versions and sources; vendor anything fetched at install time.| `scripts/llms-txt.mjs` | `llms.txt` and clean Markdown copies of every post |Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…p.slug); added = true; } } if (!added && round > 0) break; } console.log(`\nBATCH PLAN (${due} post(s), different topics (one per pillar first), distinct headline shapes; cost/pri…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.`Usage: npx ${SKILL_NAME} <command> [options]`,Fix: Pin versions and sources; vendor anything fetched at install time.- `templates/`: `seo.config.json`, `post.md`, `brief.md`, `evidence-pack.md`, `learnings.md`, `backlog.example.json`Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…"\nProposed clusters (pillar candidates):"); for (const c of clusters) console.log(` • "${c.head}": ${c.keywords} keywords, ${c.volume}/mo total, ${c.buyerShare}% buyer-intent. e.g. ${c.top.slice(0, 4).join(" | ")}${c.subthemes.length ? `\…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// Build an llms.txt index and clean Markdown copies of every post, for AI assistants and crawlers.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(`Catch-up rule: expected ${expected}, published ${published} -> publish ${due} post(s) now (max ${max} per run).`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// Creates: seo.config.json, strategy/{LEARNINGS.md,backlog.json,STRATEGY.md}, content/posts/Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.` npx ${SKILL_NAME} qa --json`,Fix: Pin versions and sources; vendor anything fetched at install time.init: "Create seo.config.json, strategy/ and content/posts/ here (never overwrites)",Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…rl <https://site> [--year 2027]` in the workspace folder. It creates `seo.config.json`, `strategy/` and `content/posts/` without overwriting anything. ## 3. Hard rules (never break these) 1. **No…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.<summary><b>I don't have Keyword Planner or Search Console. Can I still start?</b></summary> Yes. Claude will research with web search and mark volumes as unverFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.// node scripts/plan.mjs use seo.config.json (program.postsPerDay / maxPerRun)Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.if (json) console.log(JSON.stringify({ posts: report, errors }, null, 2));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(errors ? `\n✗ ${errors} blocking issue(s). Fix them before publishing.` : "\n✓ All posts pass the quality gate.");Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(`QA: ${selected.length} post(s) checked`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.… !used.has(x.id)) ?? shapes[i % shapes.length]; used.add(sh.id); console.log(` ${i + 1}. ${p.slug} · ${t.id}${isCost(t) ? " [COST TOPIC: sourced figures only]" : ""}${t.type === "pillar" ? " [PILLAR GUIDE]" : ""}\n Q: ${t.question}\n KW: $…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.… const bar = recentBar(posts, t0, "", cfg.ratchet.window); if (bar.n) console.log(`\nQUALITY BAR (median of the last ${bar.n} posts; match or beat every item and add one improvement from strategy/LEARNINGS.md):…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.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
No advisories in OSV for automated-seo-aeo-anysite@1.1.0 as of 6d ago. This is the package itself, not its dependencies.
What would make this Verified
5 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- README links to a committed installer≈ +9 on the totalPin versions and sources; vendor anything fetched at install time.
- Unclaimed publisher≈ +8 on the totalClaim ahmadkhancodes: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- 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.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.