Explore skills

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

Short-form post (X single / LinkedIn / Threads) stating a single observation. No list, no contrast — just one thing noticed clearly and named. Use when the user has a one-line insight, pattern, or quiet contrarian take that doesn't need scaffolding to land.

Derives an X thread (and optionally LinkedIn post + Threads post) from a long-form piece. Repurposing engine — chops one published long-form into 2-4 short-form derivatives so the writing system stays sustainable. Use after a long-form is drafted (and ideally edited) when you want to extract its substance for social channels.

Use this skill when the owner wants to write, draft, or generate a blog article. Invoke when the user says "write a blog article", "draft a blog post", "create a blog article", "generate a blog post", "write a how-to article", "draft a thought leadership piece", "write a pillar page", or similar requests for long-form web content.

Use this skill when building a new content-production skill for a specific output format. Invoke when the user says "create a new content skill", "build a skill for [format]", "new content skill", "synthesize research into a skill", or "create a [format] skill".

既存の GitHub issue を `issue-create` skill のフォーマットに沿って整理する。タイトルのみで起票された issue や、フォーマット不完全な issue を後から rich plan に仕上げ直したい場合に使用する。

Ask clarifying questions in rounds until the task is unambiguous, before producing any code, research, or other output. Manually invoked only via slash command. Useful when the cost of getting the work wrong is higher than the cost of a few extra messages. Applies to coding, research, design, writing, refactoring, and analysis.

Checks science files for cross-layer contradictions, inconsistent equations, broken derivation chains, and violations of the universe's foundational axiom. Use when promoting drafts to canon, after writing new science content, after restructuring, or when user says "audit the science", "physics audit", "check for contradictions", "does this break anything", "verify the science", or "cross-layer ch

LinkedIn carousel — multi-slide PDF post (8–10 slides typical). Derives from a long-form piece OR a strong listicle / how-to topic. Use when repurposing a published long-form into LinkedIn's highest-engagement format, or when a user has a step-by-step / numbered insight that benefits from one-idea-per-slide pacing.

Short-form numbered list post for X / LinkedIn / Threads. "X things I learned doing Y", "X mistakes that cost me Z", "X principles for Z". Use when the user has a small set (3–10) of crisp, parallel points worth shipping as a standalone short-form piece — or when distilling a how-to / launch-retro long-form into a list.

Master writing skill. Orchestrates the full pipeline (seed → draft → edit → slop-check → optional repurpose) for any post type — long-form (long-form-weekly-newsletter, long-form-monthly-devlog, long-form-hot-take, long-form-how-to, long-form-launch-retro, long-form-manifesto) or short-form (short-form-x-vs-y, short-form-listicle, short-form-observation, short-form-motivational, short-form-present