Use @agimon-ai/doompi-sandbox: Container sandbox for DoomPi launches: the agent, extensions, and tools run inside Docker or Podman while the terminal stays on the host
AgiFlow/doompi
SkillsMP has collected 29 skills from AgiFlow/doompi. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 29
- GitHub stars
- 14
- GitHub forks
- 1
Skills in this repository
Showing 29 of 29 collected skills.
Configure DoomPi plugin catalogs and domain resource selections in domains.yaml. Use when creating or editing .doom/domains.yaml or ~/.pi/.doom/domains.yaml, choosing local, Git, or npm plugins, filtering plugin resources, setting aliases or defaults, or…
Use Doom Pi MCP to inspect domain-scoped servers, authenticate, reload configuration, measure what server tool schemas cost in context, and troubleshoot tool availability.
Manage long-running commands started by bash: dev servers, watchers, builds, tails, and anything that prompts for input. Trigger when a command needs to outlive the current turn, when bash output was truncated, or when a background process needs to be…
Architectural review and design-pattern enforcement for this repository, run as a CLI. Hooks already surface patterns before an edit and diagnostics after a batch, so reach for this when you need an explicit sweep, want to know which rules govern a file…
Use @agimon-ai/doompi-cache: Provider prompt cache policy and deterministic routing for DoomPi
Configure DoomPi runtime settings, source precedence, and typed session configuration. Use for config.yaml, the doom/config Cordis service, immutable context snapshots, or shared selection transition state. Do not use for defining modes.yaml, domains.yaml, or…
Configure DoomPi default packages, layers, extensions, hook groups, and named major modes. Use when creating or editing ~/.pi/.doom/modes.yaml or a repository's .doom/modes.yaml, choosing a default mode, or diagnosing which behavior a mode activates.
Configure DoomPi profile discovery, personas, environment defaults, and precedence in profiles.yaml. Use when creating or changing personal or repository profiles. Do not use for config.yaml runtime settings, modes.yaml, or domains.yaml.
Author and distribute DoomPi agent skills. Use when creating a SKILL.md, adding supporting references or scripts, contributing a runtime skill directory through Cordis, or publishing activation-gated Help prompts from a DoomPi package.
Use DoomPi's skill catalog and deferred discovery. Use when browsing available skills, invoking /skill:name, understanding Help and extension-owned skill groups, or diagnosing why a skill is absent or shadowed.
Create or update a DoomPi extension package inside the DoomPi monorepo or as an external npm package. Use for package layout, Pi discovery entries, shared Cordis lifecycle, package-owned Help, and extension verification.
Author DoomPi repository or plugin hooks. Use when creating or changing .doom/hooks.yaml, selecting hook groups from modes.yaml, writing hook commands, or adapting Claude Code hook payloads and decisions to DoomPi.
Use Doom Pi Runner to supervise shell commands, inspect durable logs, provide interactive input, and stop background runs.
Use Doom Pi Goal to start, budget, pause, resume, complete, block, and inspect persistent repository goals.
Use Doom Pi Help to activate package guidance, load exact-version skills, and diagnose unavailable or conflicting contributions.
Use Doom Pi Loop to start, inspect, and stop session-scoped recurring prompts safely.
Use Doom Pi Plan to draft reviewable normal, debug, or Fable-assisted plans, persist them, and exit safely.
Use Doom Pi Voice for manual transcription, autonomous capture, narration, configuration, and recovery on macOS.
Recover a failed or interrupted workflow-mcp run so it resumes from its active repair rather than starting over. Use before calling workflow_run with action recover, whenever a run shows stage error or interrupted, or when deciding between recovering a run,…
Author DoomPi workflow definitions. Use when creating or changing a *.workflow.yml graph, arranging job dependencies and host-executed steps, or deciding how a command requiring a TTY should run.
Use DoomPi workflows. Use when discovering or launching workflows, monitoring or controlling asynchronous runs, interpreting terminal notifications, or recovering a failed run safely.
Draft a clear, source-backed blog post from an approved outline and research brief. Use when the structure and factual basis are ready for prose.
Turn an approved blog brief and research into a focused, source-aware outline. Use after research and before drafting a post.
Research a blog topic and produce a traceable source brief. Use before outlining or drafting when claims need current facts, external evidence, quotations, or links.
Fact-check and edit a blog draft for accuracy, structure, clarity, and publication readiness. Use after drafting or when the user requests an editorial review.
Implement scoped code changes in an existing repository and verify them with its native checks. Use when the user asks to build, change, or fix code, not for a review-only request.
Review a code change for concrete defects, regressions, missing tests, and contract violations. Use when the user asks for code review, diff review, or risk assessment, not as a general implementation workflow.
Design, add, and run focused tests for repository behavior. Use for test implementation, regression coverage, verification, or diagnosing a failing test, not for a review-only request.