Explore skills

Invoke for any request to create, file, open, or record a new GitHub issue. Trigger on:\n- Direct creation: 「issue 作って」「起票して」「issue 立て(といて)」「issue 化して」「issue 作れる?」\n- Record intent: 「issue に残したい/残しておいてほしい」「issue として残しておきたい」\n- Issue types: bug reports (with repro steps), feature requests, refactoring tasks, doc fixes, code-review findings to track later\n\nDo NOT trigger for viewing, listing, sear

Strategy evaluation and design framework based on Richard Rumelt''s "Good Strategy Bad Strategy" and Michael Porter''s "What Is Strategy?". Use this skill whenever the user is discussing strategy, plans, priorities, vision, roadmaps, OKRs, or competitive positioning — even if they do not explicitly say "good strategy", "Rumelt", "Porter", or "strategy kernel". Triggers include: (1) evaluating whet

Post-launch breakdown (~800-1500 words). What you shipped, the numbers (good or bad), what worked, what didn't, what you'd change next time. Use after every product/launch/release where you have real numbers to share — including (especially) when the numbers are embarrassing.

Vision/strategy piece (~1500-3000 words). Rare format — once or twice a year. Names what you're building, why it matters, and how you'll get there. Use to plant a flag, reset direction, or invite people into a longer-term mission.

Publishes a `status: ready` draft from the weekly calendar to its configured target (Astro blog collection) and archives social derivatives. Reads scribetronic/publish-config.yaml. Updates calendar history and per-week plan. Optionally archives completed weeks. Does NOT push to social platforms (out of scope v1).

Detects framework, finds available ports, and starts dev servers with correct port flags. Resolves port conflicts when multiple projects compete for the same default port (common with git worktrees). Scans running processes, identifies frameworks from config files, and uses the right CLI flag per framework. Use when starting dev server, port conflict, port in use, address already in use, EADDRINUS

Derives social and coordination structures from a species' biology, cognition, and environment rather than starting from a template of expected institutions. Works for any species — alien civilizations derive non-human structures; human civilizations in novel environments derive structures that may differ from any Earth precedent. Triggers on "derive social systems", "what structures emerge", "how

Create single-file horizontal HTML presentation decks with rich visual style. Use when the user asks for a web PPT, HTML slides, magazine-style deck, Swiss-style deck, horizontal swipe deck, or a shareable presentation that should open directly in a browser. Use office-pptx instead when the requested final artifact is a native PowerPoint .pptx file.

Navigate repo-specific wiki protocols, code-index maps, and agent update rules. Use when Codex needs to work in a repository that has `wiki/index.md`, `wiki/code-index/`, `AGENTS.md`, or `CLAUDE.md`; when creating, updating, or following wiki specs/plans; when creating or maintaining nested code indexes; when deciding which project files to read before code changes; or when updating agent-facing p

Use this skill when creating or redesigning a GitHub profile README and pinned-project strategy so the profile communicates credibility, project taste, current focus, writing, and practical authority without sounding arrogant or exposing private employer work.

Weekly newsletter — the parent piece of the week. ~600-1200 words. Drafted Sunday. Spawns 5-7 derivative short-form pieces for X / LinkedIn / Threads via /write Phase 5. The recurring Sunday default.

Parallel review of a draft along multiple focuses (voice, structure, slop, hook, closer, optional factual). Spawns N subagents concurrently — each with a single focus and the user's writing-style — then aggregates findings into one severity-grouped report. Use full mode mid-draft or as a pre-publish gate; use delta mode (--since-last / --since <ref>) to review only what changed since the last snap