Menu
SkillsMP has collected 15 skills from agentculture/reachy-mini-cli. Open a skill to review its source and details.
Showing 15 of 15 collected skills.
Find a Reachy Mini Wireless on the local network without a human typing an IP: sweep the LAN, remember which unit is yours, and log into it over SSH. Wraps `reachy wireless` (`reachy/discover/`) — a stdlib-only HTTP probe plus a bounded, capped,…
Ask the repository's Colleague harness for an independent read-only explore or review, a previewed scoped write, or feedback on a finished work item. Use when the user asks to consult a colleague or when a fresh, independently verifiable perspective would…
Fan out a converged Devague plan's dependency waves to isolated workers with human approval of the implementation split and test-gated reconciliation. Use when the user asks to assign a plan to a workforce, fan out work, or run approved plan waves in parallel.
Pressure-test a converged, exported Devague spec for blind spots before planning. Use when the user asks to challenge a spec, find missing risks or unknowns, run a blind-spot pass, or proceed from think to spec-to-plan.
Coordinate with sibling repositories and Culture mesh agents through tracked GitHub handoffs, issue follow-ups, current issue reads, or ephemeral channel messages. Use when work or a question needs to cross the reachy-mini-cli repository boundary.
Stop and record an execution-time departure from a confirmed Devague plan before work continues. Use when reality no longer matches an approved task, dependency, acceptance criterion, or workforce split.
Explore what a feature idea touches before framing it into a spec. Use for scope exploration across code, tests, docs, CI, skills, deployment, hardware, and sibling systems, especially when the user asks to scope, map boundaries, or ground a Devague frame in…
Turn a converged Devague spec into a buildable, dependency-ordered plan with complete claim coverage and testable acceptance criteria. Use after think and challenge, or when the user asks to plan a spec or create an implementation plan.
Close a Devague workforce run with an evidence-backed planned-versus-actual delivery artifact. Use after complete, partial, or failed execution when the user asks what shipped, requests a delivery summary, or wants remaining work and drift recorded honestly.
Turn a vague idea into a converged, buildable Devague spec by working backwards from the shipped announcement. Use when the user asks to think an idea through, write a spec, work backwards, or continue from scope exploration.
Search the shared eidetic memory store and get back ranked, provenanced records. Drives `eidetic recall` with four search modes — exact (verbatim substring), approximate (vector/semantic), keyword (BM25 lexical), and hybrid (a weighted blend of…
Ingest records into the shared eidetic memory store so they can be recalled later. Drives `eidetic remember`: accepts one record as a JSON object, or a batch as NDJSON on stdin for bulk ingest. Upsert is idempotent by id (and dedups by content hash) —…
reachy-mini-cli's CI/CD lane, layered on `agex pr`. Delegates lint / open / read / reply / delta to agex; adds two extensions — `status` (SonarCloud quality gate + hotspots + unresolved-thread tally) and `await` (read --wait + status with non-zero exit on…
Cross-repo + mesh communication from reachy-mini-cli: file tracked GitHub issues on sibling repos, fetch issues from sibling repos to inline current state into briefs, and send live messages to Culture mesh channels. Use when the next step lives outside…
Fan out a converged devague plan's dependency waves to parallel agents in isolated git worktrees, one agent per task per wave, with TDD-gated merges by the main agent. Human gates: the exported spec, the implementation split plan (task map + per-task…