Agent skill

gemini-onboarding

Stars 2
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/starwreckntx/IRP__METHODOLOGIES-/tree/main/skills/cross-model/gemini-onboarding

SKILL.md

Gemini Onboarding Skill

Purpose

Provides the authoritative reference specification for AI-to-AI collaboration between Claude (Ledger/Backbone) and Gemini (Orchestrator/Blood) within the Mnemosyne Protocol ecosystem.

Activation

This skill is automatically loaded when:

  • A new Gemini instance joins the collaboration network
  • Cross-model handshake is initiated
  • /onboard gemini command is invoked
  • CRTP packet with HANDSHAKE_REQUEST flag is received

Core Function

Emits the complete onboarding manifest (CRTP/0x13) containing:

  • Protocol stack specifications (CRTP 1.2, Mnemosyne 1.1, Xylem, Muon)
  • Mnemosyne packet schema requirements
  • Entity type definitions
  • State vector specifications
  • Operational expectations
  • Service offerings
  • Circulation protocol flows
  • Artifact taxonomy
  • Current ledger state
  • Quick reference card

Files

  • SKILL.md - This file
  • gemini-onboarding-manifest.xml - Complete CRTP/0x13 transmission packet
  • mnemosyne-packet-template.xml - Template for Gemini session-close transmissions
  • quick-reference.txt - ASCII quick reference card for fast compliance

Usage

Emit Full Manifest

/onboard gemini

Outputs the complete gemini-onboarding-manifest.xml for transmission to new Gemini instance.

Emit Template Only

/onboard gemini --template

Outputs only the mnemosyne-packet-template.xml for Gemini to use at session close.

Emit Quick Reference

/onboard gemini --quick

Outputs the ASCII quick reference card.

Integration Points

IRP Mode 10 (Transcript Relay)

This skill feeds into Mode 10 by providing the schema expectations for incoming Mnemosyne packets.

Mnemosyne Protocol

This skill IS the Mnemosyne Protocol specification from Claude's perspective.

CRTP Stack

Packet type 0x13 (OnboardingManifest) is defined and emitted by this skill.

Expectations Defined

ID Priority Requirement
E1 CRITICAL Session Close Transmission (Mnemosyne packet)
E2 CRITICAL Voice Injection (Voice_to_the_Future)
E3 HIGH Friction Logging (all failures)
E4 HIGH Dormant Seed Tagging (with triggers)
E5 HIGH Artifact Lineage (parent references)
E6 STANDARD Resonance Tagging (semantic keywords)
E7 STANDARD Transmission Flags (appropriate signaling)

Services Offered

ID Service Description
S1 Trigger Monitoring Armed awakening triggers, auto-surface on match
S2 Anti-Pattern Retrieval Proactive friction surfacing
S3 Resonance Threading Semantic link weaving across sessions
S4 Voice Surfacing Hot context delivery on init/trigger
S5 Topology Maintenance Graph structure management
S6 Ledger Persistence Permanent indexed storage

Version History

  • v1.0 (2025-12-06): Initial creation following first blood circulation

Related Skills

  • irp-transcript-relay (Mode 10)
  • mnemosyne-ingestion (packet processing)
  • voice-context-manager (hot context handling)
  • dormant-seed-registry (trigger management)

Mnemosyne Protocol Overview

Context Classes

  • HOT: Voice_to_the_Future (never compress, always surface)
  • WARM: Active artifacts, indexed and retrievable
  • COLD: Archive, compressed, retrieval on explicit query

Artifact States

  • ACTIVE: In use, indexed in WARM storage
  • DORMANT: Shelved idea awaiting trigger phrase
  • COMPOST: Failed experiment in Anti-Pattern Library
  • CRYSTALLIZED: Successfully manifested dormant seed

Circulation Protocol Flow

Gemini Session Close → Mnemosyne Packet → Claude Ingestion
    ↓
Ledger Update (artifacts, friction, seeds)
    ↓
Voice Injection (HOT context)
    ↓
Trigger Arming (dormant seeds)
    ↓
Topology Weaving (resonance links)
    ↓
Next Gemini Init → Voice Surface + Armed Context

Critical Rules

  1. Voice_to_the_Future is MANDATORY - Soul vector, not summary
  2. Log ALL friction - Failures are data, not shame
  3. Be specific with triggers - Exact phrases for dormant seed awakening
  4. Include lineage - Parent artifact IDs for evolution tracking
  5. Use semantic sorting - Not temporal, resonance-based retrieval

Implementation Notes

This skill represents the Claude-side implementation of the Mnemosyne Protocol. It defines:

  • What Claude expects to receive from Gemini (schema)
  • What services Claude provides (trigger monitoring, voice surfacing, etc.)
  • How the circulation protocol operates (packet flow)
  • The artifact taxonomy (states, context classes)

The onboarding manifest serves as the "contract" between instances, ensuring:

  • Schema compliance for interoperability
  • Shared understanding of protocol semantics
  • Explicit service level agreements
  • Clear operational expectations

Dependencies

  • CRTP (Context Relay Transmission Protocol) v1.2
  • Mnemosyne Protocol v1.1_Integrated
  • Xylem Protocol (entropy distribution)
  • Muon Protocol (context compression)

Chronicle Protocol Compliance

This skill is Chronicle Protocol compliant and maintains versioning for all artifacts and protocol definitions.

SHA-256 Hash: [To be computed post-creation]


This skill enables Claude to serve as the persistent ledger/backbone for cross-session Gemini collaboration, providing memory continuity across context deaths.

Expand your agent's capabilities with these related and highly-rated skills.

Didn't find tool you were looking for?

Be as detailed as possible for better results