Agent instructions

AGENTS.md is the durable brief the runtime gives your agent. Write it like guidance for a capable teammate: clear about the outcome, explicit about boundaries, and quiet about details that belong elsewhere.

A useful shape#

# Release notes assistant

Summarize shipped changes for product teams.

## Workflow

1. Read the supplied change list.
2. Group changes by customer outcome.
3. Flag claims that lack evidence.

## Boundaries

- Never invent release dates.
- Never include credentials or private issue links.

State the agent's role, normal workflow, response style, and non-negotiable safety rules. Prefer concrete verbs over personality adjectives.

Route detailed work to skills#

Keep recurring procedures in skills/<name>/SKILL.md. In AGENTS.md, tell the agent when to use each skill. This keeps the core prompt readable while making specialized guidance discoverable.

Write for change#

Avoid duplicating configuration schemas, API responses, or volatile operational facts in prose. Link to a skill or supporting file when the detail needs independent maintenance.

Test instructions with realistic requests, ambiguous requests, and requests the agent should refuse or clarify.