Ai Seo

v1.0.0

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,...

0· 97·0 current·0 all-time
byMario Karras@mariokarras·duplicate of @mrhuang09/ai-seo
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (AI SEO) matches the SKILL.md content: auditing AI visibility, recommending content patterns, checking robots.txt and platform-specific signals. It does not ask for unrelated binaries, cloud creds, or system-wide access.
Instruction Scope
Runtime instructions are focused on AI visibility audits and content optimization. They explicitly instruct the agent to read .agents/product-marketing-context.md (or .claude/...) if present and to check site crawlability/robots.txt and platform behavior — all reasonable for this task. Note: reading product-marketing-context.md may expose internal product details; network access to check robots.txt and platform results is implied.
Install Mechanism
No install spec and no code files — instruction-only skill — so nothing will be written to disk or installed by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. The checks it recommends (robots.txt, indexing) do not require secrets and are proportional to the stated goal.
Persistence & Privilege
Flags show always:false and normal user-invocable/autonomous settings. The skill does not request permanent presence or elevated platform privileges.
Assessment
This skill appears internally consistent for AI search optimization. Before installing: (1) Review any product-marketing-context.md files the skill will read — they can contain sensitive internal information, so restrict access if needed. (2) Be aware the skill implies network checks (robots.txt, searching platforms) — if you run it in a sensitive environment, run on staging or with limited network access first. (3) If you follow its advice to allow AI bots in robots.txt, understand the tradeoff: improved AI visibility vs broader scraping/training exposure. (4) For regulated domains (health, legal, finance), have subject-matter experts review any content changes recommended by the skill. If you need a stricter posture, test the skill in a sandboxed agent workspace and audit any file reads or outbound requests it makes when invoked.

Like a lobster shell, security has layers — review code before you run it.

latestvk973em3h3nhb2zkzxc1pqwmv458355n9

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments