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:
- A private agent-context-file for verified career facts.
- Focused skills for CV/ATS, GitHub, LinkedIn, portfolio SEO, and X.
- One export/install CLI for Claude Code, Codex, Gemini CLI, Antigravity, OpenCode, and portable
SKILL.mdusage, plus a Claude Code plugin marketplace.
How it works
The workflow moves from scattered raw material to consistent public results in four stages:
- Raw material: Gather your existing CV, LinkedIn exports, GitHub profile, portfolio URLs, screenshots, and raw project notes.
- Agent context file: Load your agent with the agent-context-optimization skill and provide your raw material. The agent will distill this into one private, structured source of truth. This file stores your verified identity, education, experience, projects, metrics, links, constraints, and preferred tone, plus a separate goals and targeting section (ideal role, current focus, target locations) kept as stated intent rather than verified fact.
- Platform skills: Provide the resulting context file to an agent loaded with a focused platform skill (such as LinkedIn, GitHub, CV/ATS, or Portfolio).
- Grounded output: The agent produces an audit, rewrite, patch proposal, or action plan that is consistent across all surfaces and backed by the verified facts in your context file.
This is not a prompt collection. It is an operating manual for agents working on professional identity: verify facts first, then optimize the surface.
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 Antigravity
Reference the installed plugin skill by name. The layout is based on the Gemini-compatible bundle:
Use the installed agentkit-seo-github plugin skill to audit my GitHub profile. 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.