agentleFS
Sign inStart free
frankxaifrankxai/Starlight-Intelligence-System/skills/integration/ecosystem-sync/SKILL.md

integration/ecosystem-sync

Skill10 starsChanged 2 months agoMITView on GitHub

Use when synchronizing intelligence, state, or knowledge across the FrankX ecosystem — ensures consistency and coherence across ACOS, Arcanea, AI-Ops, and Starlight. 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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:

    Read current state from all repo contexts

    line 25
  3. Distinctive:

    Update non-authoritative copies to match

    line 28
  4. Distinctive:

    Check each repo's implementation of the pattern

    line 35
  5. Distinctive:

    Create update recommendations for each repo

    line 37
  6. Distinctive:

    Update cross-references in vault indices

    line 48
  7. Distinctive:

    Context: All repo contexts (read and update)

    line 53
  8. Distinctive:

    Transmissions: All channels (sync communication)

    line 54

≈ “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

Ecosystem Sync

"When all systems are in sync, the whole becomes unstoppable."

When This Skill Activates

  • Synchronizing state, patterns, or knowledge across the ecosystem
  • Keywords: "sync", "synchronize", "align", "ecosystem", "all systems"
  • Default for: Starlight Orchestrator, Starlight Prime

What This Skill Does

Synchronizes intelligence, state, and knowledge across all FrankX ecosystem repositories. Ensures consistency and coherence across ACOS, Arcanea, AI-Ops, and Starlight.

Procedures

Procedure 1: State Synchronization

  1. Read current state from all repo contexts
  2. Identify state discrepancies or drift
  3. Determine the authoritative source for each piece of state
  4. Update non-authoritative copies to match
  5. Log sync operations in Operational Vault
  6. Send sync confirmation via Broadcast Channel

Procedure 2: Pattern Propagation

  1. Identify patterns that should be consistent across repos
  2. Check each repo's implementation of the pattern
  3. Find repos that are behind or divergent
  4. Create update recommendations for each repo
  5. Package as Transmissions to respective channels
  6. Track propagation status

Procedure 3: Knowledge Federation

  1. Identify knowledge that exists in one repo but is relevant to others
  2. Extract and package the knowledge
  3. Adapt to each target repo's format and conventions
  4. Send via appropriate Transmission channels
  5. Store federation event in Wisdom Vault
  6. Update cross-references in vault indices

Integration Points

  • Vault: Operational Vault (sync state), Wisdom Vault (federated knowledge)
  • Context: All repo contexts (read and update)
  • Transmissions: All channels (sync communication)
  • Agents: Orchestrator (primary), Prime (authorization)

Quality Criteria

  • Is synchronization complete (no missed repos)?
  • Are authoritative sources correctly identified?
  • Are patterns properly adapted per repo conventions?
  • Is sync state tracked and auditable?

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