pi-skills

Audit a directory of skills for visibility, deterministic vs non-deterministic behavior, and composability. Use when the user wants to review, assess, or improve a skill collection. Produces a structured report with per-skill ratings and cross-cutting findings.

Instructions for a simplification turn injected by pi-skills' code-simplifier extension. Use when code has been edited or written and needs cleanup, or when the user asks to simplify/refactor recently modified code. Do not invoke as a task subagent; apply these instructions inline in the active agent turn, or via the /simplify extension command.

Automatically augment a skill after it produces friction, misunderstandings, or back-and-forth correction. Invoke after a rough interaction with any skill using phrases like "that was painful," "fix that skill," "don't make me explain that again," "that skill misunderstood me," or /skill:lessons-learned. Reads the current session context, identifies the root cause, and surgically edits the target skill's SKILL.md so future invocations incorporate the correction without manual user intervention.

Create a rich, self-contained HTML visualization of an implementation plan. Invoke whenever the user asks to visualize a plan, create a plan overview, make an implementation plan visual, "show me the plan," "plan as HTML," or any request to turn a project plan, roadmap, or architecture into a visual artifact. Also trigger when the user mentions wanting mock-ups, code excerpts, or maximum context about a plan in a single viewable file. Also trigger automatically after a plan is created, saved, or just written (e.g., after `writing-plans` produces a plan file). This skill gathers plan content from conversation or files and produces a styled HTML file with sections for overview, phases, architecture, code/mock-ups, dependencies, risks, and success criteria, then opens it in a browser window using the `browser` tool (requires a graphical environment; falls back to reporting the file path).

Create effective technical presentations with Slidev, focused on data science, statistics, and developer talks. Opinionated toward the neversink theme with the-unnamed as an alternative. Use when the user wants to build, edit, review, or export slide decks. Covers Slidev syntax, neversink/the-unnamed theme features, visual design principles, storytelling structure, and export workflows.

Plan and review work on a daily and weekly cadence using a small prioritized task slate (inspired by the Ivy Lee method) with Todoist time-blocking. Use when the user asks to "plan my day/tomorrow", "time block my tasks", wants a "nightly review", a "weekly review" or "weekly planning" (Fri afternoon through Sun evening), or wants to clean up incomplete tasks from a finished day or week. Provides plan_day (proposes up to six ordered tasks fitted around existing calendar events and writes them back as timed Todoist tasks), nightly_review (reconciles completions, reschedules or un-dates incomplete items), and weekly_review (light retrospective + stalled-project sweep + per-day soft schedule for the coming week via date-only Todoist dates). Depends on the `todoist-api` skill (td CLI) and the `gws-calendar` MCP tools.