Myr

What This Skill Does

The Myr (Methodological Yield Reports) skill is an intelligence compounding system designed for Starfighter/Pistis architectures. It operates on the core OODA (Observe, Orient, Decide, Act) loop to capture, index, and verify intellectual yield. Unlike standard note-taking, Myr creates cryptographically signed artifacts that allow for the secure exchange of techniques, insights, and pattern recognitions across different computing nodes. By centralizing the 'yield' of an agent's problem-solving process, it ensures that lessons learned in one session are never lost and can be synthesized into broader, cumulative intelligence.

Installation

1. Install via OpenClaw: clawhub install openclaw/skills/skills/jordangreenhall/myr
2. Clone the repository: git clone https://github.com/JordanGreenhall/myr-system.git
3. Navigate to the directory: cd myr-system
4. Install dependencies: npm install
5. Initialize configuration: cp config.example.json config.json
6. Update config.json with a unique node_id (do not use 'n1').
7. Generate keys: node scripts/myr-keygen.js
8. Set the environment variable: export MYR_HOME=/absolute/path/to/myr-system
9. Verify identity: node $MYR_HOME/scripts/myr-identity.js

Use Cases

• Continuous Learning: Documenting successful techniques during high-stakes debugging sessions so they become part of the agent's reusable pattern library.
• Agent Collaboration: Exporting verified MYRs between distributed nodes to sync shared intelligence while maintaining cryptographic provenance.
• Quality Control: Using the myr-verify and myr-sign tools to ensure that only high-integrity data enters the collective memory system.
• Weekly Synthesis: Generating digests of OODA cycle results to track progress on long-term initiatives.

Example Prompts

1. "Myr, store a new yield regarding the recent API timeout fix: mark it as a technique, note the evidence of consistent latency improvement, and tag it as 'network-stability'."
2. "What did we learn about the authentication flow patterns from last week's sessions? Provide a summary of the captured MYRs."
3. "Export all verified yield artifacts to the secure share node; verify identities before proceeding."

Tips & Limitations

• Security First: Never exchange yield with a node without manually confirming the node_uuid and SHA256 fingerprint out-of-band.
• Uniqueness: The system will strictly fail if you attempt to run with the default 'n1' node ID. Always assign a unique identifier.
• Maintenance: Run the ping test (myr-store, myr-search, myr-verify, myr-sign, myr-export) periodically to ensure your node is healthy.
• Scope: Myr is designed for structured methodological output; ensure your input data is clear and follows the OODA cycle structure for best results.