AgentKit SEO

Workflow

Usage

Read the relevant module, prepare verified context, then improve one professional surface at a time.

Why it exists

Most AI agents can rewrite a CV, LinkedIn bio, GitHub README, or portfolio page. The problem is that they usually rewrite from whatever context happens to be in the chat. That produces generic personal-branding copy, missing facts, repeated questions, and platform advice that does not travel from one agent to another.

AgentKit SEO fixes the starting point by providing:

How it works

Raw user material
  (CVs, profile URLs, LinkedIn exports, screenshots, portfolio code, project notes)
        |
        v
Agent context file
  (one private, structured source of truth for verified career facts)
        |
        v
Platform skill
  (LinkedIn, GitHub, CV/ATS, web portfolio, X, or cross-platform audit rules)
        |
        v
Grounded output
  (audit, rewrite, prioritized action plan, patch proposal, or maintenance checklist)

The agent-context-file is the core concept. It is a private Markdown file that stores verified identity, target roles, education, experience, projects, metrics, links, constraints, and preferred tone.

This is not a prompt collection. It is an operating manual for agents working on professional identity: gather inputs, verify facts, route to the right platform rules, produce grounded output, and avoid inventing unsupported claims.

Quick Start

Start with the context file, then send one platform through the right skill.

Use agentkit-seo-agent-context-optimization to create my agent-context-file.
I can provide my CV, LinkedIn sections, GitHub URL, portfolio URL, project notes,
screenshots, or any other career material you need.

Then use a platform skill:

Use agentkit-seo-github to audit my GitHub profile for hiring visibility.
Use my personal context file at the path I provide.

Invocation by Provider

Provider behavior is not identical. Some agents can select installed skills from their metadata, some expose slash commands, and some require you to mention the skill or add provider-specific rules. The shared skill names are the stable contract, but the way you invoke them depends on the provider.

Codex

Mention the installed skill when the environment supports it:

$agentkit-seo-agent-context-optimization
$agentkit-seo-github

Claude Code

Ask for the installed skill by name. Claude may auto-select from skill metadata, but explicit naming is safer:

Use the agentkit-seo-linkedin skill to audit my LinkedIn profile.

Gemini CLI

Use the namespaced commands shipped with the Gemini extension bundle:

/agentkit-seo:context
/agentkit-seo:github
/agentkit-seo:linkedin

OpenCode

Use native skill loading or the flat command wrappers:

/agentkit-seo-context
/agentkit-seo-github
/agentkit-seo-linkedin

Other Agents

Install or copy the portable SKILL.md folders, then follow that agent's rule or skill system. If the agent cannot load skills automatically, paste or reference the relevant skill instructions manually.

Verify before publishing

Review unsupported claims, stale links, missing evidence, and platform-specific constraints before applying public changes.