agentsclimarketplace

Observe

Skill hyuniiiv/quantum-agent/skills/observe

Install
npx -y skills add hyuniiiv/quantum-agent --skill observe

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

QuantumAgent — Inspect the live superposition of running cosmos agents. Read insights, detect resonance (agreement), uncertainty (divergence), tunneling, and condensate signals across all cosmos namespaces.

SKILL.md

9.5 KB, as published. Nobody here has run it

cosmos:observe

Show the current superposition snapshot: all cosmos insights, resonance signals, and uncertainty map. Uses Claude's semantic judgment — no vector database needed.

Trigger

/cosmos observe

Also called automatically after /cosmos spawn completes.

Execution Steps

Step 1 — Detect repo root

git rev-parse --show-toplevel

Store as <repo_root>.

Step 2 — Read macro-scale context (optional)

Project Spin — read if exists:

[ -f <repo_root>/.quantum/project/spin.json ] && cat <repo_root>/.quantum/project/spin.json

Capture: name, type, description, immutable_constraints.

Active Singularities — read if exists:

[ -f <repo_root>/.quantum/singularities/events.jsonl ] && cat <repo_root>/.quantum/singularities/events.jsonl

Parse each line. The most recent singularity (by ts) defines the current era. Earlier singularities are historical context.

If neither exists: skip silently. Continue to insight reading.

Code-scale findings (v4.0+) — read if exists:

[ -f <repo_root>/.quantum/code/findings.jsonl ] && cat <repo_root>/.quantum/code/findings.jsonl

Parse each line. Schemas vary by type field:

  • code-tunnel — type-system bypass at (file, line)
  • code-decoherence — untested source file
  • code-superposition — feature flag / A/B branch
  • code-jump — high recent git churn

Take the most recent scan's findings (group by closest timestamp cluster, or just the latest 200 lines if many). Earlier scans are historical.

If file doesn't exist: skip silently. Continue to insight reading.

Step 2.5 — Read all insights

