flypod install skill

Write the flypod Agent Skill into your repo so coding agents (Claude Code, Codex, Cursor, Gemini CLI, Copilot) know how to deploy with flypod.

flypod install skill teaches the coding agents working in a repo how to deploy with flypod. It writes an Agent Skill — a SKILL.md plus its reference docs — into the two directories every major agent reads, so the next time you ask an agent to "deploy this," it knows to run flypod.

flypod install skill

It writes the same skill twice, because agents look in two places:

Directory	Read by
`.claude/skills/flypod/`	Claude Code
`.agents/skills/flypod/`	Codex, Cursor, Gemini CLI, GitHub Copilot

Run it from your project root. The command is non-interactive by default (safe for agents and CI); when a human runs it in a terminal with no target flags, an arrow-key picker appears to choose targets.

What gets written

The skill uses progressive disclosure: a short entry file that the agent always loads, and reference documents it opens only when the task calls for them. That keeps the always-on cost small while making the full capability surface reachable.

.claude/skills/flypod/
├── SKILL.md                              the deploy loop — always loaded
└── reference/
    ├── updates-and-versions.md           update, versions, rollback, --site
    ├── publishing-markdown.md            deploying .md as a rendered site
    ├── comments.md                       review loop on a deployed preview
    └── troubleshooting.md                exit codes, warnings, CI, env vars

.agents/skills/flypod/ gets a byte-identical copy.

Synopsis

flypod install skill [targets] [flags]

Targets

Both targets are written by default. Pass a flag to write just one.

Target	Flag	Directory written
Claude Code	`--claude`	`.claude/skills/flypod/`
Agent Skills (shared)	`--agents`	`.agents/skills/flypod/`

--cursor, --codex, --copilot, --gemini, --windsurf, --cline, and --roo still work as aliases for --agents. Those agents used to need their own file format; they all read .agents/skills/ now, so one directory covers them.

Flags

Flag	Description
`--all`	Write every target without prompting, even in a terminal.
`--global`	Write to your home directory (`~/.claude/skills/`, `~/.agents/skills/`) instead of the project.
`--list`	Print where each target would be written; write nothing.
`--dry-run`	List every file that would be written, then exit without touching disk. (`--print` is an alias.)

Examples

Install into both locations:

flypod install skill

See where the files would go without writing anything:

flypod install skill --list

Write only the Claude Code skill:

flypod install skill --claude

Install once for every project on this machine:

flypod install skill --global

Idempotency

The command is safe to re-run. Every file inside a skill directory is flypod-owned and rewritten wholesale, and a file that already matches is reported as unchanged. Nothing outside those two directories is touched.

Alternative: the `skills` CLI

The flypod skill is also published as a standalone repo, so you can install it with skills — the open-source CLI that manages agent skills across 76+ coding agents. Reach for this when you already use skills to manage the rest of your toolkit, or when you want flypod's skill without installing the flypod CLI first.

npx skills add flypod-dev/flypod-skill

Target specific agents with -a, or install once for every project on the machine with -g:

npx skills add flypod-dev/flypod-skill -a claude-code -a codex -a cursor
npx skills add flypod-dev/flypod-skill -g

It installs the same SKILL.md and reference/ files that flypod install skill writes — the packaged repo is generated from the same source, so the two paths can't drift. Afterwards, npx skills update picks up new versions and npx skills ls shows what's installed.

The layout differs, though the content doesn't: skills writes the real files to .agents/skills/flypod/ and makes .claude/skills/flypod a symlink to them, where flypod install skill writes two independent copies. Claude Code follows the symlink, so both work — but expect a symlink rather than a second directory in your diff.

The two are interchangeable, not cumulative — pick one. flypod install skill knows exactly which two directories agents read and needs no arguments; npx skills add covers a much longer tail of agents and manages updates alongside your other skills.

Upgrading from the pre-skills layout

Earlier versions wrote a fenced flypod block into AGENTS.md and native rule files for each agent (.cursor/rules/flypod.mdc, .clinerules/flypod.md, GEMINI.md, and others). Those agents have since converged on .agents/skills/, so the skill directory replaces all of them.

After installing, the command lists any of those older files it finds. It does not delete them — AGENTS.md in particular is your file, and may contain plenty that has nothing to do with flypod. Remove the flypod parts yourself when you are ready; leaving them in place means your agents read two sets of flypod instructions, and the older set is out of date.

On this page