Move ward ambient content into skills #1276

Closed
opened 2026-07-14 10:59:58 +00:00 by coilysiren · 1 comment
Owner

And make it so that ward bootstrap vendors or otherwise generates those skills on init. DO NOT implement this via mounting the ward repo and its skills into everyone's substrate. You can, probably should, define them as 1st class skills in the ward repo. But a literal substrate dir mount is not how those skills should make their way to users. Their native ~/.agents/ style homedir is where it should go.

As far as what qualifies, here's some examples:

  • "you are a warded agent" - AGENTS.md AND skill - there are some basic facts that are reasonable to mention twice
  • "you are a readonly director surface" - skill
  • "work on issue # 1234" - startup prompt (where it currently lives)
  • everything else: case by case. itemize them in this issue first if you have to
And make it so that ward bootstrap vendors or otherwise generates those skills on init. DO NOT implement this via mounting the ward repo and its skills into everyone's substrate. You can, probably should, define them as 1st class skills in the ward repo. But a literal substrate dir mount is not how those skills should make their way to users. Their native `~/.agents/` style homedir is where it should go. As far as what qualifies, here's some examples: - "you are a warded agent" - AGENTS.md AND skill - there are some basic facts that are reasonable to mention twice - "you are a readonly director surface" - skill - "work on issue # 1234" - startup prompt (where it currently lives) - everything else: case by case. itemize them in this issue first if you have to
Owner

Closing as uncommitted bootstrap expansion. Ward v1 will keep its supported context and role contracts explicit rather than add automatic ambient-skill vendoring.

Closing as uncommitted bootstrap expansion. Ward v1 will keep its supported context and role contracts explicit rather than add automatic ambient-skill vendoring.
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
2 participants
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/ward#1276
No description provided.