Skip to main content
Skills teach Indent specific workflows — repeatable procedures that are too narrow for AGENTS.md but too important to explain every time. Indent pulls in the right skill when a task matches.

​
Where they live

Commit skills under .agents/skills/ in your repository. Each skill gets its own directory with a SKILL.md and any supporting files it needs. 
.agents/
  skills/
    deploy/
      SKILL.md
      scripts/
        deploy.sh
    db-migration/
      SKILL.md
    incident-triage/
      SKILL.md
      references/
        runbook.md

​
What goes in SKILL.md

SKILL.md tells Indent when to use the skill and what steps to follow. Be specific — the more concrete the instructions, the more reliably Indent will execute the workflow.

​
Example: deploy

# Deploy

## When to use
When deploying a service to staging or production.

## Steps
1. Run `pnpm build` and confirm it succeeds
2. Run `pnpm test` — do not deploy if tests fail
3. For staging: push to the `staging` branch
4. For production: create a PR to the `release` branch
   - Title format: `release: <service> <version>`
   - Wait for CI to pass before merging
5. After merge, monitor Datadog dashboard "Service Health"
   for 10 minutes before confirming the deploy is stable

## Notes
- Never force-push to `release`
- If a deploy needs to be rolled back, revert the merge commit
  and push to `release` again

​
Example: db-migration

# Database Migration

## When to use
When a task requires changes to the database schema.

## Steps
1. Create the migration with `pnpm prisma migrate dev --name <description>`
2. Check that the generated SQL in `prisma/migrations/` looks correct
3. If the migration is destructive (dropping columns, changing types),
   add a two-phase approach:
   - First PR: make the column nullable or add the new column
   - Second PR: backfill data and remove the old column
4. Run `pnpm test:integration` to verify against a real database
5. Note in the PR description that this includes a migration

## Notes
- Migrations run automatically on deploy — they must be backward-compatible
  with the currently running code
- Never edit a migration that has already been applied to staging or production

​
Example: incident-triage

# Incident Triage

## When to use
When investigating a production incident or alert.

## Steps
1. Check the Datadog dashboard for the affected service
2. Pull recent error logs from Sentry for the relevant time window
3. Identify whether the issue correlates with a recent deploy
   — check the last 3 merged PRs on the `release` branch
4. If a deploy caused it, draft a revert PR
5. If not deploy-related, investigate the error stack trace
   and check for recent changes to the affected code paths
6. Write up findings as a comment in the incident thread

## References
- See `references/runbook.md` for service-specific escalation paths

​
Viewing your skills

You can see which skills are available to Indent from the bottom of the Settings > Integrations page. Select a repository from the dropdown to see the skills committed under .agents/skills/.

​
Skills vs AGENTS.md

AGENTS.md is always-on context — Indent reads it at the start of every session. Use it for things that apply broadly: setup commands, architecture, conventions. Skills are pulled in when relevant. Use them for specific procedures that only matter for certain types of tasks. This keeps your always-on context focused and avoids overwhelming Indent with instructions it doesn’t need for most work.