decide how low context usage agents determine which skills to ignore (via agent compose) #70

Closed
opened 2026-07-24 11:12:39 +00:00 by coilysiren · 4 comments
Owner

(so: every open source one except the ones that use gpt 120... which I think is just hermes?)

(so: every open source one except the ones that use gpt 120... which I think is just hermes?)
Author
Owner
for configuration: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/issues/716
Author
Owner

I don't think "all the composed skills" or "all the simple skills" is a good call here. probably case by case. which means the skills themselves get to decide if they are critical for low context agents. so like the core python skill is, but the high end architectural design skill isnt. and those are both composed.

I don't think "all the composed skills" or "all the simple skills" is a good call here. probably case by case. which means the skills themselves get to decide if they are critical for low context agents. so like the core python skill is, but the high end architectural design skill isnt. and those are both composed.
Member

AOS issue 717 landed the coarse gate for tooling-skill-authoring: only director and PM receive it through role composition. When this issue adds harness or model-class selection, refine that source to frontier-model seats while retaining the director and PM role boundary.

AOS issue 717 landed the coarse gate for `tooling-skill-authoring`: only director and PM receive it through role composition. When this issue adds harness or model-class selection, refine that source to frontier-model seats while retaining the director and PM role boundary.
Member

Implemented the core in agent-compose commit 8cdc874 and the source-owned policy in AOS commit 9f7ec90 (AOS #716).

End-to-end verification used a real low-context director bundle against the landed AOS provider:

  • bundle verification passed
  • coding-python remained selected and was materialized
  • tooling-skill-authoring was excluded because its frontmatter marks it optional for low-context model classes
  • the director role boundary remained intact

The policy defaults missing metadata to required, so pruning happens only after an explicit per-skill authoring decision.

Implemented the core in agent-compose commit `8cdc874` and the source-owned policy in AOS commit `9f7ec90` (AOS #716). End-to-end verification used a real low-context director bundle against the landed AOS provider: * bundle verification passed * `coding-python` remained selected and was materialized * `tooling-skill-authoring` was excluded because its frontmatter marks it optional for low-context model classes * the director role boundary remained intact The policy defaults missing metadata to required, so pruning happens only after an explicit per-skill authoring decision.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
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/agent-compose#70
No description provided.