jordanhindo
- 11 skills
- 0 followers
- 1 day ago last updated
- ▌ Beadboard Driver · jordanhindo bundleUse when an agent is executing work in any project repo and needs to coordinate with a human or other agents via BeadBoard. BeadBoard is the human-facing dashboard running separately; this skill is the agent-side operating contract for state, mail, assignment, and evidence flow.
- ▌ Rlm Mem · jordanhindo bundleUse when an agent needs persistent, policy-scoped memory with strict verification gates and a single canonical package path.
- ▌
- ▌ Brainstorming · jordanhindoYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- ▌ Writing Skills · jordanhindo bundleUse when creating new skills, editing existing skills, or verifying skills work before deployment
- ▌
- ▌ Lore · jordanhindo bundleUse to recall anything from past agent sessions with the server-free `lore` CLI — the "what did we decide", "how did we build X", "why did we drop Y", "find that earlier conversation", "pull context from my last session" task. Trigger whenever you need memory of prior work (yours or another harness's) — searching transcripts by keyword or recency, reading a remembered message back in full, seeing what surrounded it, skimming or jumping around a past session, listing recent sessions, or charting when a project was active. Also covers writing new memory in live (`lore push`). This skill is self-bootstrapping — if the CLI isn't installed or your sessions aren't indexed yet, it covers setup too (detail in references/setup/index.md) — installing lore, indexing or backfilling a harness (Claude Code, Codex, Cursor, Cline, openclaw, Hermes, or any tool that records transcripts), teaching lore a new format by writing and proving an adapter, registering the MCP server, wiring freshness hooks, or feeding a live process
- ▌ Lore Brief · jordanhindo bundleProduces proposal-only Lore continuity briefs for the last 24 hours by default, with cited evidence, open work, learned signals, memory-card candidates, contradiction candidates, and sideEffects:false. Use for daily briefs, recap/continuity summaries, scheduled read-only synthesis, or proposing next actions from Lore without creating anything automatically.
- ▌ Lore Recall · jordanhindo bundlePlans and executes bounded Lore memory recall with status checks, query expansion, context drill-down, freshness labels, cited evidence packets, and retrieval-failure recovery. Use whenever an agent needs to answer from past Lore sessions, recall decisions, inspect last-session context, verify what happened before, or explain gaps without dumping transcripts.
- ▌ Lore Handoff · jordanhindo bundleBuilds compact Lore continuation handoff packets with verified/open/stale/risky sections, cited evidence, artifacts, shared proposal vocabulary, unresolved questions, and no transcript dumps. Use when handing work to another agent, resuming later, compacting active work, or preparing next-agent context from Lore.
- ▌ Lore Dev Verification · jordanhindo bundleVerifies changes to the Lore repo and Lore workflow skills. Use when working on Lore PRs, issue slices, recall/brief/handoff skills, CLI/MCP retrieval, store migrations, adapters, privacy/destructive-memory behavior, packaging, or any change that needs proof before it is called done.