payloadcms — Claude Code skill: what it does, how to install
Walks the agent through Payload CMS work in a repo: bootstrapping an app, changing collection schemas, debugging the admin panel or API, preparing migrations.
no license 253 installs ★ 61 updated 2026-10-24
npx skills add akillness/jeo-skills --skill payloadcms -a claude-codeWhat payloadcms does
This skill covers Payload CMS, the Next.js-native headless CMS, inside an existing repository. It starts by asking you to pick one mode. Bootstrap handles a fresh install or a first integration. Modeling is for collection and global schemas. Runtime debug is for a failing admin page or endpoint. Release prep comes before a production rollout.
Preflight comes first: the Node toolchain and package manager, the location of payload.config.* and the model files, how DATABASE_URI plus storage and auth keys are supplied, and the migration history before any schema edit. It can call Bash, Read, Write, Edit, Glob, Grep and WebFetch. Schema work is meant to be one bounded change per pass, with the blast radius written down for collections, API output, admin forms and import jobs.
For work outside Payload's runtime the skill steps aside: physical database tuning goes to database-schema-design, auth architecture to authentication-setup. Pushing it there wastes a pass. A green admin check also proves little when DATABASE_URI is not wired up.
What it helps with
- bootstrap a Payload app and confirm the admin panel plus one collection endpoint respond
- add a collection with explicit access rules without breaking existing API output
- trace a failing admin route back to a bad field, access rule or env binding
- write migration order and rollback notes before merging a schema change
- audit how
DATABASE_URIand adapter keys reach the runtime
Example prompts for the agent
- Add a
postscollection to our Payload config and list what the migration touches - The Payload admin route broke after yesterday's schema change, find the root cause
- Bootstrap a Payload app in this repo and verify the admin panel and one collection endpoint
How to install payloadcms
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill payloadcms -a claude-code2Manually: put the files in place
~/.claude/skills/payloadcms/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/payloadcms/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill payloadcms -a codex2Manually: put the files in place
.agents/skills/payloadcms/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill payloadcms -a cursor2Manually: put the files in place
.cursor/skills/payloadcms/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install akillness/jeo-skills .agent-skills/payloadcms/SKILL.md2Manually: put the files in place
.github/skills/payloadcms/SKILL.md1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill payloadcms -a gemini-cli2Platform CLI
gemini skills install https://github.com/akillness/jeo-skills --path .agent-skills/payloadcmsManually: put the files in place
.devin/skills/payloadcms/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill payloadcms -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about payloadcms
How do I install payloadcms in Claude Code?
Run npx skills add akillness/jeo-skills --skill payloadcms -a claude-code. The skill file then sits at ~/.claude/skills/payloadcms/SKILL.md.
What does the payloadcms skill do?
It runs Payload CMS work in a repo through four modes: bootstrap, modeling, runtime debug and release prep. Each mode pairs environment checks with a validation list before merge.
What should I check before editing a collection schema?
The Node toolchain and package manager, where payload.config.* lives, how DATABASE_URI and the keys are supplied, and the migration history. Skipping that turns a schema edit into guesswork.