Write once · runs in every agent

One MCP. Every agent. Your skills, everywhere.

Author an AI workflow once — your team know-how, written down — and DeerDawn delivers it to every tool you connect. The same MCP that keeps your project context in sync carries your skills along with it.

See the MCP setup →
How it works

Write it down once. It rides the same sync.

A skill is a short markdown file describing how your team does something. Save it once and DeerDawn writes it into each tool's native location through the start_session → sync → files loop you already use for context.

1
Author the workflow

Write a SKILL.md — a step list, a runbook, a convention. Plain markdown, no per-tool formatting to learn.

2
Sync once

DeerDawn stores it alongside your project context. Nothing else to configure — it travels on the MCP you already connected.

3
It appears in every agent

Claude Code, Cursor, and Codex each pick it up in their own native location, ready to run.

Where each agent reads it
Claude Code
.claude/skills/<skill>/SKILL.md
Cursor
.cursor/rules/<skill>.mdc
Codex
AGENTS.md (indexed)
What a skill looks like

It's just markdown.

A name, a description, and the steps. DeerDawn handles the per-tool translation — Claude frontmatter for Claude Code, Cursor rule frontmatter for Cursor, an index entry for Codex.

SKILL.md
---
name: ship-pr
description: How this team opens a pull request, end to end.
---

# Ship a PR

1. Branch from `main` as `feat/<area>-<slug>`.
2. Run `npm run lint` and `npm test` — both must pass.
3. Open the PR with a one-line summary and the review checklist.
4. Tag a reviewer from the owning area.

Project context and user instructions win on any conflict.
Team know-how, made portable

The workflows your team already shares — now in every agent.

ship-pr

How this team opens a PR — branch naming, the checklist that must pass, and the review tags we use.

debug-prod

The runbook for a production incident: where the logs live, which dashboards to open, who to page.

write-migration

Our database migration conventions — reversible steps, the naming pattern, and the seed data to refresh after.

release-notes

Turn a set of merged PRs into release notes in our voice, grouped the way the changelog expects.

Author it once. Run it in every agent.

Skills ride the DeerDawn MCP you already connect for context. Set it up once and your team know-how follows you across tools and devices.

See pricing →