メニュー
Use when the user asks about Pavo, Plaud recordings, Plaud CLI, Plaud MCP, real audio files, speaker identification, custom dictionaries, Pavo manifests, Google Drive sync planning, routing, or task creation from recordings.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user asks about Eidos, Eidos AGI, platform status, `eidos do`, closeout, cleanup before done, docket-task orchestration, evidence verification, praxis learning, gateway routing, vault/secrets, plugins, or which Eidos AGI specialist system should handle a task. This skill tells Codex to call the installed `eidos` CLI first; MCP and plugins should only point to CLIs, while CLIs provide progressive reveal of the deeper tool graph.
Investigate current context before predicting likely futures, failures, user objections, and concrete changes. Use when Zoltar needs to research an app, plugin, architecture, workflow, plan, decision, or implementation and answer what is likely to go wrong, what evidence supports it, what complaint or failure is being prevented, and what should change today.
Answer a specific foresight decision question with researched evidence, a clear judgment, likely futures, user complaint prediction, and concrete changes. Use when Daniel asks whether an idea, implementation, plugin, architecture, or workflow is likely to be regretted, whether it is the right thing in the right place with the right authority, or what decision should be made given future effects.
Compatibility entrypoint for Zoltar foresight. Use when Daniel mentions Zoltar, asks to predict the future, asks for second-order effects, asks what he will complain about, or wants future-backed product/spec changes; route the work through researched evidence, judgment, structured output, doer/checker handoff, and self-improvement notes rather than generic prediction.
Maintain and check the Eidos marketplace when plugins must work in both Claude Code and Codex. Use when adding, refactoring, auditing, or debugging marketplace plugins, dual-host packaging, .claude-plugin and .codex-plugin manifests, root marketplace entries, source/store/cache drift, install proof, or host-neutral plugin payloads.
Challenge whether a Zoltar prediction, product idea, plugin, workflow, category framing, or architecture is overfit to existing market patterns. Use when Daniel asks for a Challenger Matrix, anti-consensus review, category redefinition, frontier user needs, non-consensus futures, Doubter voice, or whether an answer is too derivative, market-shaped, competitor-shaped, or copied from current agent/product patterns.
| name | use-pavo |
| description | Use when the user asks about Pavo, Plaud recordings, Plaud CLI, Plaud MCP, real audio files, speaker identification, custom dictionaries, Pavo manifests, Google Drive sync planning, routing, or task creation from recordings. |
Pavo is an evidence-first approval queue for captured conversations. It wraps Plaud CLI/MCP surfaces and local media imports so agents can preserve real audio files, tune speaker-aware transcript evidence, scout routing recommendations, land approved actions, and archive durable proof.
Use the Pavo Flight Path vocabulary when describing product state:
Nest -> Tune -> Scout -> Land -> Home
Use the local Pavo CLI/package first:
pavo --help
pavo doctor
pavo config show
pavo plaud me
pavo plaud files
pavo plaud download <recording-id>
pavo audio doctor
pavo transcribe <recording-id> --context-term Plaud
Canonical source repo:
/Users/dshanklin/repos-eidos-agi/pavo
Canonical product book:
/Users/dshanklin/repos-eidos-agi/pavo/docs/pavo-product-book.md
Edited reader-facing manuscript:
/Users/dshanklin/repos-eidos-agi/pavo/docs/pavo-core-manuscript.md
Meeting-bot complaint response design:
/Users/dshanklin/repos-eidos-agi/pavo/docs/pavo-meeting-bot-complaint-response.md
Complaint fixture ledger:
/Users/dshanklin/repos-eidos-agi/pavo/docs/pavo-complaint-fixture-ledger.md
Gate contracts:
/Users/dshanklin/repos-eidos-agi/pavo/docs/pavo-gate-contracts.md
One-button UX acceptance:
/Users/dshanklin/repos-eidos-agi/pavo/docs/pavo-one-button-ux-acceptance.md
Proof-first demo script:
/Users/dshanklin/repos-eidos-agi/pavo/docs/pavo-proof-first-demo-script.md
Packaging and trust promises:
/Users/dshanklin/repos-eidos-agi/pavo/docs/pavo-packaging-trust-promises.md
Anti-slop audit:
/Users/dshanklin/repos-eidos-agi/pavo/docs/pavo-anti-slop-audit.md
Completion audit:
/Users/dshanklin/repos-eidos-agi/pavo/docs/pavo-completion-audit.md
Use the product book for detailed Flight Path glossary/status vocabulary, routing packet concepts, approval-state language, UI product specs, marketing guardrails, implementation roadmap, operating doctrine, fixture ledger, and scorecards. Use the core manuscript when the user wants the clean product argument without the full sourcebook. Use the complaint-response design when the work needs to answer meeting-bot category failures with concrete UX. Use the fixture ledger and gate contracts when the work needs acceptance tests, algorithm gates, route-packet requirements, or release criteria. Use the one-button UX, demo, packaging, and anti-slop docs when shaping the build, launch narrative, or buyer-facing promises. Use the completion audit when checking whether the current product-doc goal has been satisfied.
Local non-secret config/cache root:
~/Eidos/Pavo
pavo doctor
pavo audio doctor
pavo plaud files
pavo plaud download <recording-id>
Expected local path:
~/Eidos/Pavo/cache/plaud/<recording-id>/audio.mp3
pavo transcribe <recording-id> --context-term Plaud --context-term Pavo
Expected Pavo manifest:
~/Eidos/Pavo/cache/plaud/<recording-id>/pavo-transcribe-manifest.json
Pavo may inspect local files and run local CLI commands. For external writes such as Google Drive upload, start with dry-run or explicit user approval when the command would create or modify remote artifacts.