How do I install the Integration/repo Bridge skill?

Run npx skillmds@latest add frankxai/integration-repo-bridge in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Integration/repo Bridge safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Integration/repo Bridge?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Integration/repo Bridge free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Integration/repo Bridge?

frankxai (@frankxai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Integration/repo Bridge by frankxai

Name: Integration/repo Bridge
Author: frankxai

Integration/repo Bridge

Use when operations span multiple FrankX ecosystem repositories — bridges Starlight understanding, references, and coordination across ACOS, Arcanea, AI-Ops, and other connected repos. Default skill for Starlight Orchestrator and Starlight Prime.

frankxai Updated Sep 17, 2026

File contents

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?

---name: integration-repo-bridgedescription: Use when operations span multiple FrankX ecosystem repositories — bridges Starlight understanding, references, and coordination across ACOS, Arcanea, AI-Ops, and other connected repos. Default skill for Starlight Orchestrator and Starlight Prime.---# 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 DoesBridges 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 Loading1. Identify which repos are relevant to the current task2. 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.md3. Extract relevant information for the task4. Merge with Starlight's own context5. Present unified cross-repo awareness### Procedure 2: Cross-Repo Pattern Transfer1. Identify a pattern from one repo that applies to another2. Document the pattern's origin and proven success3. Adapt the pattern to the target repo's conventions4. Package as a Transmission for the target channel5. Store the cross-pollination event in Wisdom Vault### Procedure 3: Ecosystem State Assessment1. Query all repo contexts for current state2. Identify cross-repo dependencies3. Find integration gaps or misalignments4. Assess ecosystem health5. Recommend cross-repo improvements6. 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?

Frequently asked questions