dyz-gongwen-skills
公文写作 Skills|AI 公文写作助手:防编造、守保密、GB/T 9704 一键排版,覆盖 22 种文书,支持 Claude Code / Codex / Cursor
翻訳待ち
リポジトリ情報はまだ収集していません。
No updates detected yet. GitHub releases will appear here.
Claude Code skills and agents for SEO, AEO and GEO: research, write, fact-check and audit pages that rank in Google and get cited by AI search.
翻訳待ち
Loading the full README.
Read the full README ↗Jump to: Quick start · Other AI tools · What the auditor checks · How it fits together · FAQ · Credits
| Pillar | What it covers |
|---|---|
| SEO | Site and page audits, technical SEO, schema, sitemaps, hreflang, E-E-A-T, backlinks, local and maps |
| AEO (answer engines) | Answer-first writing, FAQs, featured-snippet structure, structured data |
| GEO (AI search) | AI crawler access, llms.txt, citability, brand mentions, ChatGPT / Perplexity / AI Overviews tuning |
| VEO (voice) | Spoken answers, voice search, local intent |
| Content and growth | Blog production from brief to fact-check, plus CRO, offers, pricing and editorial polish |
npx seo-aeo-geo-kit audit https://your-site.com/page
You get a score out of 100 for SEO, AEO and GEO, a pass/fail list, and the top fixes. Add --summary for just the score and fixes.
/plugin marketplace add alpit-patel/seo-aeo-geo-kit
/plugin install seo-aeo-geo-kit@seo-aeo-geo-kit
Using Codex, OpenCode or Antigravity instead? See Works with Claude Code, Codex, OpenCode, Antigravity and more. Then ask in plain language: "audit this page for SEO, AEO and GEO", "write a blog post on X and fact-check it", or "check whether AI crawlers can read my site".
npx seo-aeo-geo-kit install --only seo,geo # into ./.claude/skills
npx seo-aeo-geo-kit install --global # into ~/.claude/skills
npx seo-aeo-geo-kit list --family GEO
install copies skill folders only. The plugin also includes the helper scripts.
All skills use the open Agent Skills format (SKILL.md folders), so they are not tied to one tool. One command installs them for your tool:
| Tool | Install | Where it goes |
|---|---|---|
| Claude Code (full kit) | /plugin marketplace add alpit-patel/seo-aeo-geo-kit then /plugin install seo-aeo-geo-kit@seo-aeo-geo-kit | managed by the plugin system |
| OpenAI Codex | npx seo-aeo-geo-kit install --target codex --global | ~/.codex/skills (project: .agents/skills) |
| OpenCode | npx seo-aeo-geo-kit install --target opencode --global | ~/.config/opencode/skills (project: .opencode/skills) |
| Google Antigravity | npx seo-aeo-geo-kit install --target antigravity --global | ~/.gemini/antigravity/skills (project: .agent/skills) |
| Any other Agent Skills tool | npx seo-aeo-geo-kit install --target agents --global | ~/.agents/skills (or use --dest <folder>) |
Drop --global to install into the current project instead. Run npx seo-aeo-geo-kit doctor to see which tools are on your machine. Restart your agent afterwards, then ask in plain language: "audit this page for SEO, AEO and GEO".
For tools other than Claude Code the installer makes each skill portable: it keeps only the standard frontmatter fields (author credits move into metadata, never dropped), installs the helper files next to the skills in a _seo-aeo-geo-kit folder, and points every helper-script path at it. Optional one-time setup for the Python helpers: python <skills-folder>/_seo-aeo-geo-kit/scripts/runtime.py setup.
Good to know
/seo audit) is Claude Code only. In other tools the same skills work when you ask in plain language, and the agent follows the steps itself.--dest <folder>.system/routing.md: which skills run for which task, and in what order.system/quality-gates.md: the checks a deliverable must pass.system/evidence-policy.md: no invented evidence, ever.system/skill-registry.json: machine-readable index of every skill.templates/: content brief, project context and QA report templates.scripts/: Python helpers for Search Console, GA4, autocomplete research and text cleanup. They read your own config files (see the *.example.json files).Many skills call Python helpers (page rendering, Google Search Console and GA4, PageSpeed, schema validation, and more). All 42 that the skills reference are bundled in scripts/, plus 11 standard-library blog helpers (render, preflight gates, prose lint, readability) that run with plain Python and need no setup. They run through a managed, sandboxed Python environment (Python 3.11 to 3.14), created the first time you run /seo setup inside Claude Code. Some use optional services such as Google or Moz and need your own keys. The kit works without them: skills fall back to manual checks.
25 deterministic checks: title, meta description, headings, canonical, mobile, image alt text, internal links and Open Graph (SEO); JSON-LD, FAQ markup, answer-first opening, lists and question headings (AEO); AI-crawler access in robots.txt, llms.txt, author and date, external citations, facts and entity schema (GEO).
It reports what is missing. It does not predict rankings, and nothing replaces real content quality.
Generative Engine Optimization: making your content easy for AI systems such as ChatGPT, Perplexity and Google AI Overviews to find, understand and cite.
Answer Engine Optimization: structuring content so search features and assistants can lift a direct answer, such as featured snippets and voice answers.
No. Nobody can. It gives you a repeatable process and a checklist.
No. The auditor and most skills need none. A few helper scripts use optional services (Google Search Console, GA4, DataForSEO). When a helper script is not bundled, the skills fall back to manual checks and say so.
The auditor only fetches the URL you give it, plus that site's robots.txt and llms.txt. The skills run inside your own agent (Claude Code, Codex, OpenCode or Antigravity) under your own settings.
Curated and maintained by Alpit Patel, who wrote the auditor, installer, validator and the routing and quality system. The kit also builds on MIT-licensed work by AgriciDaniel, Zubair Trabzada, Corey Haines, Siqi Chen, Guillaume Meyer, puneetindersingh and others. See THIRD_PARTY_NOTICES.md for the full list. Each skill keeps its original license file.
See CONTRIBUTING.md. Before a pull request: npm test, npm run validate and claude plugin validate ..
MIT. See LICENSE and THIRD_PARTY_NOTICES.md.