Explorar skills

Short-form comparison post (X / LinkedIn / Threads). Two things contrasted to reveal a non-obvious preference. Use when the user wants to publish an "X vs Y" take — tools, approaches, mindsets, frameworks — and stake a side. Pairs well after a hot-take or how-to long-form piece.

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.

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.

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

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.

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

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).

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.

Short-form (X / LinkedIn) comparison of how something is done today vs how it will be done in 1–5 years. Strong for tech / AI / tooling takes. Use when the user wants to frame a directional bet, a tooling shift, or an obsolescence call — anything where the punchline is "this is the present; here's the future".

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.

stakiran の GitHub Gists を取得し docs/ に静的サイト用 Markdown を生成する