Run any Skill in Manus with one click

murmur-learn

Stars7

Forks0

UpdatedJuly 11, 2026 at 01:55

Record one operator-observed lesson in Murmur's compounding learnings journal. Use when the user asks to record a learning or gives input like "<agent>: <lesson>" for `.codex/learnings/<agent>.md`.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

murmur-io

murmur-io/murmur

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	murmur-learn
description	Record one operator-observed lesson in Murmur's compounding learnings journal. Use when the user asks to record a learning or gives input like "<agent>: <lesson>" for `.codex/learnings/<agent>.md`.

Murmur Learn

Record a learning in the compounding-lessons loop. The expected input is:

<agent>: <lesson text>

Valid agents are the files in .codex/learnings/: angular-zoneless-dev, rust-tauri-dev, adversarial-verifier, lock-security-reviewer, release-engineer, and murmur-researcher.

Steps

Parse <agent> before the first : and <lesson> after it. If the agent is unknown, list valid agents and stop.
Open .codex/learnings/<agent>.md.

Insert a new entry at the top of ## Run journal:

### [<today> operator] <one-line title derived from the lesson>
- **Pattern:** <what happens / the failure mode, in the operator's words>
- **Caught by:** operator
- **Lesson:** <the imperative to apply next time>
- **Status:** journal

Use date +%F for <today>.
Do not touch ## Recurring patterns; promotion belongs to murmur-curate-learnings.
If the journal exceeds about 50 entries, drop the oldest journal entries only. Never drop distilled or success-pattern entries.
Confirm the one-line title added; do not restate the full file.

More from this repository

same repository

harness

murmur-io/murmur

Run a change through the full Murmur harness — isolated worktree, writer, deterministic checks, independent adversarial + risk reviews, hash-bound PASS attestation, guarded commit. Use PROACTIVELY when a change is risky, multi-step, or you want the earned safety net (lock/crypto/egress/protocol, or anything you want independently verified). Skip it for docs, chores, and low-risk edits — those commit normally.

2026-07-247

release-murmur

murmur-io/murmur

Cut a signed, notarized macOS release of Murmur (Tauri 2 + Angular 22). The exact, proven step-by-step runbook — preflight gates → version bump (+ Cargo.lock sync) → QueaT commit → PR-merge to the `murmur` trunk (never direct-push) → rustup targets → stop dev → universal build → Developer-ID sign BY IDENTITY HASH (the Polish-ń cert gotcha) → DMG → notarize → staple/spctl → gh release create + upload. Use whenever the user wants to ship, release, cut a version, build a distributable .app/.dmg, sign/notarize, or publish a GitHub release of Murmur. Supersedes the stale docs/RELEASE-CHECKLIST.md.

The agentic feature-shipping discipline for Murmur (Tauri 2.11 Rust core + Angular 22 zoneless). Scope → (Workflow) plan → build backend and/or FE under the project conventions → ADVERSARIAL verify (an adversarial-verifier pass, plus a lock-security review when the change touches the lock/crypto/visibility path) → gates green (cargo test --lib, ng lint, ng build, scripts/ci.sh) → QueaT commit → PR to the `murmur` trunk. Use whenever the user wants to build, implement, add, or ship a feature/fix in Murmur end-to-end. Encodes the verify-before-trust discipline that caught 7 bugs.

2026-07-237

tauri-dev

murmur-io/murmur

Run and iterate Murmur locally (Tauri 2.11 + Angular 22 zoneless). The exact dev-run recipe — MURMUR_DEV_DEK/MURMUR_DEV_KEK to avoid keychain prompts, source ~/.cargo/env, ng on :1420 + MCP on :8765, the `cargo test --lib`-not-`clippy --all-targets` inner loop, owner-aware clean relaunch, and reading the boot/abort log. Use whenever the user wants to start/run/serve Murmur in dev, debug a launch/abort, relaunch cleanly, or run the Rust test loop.

name	murmur-learn
description	Record one operator-observed lesson in Murmur's compounding learnings journal. Use when the user asks to record a learning or gives input like "<agent>: <lesson>" for `.codex/learnings/<agent>.md`.

Murmur Learn

Record a learning in the compounding-lessons loop. The expected input is:

<agent>: <lesson text>

Valid agents are the files in .codex/learnings/: angular-zoneless-dev, rust-tauri-dev, adversarial-verifier, lock-security-reviewer, release-engineer, and murmur-researcher.

Steps

Parse <agent> before the first : and <lesson> after it. If the agent is unknown, list valid agents and stop.
Open .codex/learnings/<agent>.md.

Insert a new entry at the top of ## Run journal:

### [<today> operator] <one-line title derived from the lesson>
- **Pattern:** <what happens / the failure mode, in the operator's words>
- **Caught by:** operator
- **Lesson:** <the imperative to apply next time>
- **Status:** journal

Use date +%F for <today>.
Do not touch ## Recurring patterns; promotion belongs to murmur-curate-learnings.
If the journal exceeds about 50 entries, drop the oldest journal entries only. Never drop distilled or success-pattern entries.
Confirm the one-line title added; do not restate the full file.