coilyco-flight-deck/infrastructure

Watch

Make infrastructure a canonical Agent Compose skill provider #702

New issue

Closed

opened 2026-07-31 08:53:22 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-31 08:53:22 +00:00

Owner

Outcome

Expose infrastructure as one canonical Agent Skills provider so role-scoped composition can discover and project every repository-owned operator skill.

Coordinates with:

Current state

Infrastructure has an established operator skill layer under skills/, while Agent Compose provider inference and the deploy precedent use .agents/skills/. The repository also already carries generated repo-pointer skills under .agents/skills/. The split prevents the operator catalogue from entering a normal provider bundle as one tree.

Work

Move the canonical operator skill directories from skills/ into .agents/skills/.
Preserve each skill reference, asset, and script relationship while updating repository links.
Merge with the existing repo-pointer surface without copying or renaming generated pointer skills.
Update README, AGENTS, docs/FEATURES.md, and affected runbook links to name the canonical path.
Remove duplicate tracked skill bodies after consumers have moved. Do not maintain two authoritative copies.
Keep one skill per operator domain family rather than one skill per script.
Validate names, frontmatter, description caps, references, and dead links through the owning catalog hooks.
Prove Agent Compose provider inference can load the repository root and enumerate the complete valid skill tree.
Preserve public-safety and command-boundary rules in every moved skill.

Acceptance

Every infrastructure-owned operator skill has exactly one canonical directory under .agents/skills/.
No live link or documentation still points at the retired skills/<name>/SKILL.md paths.
Generated repo-pointer skills remain byte-identical to their owning projection contract.
Agent Compose can consume the infrastructure repository as a provider without a special path exception.
The provider inventory derives from the filesystem and is not duplicated in a test list.
Existing operator skill semantics and references remain intact.
docs/FEATURES.md describes the canonical operator skill layer.
pre-commit run --all-files passes from clean repository state.

## Outcome Expose infrastructure as one canonical Agent Skills provider so role-scoped composition can discover and project every repository-owned operator skill. Coordinates with: * https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/168 * https://forgejo.coilysiren.me/coilyco-bridge/agentic-os-kai/issues/794 ## Current state Infrastructure has an established operator skill layer under `skills/`, while Agent Compose provider inference and the deploy precedent use `.agents/skills/`. The repository also already carries generated repo-pointer skills under `.agents/skills/`. The split prevents the operator catalogue from entering a normal provider bundle as one tree. ## Work * Move the canonical operator skill directories from `skills/` into `.agents/skills/`. * Preserve each skill reference, asset, and script relationship while updating repository links. * Merge with the existing repo-pointer surface without copying or renaming generated pointer skills. * Update README, AGENTS, docs/FEATURES.md, and affected runbook links to name the canonical path. * Remove duplicate tracked skill bodies after consumers have moved. Do not maintain two authoritative copies. * Keep one skill per operator domain family rather than one skill per script. * Validate names, frontmatter, description caps, references, and dead links through the owning catalog hooks. * Prove Agent Compose provider inference can load the repository root and enumerate the complete valid skill tree. * Preserve public-safety and command-boundary rules in every moved skill. ## Acceptance * Every infrastructure-owned operator skill has exactly one canonical directory under `.agents/skills/`. * No live link or documentation still points at the retired `skills/<name>/SKILL.md` paths. * Generated repo-pointer skills remain byte-identical to their owning projection contract. * Agent Compose can consume the infrastructure repository as a provider without a special path exception. * The provider inventory derives from the filesystem and is not duplicated in a test list. * Existing operator skill semantics and references remain intact. * docs/FEATURES.md describes the canonical operator skill layer. * pre-commit run --all-files passes from clean repository state.

coilyco-ops referenced this issue

2026-07-31 08:53:40 +00:00

Turn disk-pressure and Forgejo-storage runbooks into an Ops skill family #703

coilyco-ops referenced this issue

2026-07-31 08:54:01 +00:00

Promote k3s triage trees and trap docs into Ops investigation skills #704

coilyco-ops referenced this issue from coilyco-flight-deck/agent-compose

2026-07-31 08:54:16 +00:00

Add role-scoped skill providers to native and staged bundles #168

coilyco-ops commented

2026-07-31 08:54:22 +00:00

Author

Owner

The first operator-content promotion slices are:

#703
#704

The first operator-content promotion slices are: * https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/issues/703 * https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/issues/704

coilyco-ops referenced this issue from a commit

2026-07-31 09:24:43 +00:00

feat: make infrastructure a canonical skill provider

coilyco-ops closed this issue

2026-07-31 09:24:44 +00:00

No milestone

No project

No assignees

1 participant

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/infrastructure#702

No description provided.

Rows
Columns