agentkit-seo
Route broad or ambiguous AgentKit SEO work to the right module while keeping context scoped. Use when a request spans multiple surfaces, asks for overall digital-presence strategy, involves provider or install architecture, needs agent-context planning, or the correct platform skill is unclear.
What this skill does
# AgentKit SEO ## Overview Use this skill as the orchestrator for the whole repository. Its main job is to select the right module skill, avoid loading irrelevant platform rules, and sequence cross-platform work in a sane order. ## Routing workflow 1. Identify the target surface from the request. 2. Load only the matching module skill unless the user explicitly asks for a cross-platform pass. 3. If the request spans multiple surfaces, start with `agentkit-seo-agent-context-optimization` so the factual source of truth is stable before editing platform outputs. 4. If the request involves technical issues with the skill system, consult the main repository documentation. For broad requests with no clear surface: - Active applications or job-description tailoring: route to `agentkit-seo-cv-ats`. - Recruiter discovery or profile search: route to `agentkit-seo-linkedin`. - Proof-of-work, repositories, or developer credibility: route to `agentkit-seo-github` or `agentkit-seo-web-portfolio`, based on the supplied asset. - Audience building, posting strategy, or public conversation loops: route to `agentkit-seo-x-twitter`. - Conflicting, scattered, or cross-platform facts: route to `agentkit-seo-agent-context-optimization` first. ## Token discipline - Route to one module by default. - Load the agent context file before platform references only when facts, consistency, or cross-surface rewriting matter. - Prefer public URL inspection, local search, or a compact pasted section over asking the user to dump every asset into the prompt. - Summarize inspected inputs and ask for the smallest missing input set. - Do not expand into algorithm explanation unless the user asks why. ## Intake workflow - If the user already has an agent context file, ask for or use its explicit path before rewriting platform assets. - If the task spans multiple surfaces, or the user's facts are scattered, recommend creating or repairing the agent context file first. - Do not block a narrow one-off edit on a full context file when the supplied material is already enough. - For public URLs, fetch or inspect public material when tools allow it and cite which source was used. - For private or login-gated surfaces, ask the user for pasted section text, screenshots, exports, or a local text file instead of guessing. - If critical facts are missing, ask only for the minimum extra inputs needed to proceed. ## Module map - LinkedIn work: `agentkit-seo-linkedin` - GitHub work: `agentkit-seo-github` - CV or ATS work: `agentkit-seo-cv-ats` - Web portfolio work: `agentkit-seo-web-portfolio` - X or Twitter work: `agentkit-seo-x-twitter` - Personal source-of-truth context work: `agentkit-seo-agent-context-optimization` ## More Information - **Main Repository**: [https://github.com/agentkit-seo/agentkit-seo](https://github.com/agentkit-seo/agentkit-seo) - **Documentation**: [https://agentkit-seo.github.io/](https://agentkit-seo.github.io/) - **Modules**: Includes specialized logic for GitHub, LinkedIn, CV/ATS, Portfolios, and X/Twitter.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".