gem0-agent
Work in Gem0 (gem0.dev headless CMS) as the signed-in user through an agent token (gem_pat_...) - list and create projects, tables (schemes), rows, project API keys. Use whenever GEM0_TOKEN is set, th
SKILL.mdusers/kyandesutter/claude/skills/gem0-agent/SKILL.md
GitHubGem0 agent API
This skill is a stub. The contract lives on the server and changes with each deploy.
- Check
GEM0_TOKEN(gem_pat_...) is set; if not, ask the user. They mint one in the Gem admin under Settings, Agent tokens.GEM0_URLdefaults tohttps://apist.gem0.dev. - Fetch the current reference and follow it over anything you remember:
curl -fsS "${GEM0_URL:-https://apist.gem0.dev}/en/v3/agent/skill" - Find out what this token may do before doing anything:
curl -fsS "${GEM0_URL:-https://apist.gem0.dev}/en/v3/agent/me" -H "Authorization: Bearer $GEM0_TOKEN"Stay insidemodulesandprojectsfrom that response.
Rules that hold whatever the live doc says:
- Never echo, log, commit or paste the token anywhere. Reference it as
$GEM0_TOKEN. - Any
remove, disabling a user, revoking a key or publishing needs the user's explicit yes in this session. - On
success:false, show thedatafield verbatim; Gem0 messages name the exact cause. - A 403 means the token is read-only or the route is human-only (login, minting tokens). Tell the user; do not look for a way around it.