Explorar skills

Process status/needs-triage items through the full pipeline: sort (reject/dedup), spec (brainstorming + writing-plans for M/L/XL items), score against the agent-ready checklist, and promote to status/ready (with owner/ai or owner/human) or reject to out-of-scope. Interactive — you confirm every decision. Trigger: "triage", "process backlog", "review incoming items", "spec items", or /pm:triage.

Deep-dive research and analysis of external reference materials (YouTube videos, articles, GitHub repos, documentation, code sources) against the current project. Reads pulse-config.yaml for config. Reports save to {research_dir}/deep-dives/. ONLY trigger when the user explicitly asks to research, analyze, or compare a resource against their project — not just because they share a link. Trigger: "

Content and distribution strategy generator for bootstrapped founders. Produces content pillars, 15 specific content ideas with titles, 20 SEO keywords, a 90-day content calendar, channel-specific tactics, and a distribution checklist. Use when user runs `/content-strategy`, asks about "content strategy", "what should I write about", "blog topics", "SEO keywords", "content calendar", "content mark

Positioning and pitch copy generator for bootstrapped founders. Produces ready-to-paste copy — positioning canvas, one-liner, elevator pitch, homepage hero copy, value propositions, taglines, cold email opener, and language bank. NOT analysis — usable marketing artifacts. Use when user runs `/positioning`, asks about "positioning", "value proposition", "elevator pitch", "tagline", "homepage copy",

Norwegian plain language (klarspråk) guidelines from Språkrådet. Use when writing Norwegian website copy, marketing text, UI labels, documentation, or any user-facing Norwegian content. Triggers on Norwegian text, norsk tekst, klarspråk, markedsføring, nettsidetekst, brukergrensesnitt, or when reviewing/improving Norwegian copy quality.

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.

Critical editorial analysis of articles. Examines structure, argument strength, relevance, and readability. Use for substantive editing - challenging what's said and how, not just polish.

Introduces the scribetronic project layout, CLI, and skills to AI agents working ON this codebase.

Read-and-revise pass for any drafted post. Applies writing-style.md checklist, tightens prose, kills filler. Run after drafting and before ai-slop-check.

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.

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.