decide how low context usage agents determine which skills to ignore (via agent compose) #70
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-compose#70
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
(so: every open source one except the ones that use gpt 120... which I think is just hermes?)
for configuration: coilyco-flight-deck/agentic-os#716
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.
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.Implemented the core in agent-compose commit
8cdc874and the source-owned policy in AOS commit9f7ec90(AOS #716).End-to-end verification used a real low-context director bundle against the landed AOS provider:
coding-pythonremained selected and was materializedtooling-skill-authoringwas excluded because its frontmatter marks it optional for low-context model classesThe policy defaults missing metadata to required, so pruning happens only after an explicit per-skill authoring decision.