Agent skills
Skills teach your agent how to search for engineers with the Vamo API: set up access, turn a role into a search, run it, and read the results. They are plain markdown, so they work in any agent that can read a file.
Install
Choose where your agent runs. The copy buttons below follow your choice.
Run this inside Claude Code.
/plugin install vamo --marketplace vamo-ai/vamo-skills Each skill is then a command, such as /vamo:vamo-setup.
Open Customize, then Plugins. Choose Add, then Add marketplace. Enter this name and install vamo.
vamo-ai/vamo-skills Updates sync from the repository. In a chat, type / and pick a skill.
Codex: run this in your terminal.
git clone --depth 1 https://github.com/vamo-ai/vamo-skills /tmp/vamo-skills && mkdir -p ~/.agents/skills && cp -R /tmp/vamo-skills/skills/. ~/.agents/skills/ Codex reads skills from that folder in the terminal, the editor and the ChatGPT
desktop app. Run one with /skills, or type $ and its name.
ChatGPT: where Skills is on for your workspace, upload the skill zips from the latest release, then type @ and pick a skill.
Paste this into your agent.
Fetch https://vamotalent.ai/skills/install.md and follow the instructions It works out how it loads skills, installs them, and checks your API access.
Skills
- Get started Start here
Guided setup in the AI tool you already use: your agent works out the tool and what it allows, connects Vamo the way that keeps working (the MCP server with sign-in by default), adds the skills, and runs a first search as a short tutorial. Also covers setup codes and direct API access for your own code.
- “Set up Vamo for me.”
- “Connect Vamo to Claude and show me how it works.”
/vamo:vamo-setupv1.1.0 Markdown -
When Vamo stops working, your agent finds out why: which route it is on, three checks in order, what each error means, and what to send Vamo if it cannot fix it.
- “Check my Vamo connection and tell me what is wrong.”
- “Vamo worked yesterday and fails today. Find out why.”
/vamo:vamo-troubleshootingv1.2.0 Markdown -
Find engineers by what they built, from a technology, a company, a repository, a place, one person or a whole job description. Includes turning intake notes into a search spec, covering a broad topic without missing the famous items, and query phrasings for 50 domains.
- “Find 30 developers building real-time voice agents.”
- “Here is the role. Find 50 people who fit.”
/vamo:vamo-searchv3.2.0 Markdown -
Learn more about people you already have, wherever they came from: candidates in an applicant tracking system such as Ashby, LinkedIn profiles, applicants, a spreadsheet. A strength read, location, LinkedIn, current role, contact details, screening for real engineering work, a one-page summary and a full research report.
- “I interview this candidate tomorrow. What have they built?”
- “Screen this week's applicants in Ashby for real engineering work.”
/vamo:vamo-enrichv1.3.0 Markdown -
Personalized technical outreach to engineers. Starts with describing the role well in a few lines, then links one thing each person built to the work in the role: the right repository, a 50 to 80 word first message, subject lines, follow-ups, answering a reply, and a check before anything is handed over. A person approves every message.
- “Help me pitch this role in a few lines.”
- “Write a first email to this engineer that shows we read their code.”
/vamo:vamo-outreachv1.0.0 Markdown -
Vamo together with the other tools your agent can reach, with links to each one's official setup: Slack, Ashby, Greenhouse, Lever, Gmail, Outlook, Google Sheets and Calendar, HubSpot. The common hand-offs, example systems to build, where a scheduled agent can run, and the rules for runs that repeat.
- “Every Monday, post new matches for this role to our Slack channel.”
- “Write what you found back to these candidates in Ashby.”
/vamo:vamo-workflowsv1.2.0 Markdown
Last updated 2026-10-14. The source is public at GitHub, the current versions are listed at /skills/index.json, and your agent gets its access from the setup prompt on Home in your dashboard.