Explore skills

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.

Monthly devlog — longer, more reflective recap. ~1200-2000 words. Stitches together the month's work, names the pattern, draws a non-obvious lesson. Goes deeper than a weekly recap.

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.

Voice deltas for short-form (X, LinkedIn, Threads). Inherits writing-style and overrides specific rules where short-form requires it. Always loaded by short-form skills.

Run a pre-mortem analysis to identify ways a product initiative could fail before it launches. Use this skill when a team wants to proactively surface failure modes and plan mitigations before committing to execution.

Comprehensive Claude Code plugin for yFiles for HTML development - includes skills for initialization, graph building, layouts, custom styling, and interactive features

Search indexed documents (PDF, Word, Excel, PPT, TXT) using BM25 keyword search. Use for EDA tools, company docs, bug reports, and technical documentation.

Manages the writing cadence using per-ISO-week directories under scribetronic/calendar/. Combines recurring rules + per-week plan.md + history. Subcommands: show, plan-week, add, skip, done, rules. Used by /write router and /write-publish.

Detection pass for AI-generated patterns and clichés. Final check before publishing. Returns a list of detected issues with severity and fix suggestions.

Contrarian opinion piece (~800-1500 words). Stakes a position against conventional wisdom in your niche. Use when you have a real fight to pick — a widely-held belief in your space that you genuinely disagree with and can defend with evidence.

Actionable guide (~1500-3500 words). Teaches the reader to do something specific you've actually done end-to-end. Use when you've completed a process, project, or workflow worth teaching — and you can ship a worked example, not just theory.

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.