phall1

Surface the current Claude Code feature surface and report what's new since the last invocation. Run when the user types `/discover` or asks about enabled hooks, MCP servers, experimental flags, skills, agents, or "what's new in my setup".

Read yourself into an unfamiliar repo at the start of a session. Detects stack, conventions, in-flight work, and surfaces a concise orientation summary. Read-only; never writes files or runs destructive commands.

Create, iterate on, and manage custom OpenCode agents

Interact with Linear project management via CLI

steve-jobs ify the ui

An example skill to use as a template. Rename the directory and customize.

Drive persistent, interactive terminal sessions via the phux CLI instead of one-off shells. Use when work needs session state across steps (a long-lived shell, a REPL, an activated venv, a running dev server), an interactive/TUI program (installer prompts, gdb, vim, ssh password), or watching a long-running process — i.e. anything a stateless one-shot `bash` call handles badly.

Wrap the phux CLI as a programmable terminal-control surface for an agent — enumerate sessions, read panes, send input, and run commands using the stable --json contracts and exit-code mirroring. Use when you are scripting phux from another program/agent and need machine-parseable I/O and a read+act+wait loop, rather than the prose "when to use phux" guidance.

Use phux persistent terminals from Pi. Prefer this skill when work should survive across turns, be inspectable with structured snapshots, or be shared with a human tmux-style attach.

Launch relentless, evidence-backed research runs with pi-subagents. Use when the user wants to "find shit out", locate needles in haystacks, investigate companies/repos/tools/people/APIs, answer scattered landscape questions, or kick off background research they can check/resume later.

Discovery skill for the Native SDK, the complete toolkit for building native desktop applications - views are declarative Native markup (.native), logic is plain Zig, and the toolkit's own engine renders every pixel, with WebView surfaces as the optional web-content path. Use when the user asks what the Native SDK is, how to build a Native SDK app, author native UI, scaffold an app, configure app.zon, add bridge commands, embed web content, package an app, test a running app, or automate a Native SDK app.