Skip to content

docs(glossary): customization vocabulary for agents and skills #6383

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ascerra merged 2 commits into from
Sep 10, 2026
+112 −10
Merged

docs(glossary): customization vocabulary for agents and skills #6383

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5416809
docs(glossary): add customization vocabulary for agents and skills
ascerra Sep 9, 2026
a11bc35
docs(glossary): address review-bot findings on customization vocabulary
ascerra Sep 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/agents/topics/default-vs-custom.md
View file
Open in desktop
Comment thread
ascerra marked this conversation as resolved.
Comment thread
ascerra marked this conversation as resolved.
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Fullsend ships a set of default agents in
[fullsend-ai/agents](https://github.com/fullsend-ai/agents). Each can be
configured and extended.
At some point, enough modification turns a configured default into something
different. This document defines three tiers:
different. This document defines three categories:

1. **Configured default agent** — uses only documented extension points
(env vars, skills, `AGENTS.md`, plugins, host files, sandbox image layers).
Expand Down Expand Up @@ -53,7 +53,7 @@ configured review agent, not a derived one.
The `base` field in a harness YAML (see [Architecture](../../architecture.md#agent-harness)
for details on harness composition) is the first thing to check. If a
harness's `base` chain — through one or more levels of inheritance — traces
back to a default agent harness in `fullsend-ai/fullsend`,
back to a default agent harness in `fullsend-ai/agents`,
the harness *started from* a default agent. What you override on top of that
base determines whether the result is still a configured default or has crossed
into derived territory.
Expand All @@ -68,7 +68,7 @@ agent is custom by definition — regardless of how similar it looks.
| Set a documented configuration variable (e.g., `REVIEW_FINDING_SEVERITY_THRESHOLD`) | Configured default | Documented extension point. The agent was designed for this. |
| Add environment variables via `env:` | Configured default | Env vars augment behavior without changing identity. |
| Add skills via `skills:` | Configured default | Skills extend knowledge. The agent's core behavior is unchanged. |
| Add repo-level skills in `.agents/skills/` | Configured default | Repo skills are discovered automatically; no harness change needed. |
| Add repo-level skills in `.agents/skills/` | Configured default | Discovered under Claude Code and Codex; a basename matching a harness-listed skill is shadowed (no fail-fast; Claude Code emits a warning), and `runtime: pi` does not read `.agents/skills` (see [Repo Skill](../../glossary.md#repo-skill)). |
| Add project instructions via `AGENTS.md` | Configured default | All agents read `AGENTS.md`. This is the standard customization path. |
| Override a built-in skill via config-driven registration | Configured default | Documented extension point ([Configuring with Skills](../../guides/user/customizing-with-skills.md#overriding-built-in-skills)). |
| Replace the sandbox image with one based on the default image | Configured default | The agent's behavior is unchanged; the environment is augmented. |
Expand Down
Loading
Loading