AGENTS.md · git:20260521.49efe94 · 2026-05-21 · sha256 6436f78ec943dfec

AGENTS.md git:20260521.49efe94A

Immutable. This exact content is served forever at /api/v1/blob/6436f78ec943dfec.

# Skills Repository

`usetemi/skills` publishes Temi agent skills for coding agents and tools that
support the Agent Skills spec. Keep this file focused on instructions agents need
while changing the repo; keep public install, catalog, and distribution copy in
`README.md`.

## Orientation

- Each skill is self-contained under `skills/<name>/`. `SKILL.md` is the required
  entry point; deeper references should live inside the skill and be loaded only
  when the task calls for them.
- `README.md` is the canonical public catalog and install guide. Update it when a
  skill is added, removed, renamed, or its public description changes.
- Plugin and marketplace metadata lives under `.claude-plugin/`,
  `.codex-plugin/`, and `.agents/plugins/`. Touch those files only for registration
  or metadata changes.
- `template/` renders shared Python modules for the google-* CLI skills. Read
  `template/AGENTS.md` before editing the Copier template or any file generated
  from it.

## Skill Changes

- When adding a new skill, create `skills/<name>/SKILL.md` and keep the skill
  directory self-contained.
- Register new skills in `.claude-plugin/marketplace.json` and add a row to the
  `README.md` skill table.
- Codex discovers skills from `./skills/` via `.codex-plugin/plugin.json`, so new
  skills do not need per-skill Codex registration unless root plugin metadata
  changes.
- Do not document capabilities that are not implemented in the skill.

## Copier-Rendered Google Skills

The google-* Python CLI skills share modules rendered from `template/`. If you
change a template or a rendered shared module, re-render each affected consuming
skill from that skill's directory:

```bash
copier copy --data-file .copier-answers.yml --defaults --trust --overwrite ../../template .
```

Commit the template change and regenerated outputs together. The
`copier-drift.yml` workflow runs the same `copier copy --overwrite` flow and fails
if rendered files drift.

## Validation

- For Python CLI skills, run:
  ```bash
  uv run --project skills/<skill> ruff check .
  uv run --project skills/<skill> ty check
  ```
- After editing `template/**`, run the Copier re-render command for each affected
  skill with a `.copier-answers.yml` file and confirm the diff contains only
  intended changes.
- For docs-only edits, re-read the changed guidance and check for duplicated
  README content, stale file indexes, or command drift.
- Before finishing, run `git diff --check`.