Future enhancement surfaced during PR #118 review.
Currently 00_playbook.md and 06_scitexification/SKILL.md declare four requires: companion skills — scitex-session, scitex-io, figrecipe, scitex-clew. A SAC agent that loads scitexification therefore pulls all four full SKILL.md trees into context. Measured aggregate: ~30K tokens (session 3.6K + io 11.3K + plt 2.1K + figrecipe 3.6K + clew 9.4K) — comfortably within the 256K window, so the simple full-load is the right default today.
A future tag-filtering mechanism could let downstream agents declare a narrower subset — e.g. "this capsule only does stages 1+2, give me just session + io" — using sub-tags like scitexification.io / scitexification.session already sketched in the umbrella SKILL.md. The narrower load would surface only the relevant subset of each companion skill (e.g. just scitex-io's save/load surface, not its mcp / scholar integration).
This is deferred, not blocking — the full ~30K load works for all current consumers (paper-scitex-clew, future scitexification users), and tag-filtering only becomes worth it when context budgets tighten or when a consumer is doing a strict stages-1+2 subset.
Action items if/when picked up:
Suggested labels: enhancement, skills, low-priority.
Future enhancement surfaced during PR #118 review.
Currently
00_playbook.mdand06_scitexification/SKILL.mddeclare fourrequires:companion skills —scitex-session,scitex-io,figrecipe,scitex-clew. A SAC agent that loadsscitexificationtherefore pulls all four full SKILL.md trees into context. Measured aggregate: ~30K tokens (session 3.6K + io 11.3K + plt 2.1K + figrecipe 3.6K + clew 9.4K) — comfortably within the 256K window, so the simple full-load is the right default today.A future tag-filtering mechanism could let downstream agents declare a narrower subset — e.g. "this capsule only does stages 1+2, give me just session + io" — using sub-tags like
scitexification.io/scitexification.sessionalready sketched in the umbrella SKILL.md. The narrower load would surface only the relevant subset of each companion skill (e.g. justscitex-io's save/load surface, not its mcp / scholar integration).This is deferred, not blocking — the full ~30K load works for all current consumers (paper-scitex-clew, future scitexification users), and tag-filtering only becomes worth it when context budgets tighten or when a consumer is doing a strict stages-1+2 subset.
Action items if/when picked up:
scitex-dev skillsCLI with atags-expand --filter <sub-tag>mode that resolvesscitexification.ioto just the relevantscitex-iochapters.00_playbook.md's "Required companion skills" section.spec.skills.requiredto honour sub-tags (no-op for SAC versions that don't yet support it).Suggested labels:
enhancement,skills,low-priority.