Agent skill

Works with the CLI alone. No gander.md account.

The Gander skill is a SKILL.md plus two helper scripts that your coding agent can load. It does not need a gander.md account. Its job is to teach the agent: when you save a plan as markdown, offer to preview or watch it. When the agent creates a project directory, or first writes markdown into one, ask once whether to track that folder.

Without the skill, you run gander yourself. With the skill, the agent can save ./plans/YYYY-MM-DD-slug.md and ask whether to gander it. For a folder of plans, it asks once to run gander watch <dir> instead of prompting on every new file.

gander skill

gander skill install is the same command. The recommended one-liner already runs this. Run it yourself after Homebrew or a source build, because those paths do not.

When the agent shares or watches a file, it defaults to --silent unless you asked to open or preview. The CLI still creates a normal share and prints the URL; the agent reports that URL in chat instead of opening a tab. --silent is the CLI flag, not hidden visibility. Directory-adopted files never open a browser, with or without --silent.

gander share plan.md --silent
gander watch plan.md --silent
gander watch plans/

What it installs

The command downloads gandermd/gander-skill into ~/.gander/skill and symlinks that directory into the skill roots agents already search:

You do not copy files per agent. One install covers the dests above. Many other agents also read ~/.agents/skills/ or ~/.claude/skills/. If yours does not, symlink ~/.gander/skill into that agent's skills directory. Step-by-step per agent: Use with your agent. Marketing pages for the featured agents live on Use with your agent.

Clone the skill repo only if you want to edit SKILL.md or the scripts and have the symlinks point at your checkout.

Bundled scripts

After install, the scripts live under ~/.gander/skill (and the dest symlinks). Agents call them. You can too.

Save an agent-produced plan as markdown, then offer to gander it:

cat plan.txt | scripts/save-plan.sh "Add token rotation"
scripts/save-plan.sh "Refactor share rendering" plan.md
PLAN_SOURCE=opencode scripts/save-plan.sh "Plan title here"

The file lands at ./plans/YYYY-MM-DD-<slug>.md with a title heading and a short metadata block. Override the directory with PLAN_DIR=/some/path.

Track this folder

When the agent creates a project directory, or is about to write the first .md into one that is not already dir-watched, it asks once:

I created <dir> and will be adding markdown there. Want Gander to auto-share new .md files under it (including subfolders) as they appear?

• Yes runs gander watch <abs-dir> if you are signed up, otherwise gander --watch <abs-dir>. The runner persists, so later sessions do not ask again.
• No is remembered for this session. The agent still ganders individual files if you ask. It does not prompt per new file.
• Already watching that path: no ask. New files in that tree just onboard.

The agent never runs gander watch <dir> unless you said yes. It does not ask on every subsequent .md. That per-file y / s / N loop was scripts/watch-markdown.sh; directory watch replaces it.

The script is still in the skill checkout if you want a one-off prompt. The product path is the CLI:

gander watch ~/projects/notes
gander --watch ~/projects/notes

Skill vs MCP

These are different jobs. Install both for the full loop.

See MCP. gander --upgrade refreshes ~/.gander/skill when the skill is already installed, and re-links the dests.