Revise drafts for search visibility — keyword placement, heading hierarchy, meta fields, internal links — without sacrificing readability. Use after the draft is reader-ready and before publishing.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add Eliyce/paqad-ai --skill seo-optimizer --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Seo Optimizer?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/eliyce-seo-optimizer)More formats (shields.io, HTML) on the badges page.
---
name: seo-optimizer
description: Revise drafts for search visibility — keyword placement, heading hierarchy, meta fields, internal links — without sacrificing readability. Use after the draft is reader-ready and before publishing.
---
# SEO Optimizer
## What It Does
Audits a near-final draft for SEO essentials and emits a checklist of concrete edits, never aesthetic suggestions. Preserves the writer's voice.
## Use This When
Use this after `content-reviewer` has passed the draft and the destination supports search-driven traffic.
## Inputs
- The near-final draft.
- The target keyword set (primary + secondary).
- `references/seo-checklist.md`.
## Procedure
1. Run `scripts/audit-seo.sh <draft> <primary-kw>` to get heading depth, title-tag length, meta-description length, primary-keyword occurrences, and image-alt coverage.
2. Walk `references/seo-checklist.md` against the audit output.
3. Format edits per `assets/output.template.md`.
4. Validate with `scripts/lint-output.sh`.
## Output Contract
- Match `assets/output.template.md`: `## SEO Findings` (each with field/issue/fix) and `## Suggested Title/Meta`.
## Resources
- `references/seo-checklist.md`
- `scripts/audit-seo.sh`
- `scripts/lint-output.sh`
- `assets/output.template.md`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
