agentleFS
Sign inStart free
frankxaifrankxai/Starlight-Intelligence-System/skills/integration/repo-bridge/SKILL.md

integration/repo-bridge

Skill10 starsChanged 2 months agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Default for: Starlight Orchestrator, Starlight Prime

    line 15
  2. Distinctive:

    Document the pattern's origin and proven success

    line 37
  3. Distinctive:

    Context: All repo context files

    line 54
  4. Distinctive:

    Transmissions: All channels (cross-repo communication)

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Identify which repos are relevant to the current task
  2. 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
  3. Extract relevant information for the task
  4. Merge with Starlight's own context
  5. Present unified cross-repo awareness

Procedure 2: Cross-Repo Pattern Transfer

  1. Identify a pattern from one repo that applies to another
  2. Document the pattern's origin and proven success
  3. Adapt the pattern to the target repo's conventions
  4. Package as a Transmission for the target channel
  5. Store the cross-pollination event in Wisdom Vault

Procedure 3: Ecosystem State Assessment

  1. Query all repo contexts for current state
  2. Identify cross-repo dependencies
  3. Find integration gaps or misalignments
  4. Assess ecosystem health
  5. Recommend cross-repo improvements
  6. 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?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free