agentleFS
Sign inStart free
Arcanea-LabsArcanea-Labs/Starlight-Intelligence-System/skills/integration/transmission-protocol/SKILL.md

integration/transmission-protocol

Skill10 starsChanged 2 months agoMITView on GitHub

Use when sending or receiving cross-system communications — manages the Starlight Transmission system that lets intelligence flow between Starlight, ACOS, Arcanea, and AI-Ops. 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Check channel files for new entries since last read

    line 42
  3. Distinctive:

    Channels: All transmission channels

    line 60

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

Transmission Protocol

"Intelligence that doesn't flow is intelligence that dies."

When This Skill Activates

  • Sending or receiving cross-system communications
  • Keywords: "transmit", "broadcast", "channel", "message", "notify"
  • Default for: Starlight Orchestrator, Starlight Prime

What This Skill Does

Manages the Starlight Transmission system - the cross-system communication protocol that enables intelligence to flow between Starlight, ACOS, Arcanea, and AI-Ops.

Procedures

Procedure 1: Send Transmission

  1. Determine the message content and priority
  2. Select the target channel(s):
    • ACOS Channel → Creator productivity updates
    • Arcanea Channel → Creative intelligence exchange
    • AI-Ops Channel → Infrastructure and research sync
    • Broadcast Channel → All systems simultaneously
  3. Format the transmission:
    • Timestamp
    • Source (Starlight + originating agent)
    • Priority (Critical/High/Normal/Low)
    • Content
    • Action required (Yes/No + description)
  4. Append to the appropriate channel file
  5. Log in Operational Vault

Procedure 2: Receive Transmission

  1. Check channel files for new entries since last read
  2. Parse incoming transmissions
  3. Classify by priority and relevance
  4. Route to appropriate agent(s)
  5. Take action if required
  6. Acknowledge receipt in channel

Procedure 3: Broadcast

  1. Compose system-wide message
  2. Validate with Starlight Prime (authorization required)
  3. Send to ALL channels simultaneously
  4. Log broadcast in Operational Vault
  5. Track acknowledgments from each system

Integration Points

  • Vault: Operational Vault (transmission logs)
  • Channels: All transmission channels
  • Agents: Orchestrator (routing), Prime (broadcast authorization)
  • Transmissions: See transmissions/TRANSMISSION_PROTOCOL.md

Quality Criteria

  • Is the message clear and actionable?
  • Is the correct channel selected?
  • Is priority accurately set?
  • Is the transmission logged?

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