Menu
Probe, test, and document every tool the agent harness has access to (native tools, subagents, connected MCP servers). Use when the user wants to test, audit, or inventory the harness's tool/capability set, or asks "what tools do you have".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Refresh elph-ai chat model catalogs from models.dev (origin) with optional live provider pricing, inject full thinkingLevelMap on every model, regenerate src/models/catalog.rs, and verify registration. Use when the user runs /update-models, asks to sync or regenerate model catalogs, update models.dev data, refresh pricing, or keep provider model lists current.
Interactively create a new Elph skill (SKILL.md + optional scripts/references). Use when the user wants to create a skill, scaffold a skill, or runs /create-skill.
Run make check/lint/test (cargo fmt/check/clippy/test) and fix failures, then audit changed/related Rust code for memory/resource leaks, deadlock risk, data races, and structural complexity (spaghetti code, god functions/modules, tangled control flow). Also audits Turso/libSQL/SQLite usage for lock contention (SQLITE_BUSY/"database is locked"), WAL/checkpoint misconfig, connection/pool misuse, embedded-replica sync issues, and corruption risk. Use when user asks to verify build quality gates, prep Rust code for merge/release, audit concurrency/memory safety, clean up messy/spaghetti Rust code, or check a Rust service using Turso/libSQL for locking/corruption/sync problems. Consult current Rust docs (rust-lang.org, docs.rs) and lint guidance, plus Turso/libSQL docs (docs.turso.tech) when relevant, to ensure fixes align with active best practices, not deprecated patterns. Flags backward-compat/legacy code and structural refactors found during cleanup and asks the user before removing/restructuring.
Analyze pi → elph porting gaps and Elph-specific implementation differences. Compare upstream pi-ai / pi-agent-core CHANGELOGs and source against elph-ai / elph-agent: (1) what upstream has that elph still lacks, (2) how Elph-only features diverge in design and wiring. Porting doctrine: adopt only true gaps (intent/behavior from pi), implement on Elph architecture — catalogs are models.dev via update-models, never pi seed. Prefer reverse-chronological timeline prose over tables. Persisted docs are always English; in-chat reports follow the user's current language. Use for port gap audit, upstream drift, parity check, Elph extension diff, implementation delta, changelog walk, selisih implementasi, or /pi-port-gap.
Guide terminal UI development with iocraft (components, flex layout, scroll, a11y) and CLI/slash command UX: anstyle coloring, readable structured output, TTY/NO_COLOR rules, and dialog-safe plain text. Use when building or refactoring a TUI, CLI subcommands, slash commands, colored terminal output, fixing scroll/focus/layout bugs, improving keyboard/contrast ergonomics, or the user mentions iocraft, terminal UI, CLI colors, anstyle, command UX, accessibility, a11y, or runs /tui-design.
Audit a Rust workspace for dependency hygiene: duplicate crate versions across members, unused/dead dependencies, feature-flag bloat, and un-unified workspace dependency tables. Proposes and safely applies fixes (unify to [workspace.dependencies], drop unused deps, trim feature sets), verifying cargo check/clippy/test stay green. Use when user asks to clean up Cargo.toml(s), dedupe dependency versions, find unused crates, unify workspace deps, or audit workspace dependency structure. Does not cover security advisories or license compliance — see rust-dep-audit for that.
| name | test-agent-tools |
| description | Probe, test, and document every tool the agent harness has access to (native tools, subagents, connected MCP servers). Use when the user wants to test, audit, or inventory the harness's tool/capability set, or asks "what tools do you have". |
Enumerate available tools/capabilities — including connected MCP servers — exercise each one (web search, subagents, MCP calls), and produce a final report with a status table + subagent summary, under a timestamped demo/ run folder.
demo/YYMMDD_hhmm (current date/time).demo/YYMMDD_hhmm/.demo/YYMMDD_hhmm/<subagent_id_or_name>/findings.md.demo/YYMMDD_hhmm/REPORT.md:
| Tool | Type (native/MCP/subagent) | Status (OK/FAIL/SKIPPED) | Notes |REPORT.md directly in the chat reply (not just a file link) — including the tool status table and the subagent summary. If subagents produced findings, include their key results inline too, not just a reference to the file.
REPORT.md, findings, etc.) stay in English regardless of chat language.demo/.demo/.demo/YYMMDD_hhmm (current date/time, no suffix/label).demo/YYMMDD_hhmm/.demo/YYMMDD_hhmm/<subagent_id_or_name>/.REPORT.md always lives flat at demo/YYMMDD_hhmm/REPORT.md, never inside a subagent folder.demo/260731_1420/mcp-github/findings.md or demo/260731_1420/findings.mddemo/260731_1420/web-search-agent/findings.mddemo/260731_1420/REPORT.md