Repo Bridge
"Across repositories, intelligence flows."
When This Skill Activates
- •Operations involving multiple FrankX repositories
- •Keywords: "repo", "repository", "cross-repo", "ACOS", "Arcanea", "AI-Ops"
- •Default for: Starlight Orchestrator, Starlight Prime
What This Skill Does
Bridges operations across the FrankX ecosystem repositories. Enables Starlight to understand, reference, and coordinate work across ACOS, Arcanea, AI-Ops, and any other connected repos.
Procedures
Procedure 1: Cross-Repo Context Loading
- •Identify which repos are relevant to the current task
- •Load the appropriate repo context from context/repo-contexts/:
- •ACOS context → acos-context.md
- •Arcanea context → arcanea-context.md
- •AI-Ops context → ai-ops-context.md
- •Extract relevant information for the task
- •Merge with Starlight's own context
- •Present unified cross-repo awareness
Procedure 2: Cross-Repo Pattern Transfer
- •Identify a pattern from one repo that applies to another
- •Document the pattern's origin and proven success
- •Adapt the pattern to the target repo's conventions
- •Package as a Transmission for the target channel
- •Store the cross-pollination event in Wisdom Vault
Procedure 3: Ecosystem State Assessment
- •Query all repo contexts for current state
- •Identify cross-repo dependencies
- •Find integration gaps or misalignments
- •Assess ecosystem health
- •Recommend cross-repo improvements
- •Store assessment in Operational Vault
Integration Points
- •Vault: Operational Vault (ecosystem state), Wisdom Vault (cross-repo patterns)
- •Context: All repo context files
- •Transmissions: All channels (cross-repo communication)
- •Agents: Orchestrator (coordination), Prime (ecosystem awareness)
Quality Criteria
- •Is the correct repo context loaded?
- •Are cross-repo patterns properly adapted (not just copied)?
- •Is ecosystem state accurate and current?
- •Are recommendations actionable?