michael-denyer/pstack-claude / plugins/pstack/skills/poteto-mode
poteto-mode
Verifiedpoteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.
references/omp-tools.md
View on GitHub# OMP tool mapping for pstack
OMP loads these skills from the installed pstack marketplace plugin. Skill names are unqualified unless a collision changes their namespace. For a pstack skill named by the routing instruction, read its file under the installed plugin path supplied by that instruction. This avoids resolving a same-named skill from another source. For interactive invocation, use the name shown by OMP; Claude Code's `pstack:` prefix is not an OMP skill name.
| Claude Code action | OMP action |
| --- | --- |
| Read (`Read`), write (`Write`), edit (`Edit`), search (`Grep` / `Glob`), shell (`Bash`) | `read`, `write`, `edit`, `grep`, `glob`, `bash` |
| Invoke the `Skill` tool | Read `skills/<name>/SKILL.md` in the installed plugin path supplied by the routing instruction |
| Dispatch the `Agent` tool (`subagent_type`, `general-purpose`, `pstack:poteto-agent`) | Use `task` and its advertised agent roster; include the poteto-mode instructions in the brief |
| Background dispatch (`run_in_background`) | Follow the active `task` schema; use `wait` for its result |
| Read-only child (`readonly`) | Select an available read-only agent, or explicitly prohibit writes in its brief |
| Isolated writer (`isolation: "worktree"`) | Use the active `task` schema or create separate worktrees before parallel writes |
| Ask (`AskUserQuestion`) | `ask` |
| Tasks (`TodoWrite` / `TaskCreate` / `TaskUpdate`) | `todo` |
| Web (`WebSearch`) | `web_search` when available |
| `plugin-dev:skill-development` | Use it only if available; otherwise report the missing authoring companion |
| `CLAUDE.md` / `.claude/skills` | Follow OMP's discovered context files and skill catalog; do not install pstack skills into a standalone directory |
| `${CLAUDE_CONFIG_DIR:-$HOME/.claude}/projects` transcripts | Use OMP session history and the paths or internal URLs exposed by the active session |
| `loop` | Use OMP's interactive `/loop` when available |
OMP provides its own subagent roster and model selection. Use the agents and model options listed by the active `task` tool. Map a review panel to separate task items. Do not pass Claude-specific `subagent_type` or model aliases. Follow the active OMP tool schema for effort. A task result is evidence; inspect the actual artifact before reporting it as complete.
OMP's `/loop` is an interactive session command, not a subagent tool. For a recurring interactive workflow, provide the user with the appropriate `/loop` command rather than emulating it with a sleep loop. If the current host does not expose it, follow that host's available scheduling mechanism or report the limitation.
The plugin injects its routing instruction before each main-agent turn and this mapping pointer into main and subagent turns. Restart a session after changing `session hook` to clear previously injected context. The Pi extension and its agent tools are not loaded by the OMP marketplace plugin.
OMP's marketplace skill discovery does not apply pstack's `paths` frontmatter as a file-triggered invocation rule. Invoke `typescript-best-practices` explicitly for TypeScript work when applicable.
Use the OMP session's available browser or project verification tools to drive applications. Project instructions take precedence over generic driver guidance. Where poteto-mode names the project `verify` skill at `.claude/skills/verify/`, look under `.omp/skills/verify/` first, where `create-verification-skill` writes it on OMP, then under `.claude/skills/verify/` and `.agents/skills/verify/`.
## Model names
OMP uses its own model selection; without a pstack sheet, use the runtime's defaults. The global `~/.omp/pstack-models.md` is shared across OMP profiles; `session hook: off` there disables main-session routing while retaining the subagent mapping. Configure models only when the user asks. List available chat models with `omp models --kind chat` and inspect the active OMP configuration with `omp config`. Ask which available models the user wants for routine, worker and demanding roles. Configure OMP's own `modelRoles` and `task.agentModelOverrides` through its configuration interface, preserving unrelated settings. Use only models listed by the active installation; do not copy Claude model aliases into OMP. If the available agent roster cannot select distinct models for a requested panel, report that limitation.
## Per-skill notes
| Skill | On OMP |
| --- | --- |
| `why` | Use OMP tools and available sources. |
| `automate-me` | Look for mode skills under `.omp/skills/`, `.agents/skills/`, and the active profile's agent directory (`~/.omp/agent/skills/` by default, `~/.omp/profiles/<name>/agent/skills/` under a named profile) as well as the Claude Code paths. Write a new project mode skill to `.omp/skills/<handle>-mode/SKILL.md`, and a personal one to `<handle>-mode/SKILL.md` in that agent directory's skills folder. OMP does not load a skill nested in a category directory, so keep the mode skill directly under the skills folder. |
| `create-verification-skill` | The generated skill lands under `.claude/skills/verify/` on Claude Code; on OMP write it to `.omp/skills/verify/`, where OMP loads native project skills. The app-driving harness is platform-neutral. |
| `maintain-verification-skill` | Look for the project-local skill under `.omp/skills/` first, then under `.claude/skills/` and `.agents/skills/`. |
| `create-formal-verification-skill` | On OMP write the generated skill to `.omp/skills/<area>/`, named for the area it verifies, with a `description` in its frontmatter, because OMP skips a native skill without one. The verifier and its run command are platform-neutral. |
| `maintain-formal-verification-skill` | Look for project skills, the formal verification skill among them, under `.omp/skills/` first, then under `.claude/skills/` and `.agents/skills/`. |
| `reflect` | For a pstack skill, never edit the installed plugin at the path the routing instruction names. Its edited copy is the one exception to keeping pstack skills out of a standalone directory. Before approval, show the destination in OMP's skill folders, and after approval copy the skill folder there: `.omp/skills/<skill>/` for a project copy, or `<skill>/` in the active profile's agent skills folder for a personal one. That folder is `~/.omp/profiles/$OMP_PROFILE/agent/skills/` when `OMP_PROFILE` is set, and `~/.omp/agent/skills/` otherwise. OMP skips Claude Code's personal skills folder by default, and loads it only when `skills.enableClaudeUser` is on, `enabledProviders` lists `claude`, or `CLAUDE_CONFIG_DIR` is set. Edit a project or personal skill where it already lives. OMP gives the edited copy the skill's bare name and lists the plugin's copy under a namespaced name. pstack's own skill invocations still read the plugin file, per the `Skill` row and the routing instruction, so the edited copy runs when the user or OMP's skill catalog invokes it by its bare name. |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |