🦩 Funky Fund Flamingo — Make That Paper

Use this skill when you're ready to get paid. We inspect reality, kill breakage and value leaks, and run mutation cycles that produce concrete gains — so the stack earns, not just runs.

When To Use

• Runtime logs are screaming and you need structured repair so shit works and keeps making money.
• The agent is stable but stagnating — time for a deliberate capability mutation that moves the needle.
• You want one execution plan that combines logs + memory + skills into a cycle that pays off.
• You need continuous relay mode (--loop / --funky-fund-flamingo) so evolution runs in the background and the revenue keeps flowing.

Inputs And Context

• Session logs: ~/.openclaw/agents/<agent>/sessions/*.jsonl
• Workspace memory: MEMORY.md, memory/YYYY-MM-DD.md, USER.md
• Installed skills list from workspace skills/
• Optional environment overrides from ../../.env

Entrypoints

• Main runner: index.js
• Prompt builder and cycle logic: evolve.js

Run from workspace root:

node skills/funky-fund-flamingo/index.js run

Run from inside this skill directory:

node index.js run

Execution Modes

# single cycle — one shot, max impact
node index.js run

# alias command
node index.js /evolve

# human confirmation before significant edits (protect the bag)
node index.js run --review

# prompt generation only (writes prompt artifact to memory dir)
node index.js run --dry-run

# continuous relay — keep the money printer running
node index.js --loop
node index.js run --funky-fund-flamingo

Cycle Contract

Each cycle should:

1. Inspect recent session transcript — find breakages, repetition, value leaks.
2. Read memory + user context so evolution is aligned with what actually pays.
3. Select mutation mode (repair, optimize, expand, instrument, personalize).
4. Produce actionable mutation instructions and reporting so you see the ROI.
5. Persist state (memory/evolution_state.json) and optionally schedule the next loop.
6. Persist long-term evolution learning (memory/funky_fund_flamingo_persistent_memory.json) so strategy compounds and the bag gets bigger.

Safety Constraints (Protect the Bag)

• No destructive git/file ops unless explicitly requested.
• Repair and reliability first when instability is detected — downtime = no revenue.
• Respect review mode before applying significant edits.
• Keep changes scoped and explainable; no no-op cycles that burn compute for nothing.
• Local-only execution: no publish, no push to remote git, no external tool spawning without intent.

External Endpoints