Read every file matching <repo_root>/.quantum/*/insights.jsonl.

Parse each line as JSON. Current schema (preferred):

{"type": "<type>", "content": "<text>", "ts": "<timestamp>"}

Legacy compatibility:

  • If type is missing → treat as "discovery"
  • If content starts with [TUNNEL] → treat as type: "tunnel"
  • If content starts with [JUMP] → treat as type: "jump"

Build a map: cosmos_id → [insights sorted by ts]. Also build a secondary index type → [insights] for grouped reporting in Step 4.

If .quantum/ is empty or missing, output:

(no cosmos active — run /cosmos spawn first)

Step 3 — Output superposition snapshot

For each cosmos (sorted alphabetically), output:

🌌 cosmos:<name>  (<N> insights)  — <strategy>
   └ <most recent insight, truncated to 120 chars>
   └ <second most recent insight, truncated to 120 chars>

Step 4 — Detect Resonance and Uncertainty

Using all insights from Step 2, perform two analyses:

Resonance — decisions where 2+ cosmos independently reached the same conclusion. These are answers you can trust regardless of which strategy you pick.

  • List each resonant decision as one line
  • Note how many cosmos converged on it

Uncertainty — decisions where cosmos reached genuinely different conclusions. These are real tradeoffs with no universal answer. The developer must choose.

  • List each uncertain decision as one line
  • Briefly name what each cosmos chose

Decoherence — if a cosmos appears to have abandoned its core strategy and simply copied another cosmos, flag it. Healthy entanglement is influence, not wholesale adoption.

Degeneracy — if two or more cosmos with different strategies arrived at functionally identical implementations (same library, same algorithm, same concrete design), that is Degeneracy: the problem had a single natural solution regardless of approach. Flag this separately from Resonance (which is about conclusions, not implementations being identical).

Tunneling — collect all insights with type: "tunnel" (or legacy [TUNNEL] content prefix). These are solutions that bypassed assumed constraints. List each one.

Quantum Jump — collect all insights with type: "jump" (or legacy [JUMP] content prefix). These are discontinuous architectural leaps triggered by a single entanglement read. List each one with the cosmos it came from.

Blockers — collect all type: "blocker" insights still unresolved (no later type: "decision" or type: "discovery" from the same cosmos that addresses them). Surface these — they need developer attention.

Live entanglement audit (v1.3) — for runs using --entanglement strict, verify the heartbeat protocol:

  1. Collect all type: "heartbeat" entries across cosmos. Each has step, ts, source cosmos.
  2. Collect all type: "heartbeat-ack" entries. Each has refs: ["<cosmos>@<ts>", ...] citing the heartbeats it acknowledges.
  3. For each heartbeat H from cosmos C at time T:
    • For every OTHER active cosmos C', check if C' has emitted any heartbeat-ack whose refs includes C@T (or a later T' from C).
    • If not → H is unacknowledged by C' → broken entanglement.
  4. Compute entanglement quality:
    • total_heartbeats × (N - 1) = expected ACK count (each heartbeat needs ACK from every other cosmos)
    • actual_acks = total heartbeat-ack count
    • ratio = actual / expected
    • High if ratio ≥ 0.8, Medium if 0.4 ≤ ratio < 0.8, Low if < 0.4
  5. List broken channels: <cosmos_C> → <cosmos_C'>: <count> unacknowledged heartbeat(s).

For non-strict runs (none/passive/active), heartbeat audit is skipped. Optionally, for any run, scan insight content and read_from fields for cross-cosmos references to compute an informal entanglement signal (count of insights citing other cosmos / total insights).

Step 5 — Output quantum map

Macro context block (only if Step 2 loaded any):

🌍 Project Spin — <name> (<type>)
   <description>
   Immutable constraints:
     • <constraint 1>
     • <constraint 2>

☄️  Active Singularities — <count> event(s):
   <ts>  <name>: <description>
                  Invalidates: <invalidates>
   <ts>  <name>: <description>
                  Invalidates: <invalidates>

   Current era: post-<most-recent-singularity-name> (since <ts>)

Code-scale block (v4.0, only if .quantum/code/findings.jsonl had any):

⚛️  Code-scale findings (last scan):
   Tunnels:        <N>  type-system bypasses
   Decoherence:    <N>  source files without tests
   Superposition:  <N>  feature flags / A/B branches
   Jumps:          <N>  high-churn files  (if --git-churn-threshold was used)

   Top tunnel hotspots (file:line — subtype):
     <file>:<line>  <subtype>  "<evidence>"
     <file>:<line>  <subtype>  "<evidence>"

   Top decoherent files:
     <file>  (no test found)

   Cross-scale signal: (only if cosmos modified these files)
     cosmos:<name> touched <file> which has code-tunnel — review at next crystallize

Then the standard quantum map:

⚡ Resonance — trust these (all strategies converged):
   "<decision>" — N cosmos independently concluded this
   "<decision>" — N cosmos independently concluded this

🌀 Uncertainty — your call (strategies diverged):
   "<decision>" — alpha: <choice A>  |  beta: <choice B>  |  gamma: <choice C>
   "<decision>" — alpha: <choice A>  |  beta/gamma: <choice B>

♊ Degeneracy: (only if applicable)
   cosmos:<nameA> and cosmos:<nameB> reached identical implementations despite different
   strategies — the problem has a single natural solution

⚛️  Quantum Tunneling: (only if [TUNNEL]-tagged insights exist)
   cosmos:<name>: "<insight content>"

⚡ Quantum Jump: (only if [JUMP]-tagged insights exist)
   cosmos:<name>: "<insight content>"

⚠️  Decoherence detected: (only if applicable)
   cosmos:<name> appears to have lost its <strategy> identity — review its insights

🔗 Live entanglement quality: <High | Medium | Low>   (v1.3+, when applicable)
   Strict runs: <actual>/<expected> heartbeat ACKs (<ratio>%)
   Broken channels: (only if any)
     • cosmos:<C> → cosmos:<C'>: <N> unacknowledged heartbeat(s)
   Non-strict runs: <X>/<total> insights reference other cosmos (informal signal)

Bose-Einstein Condensate check: Fires only when ALL three conditions hold:

  1. ≥3 distinct decisions are detected in the Resonance map
  2. Zero Uncertainty items
  3. All active cosmos participated in every resonance (no cosmos sat out a decision)

If all three hold, append:

🌡️  Bose-Einstein Condensate: complete convergence across all decisions.
    The goal was deterministic — any strategy would have found the same answer.

Footer (always):

🔬 Non-destructive observation — superposition intact.
   Run /cosmos crystallize <id> to collapse a cosmos into a definite result.

If no resonance detected:

⚡ Resonance:
   (none yet — cosmos may still be in early stages)

Output philosophy

  • Resonance = the quantum signal that this answer is robust. Multiple independent paths found it. Ship with confidence.
  • Uncertainty = the Heisenberg limit of this problem. You cannot optimize all dimensions simultaneously. Make a conscious choice.
  • Degeneracy = same implementation from different strategies. The problem itself points to one answer — strategy choice was irrelevant.
  • Decoherence = a cosmos that lost coherence. Its insights may still be valuable but its strategy is no longer a true independent sample.
  • Tunneling / Jump = non-obvious breakthroughs. Worth examining even if you don't crystallize that cosmos.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.