Explore skills
66,821 skills found
write-publish
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).
writing-style
The shared style guide every long-form and short-form post inherits. Reference for tone, structure, sentence rhythm, signature moves, and anti-patterns. Always loaded by drafting and editing skills. This is the only skill that should be personalized — every other skill stays format-only.
debut
Audit a personal open-source repo for public-readiness before going public or pushing to its public git history — secrets/PII in history, licensing, README & community-health files, code quality, tests/CI, deps & releases. Produces a scored report (SHIP IT / NEEDS POLISH / NOT READY) with exact fix commands. Use when: '/debut', 'is this repo ready to go public', 'oss readiness audit', 'public-read
util-review
Review Claude Code skills, hooks, CLAUDE.md files, scripts, or workflow configurations for design flaws, unclosed loops, stale references, side effects, security risks, and portability issues. Use when: 'review this skill', 'audit this hook', '/util-review', 'check this config', or when evaluating any supplementary Claude Code artifact for quality and correctness.
perspective
Strategic reality check for any project. Researches whether the solution already exists, whether there are better approaches, and whether the codebase follows current best practices — using live documentation, not stale training data. Use this skill when the user says 'perspective', 'am I on the right track?', 'is there a better way?', 'has someone already built this?', 'reality check', or any req
plan-challenger
Stress-test and improve implementation plans before execution. Researches alternatives, challenges complexity, checks modularity and feasibility, then delivers a full revised plan. Use whenever the user has a plan — any format (PLAN.md, inline, pasted, attached) — and wants it reviewed before starting. Trigger on 'review this plan', 'challenge this plan', 'stress test', 'is this plan good', 'befor
verify
Audits Claude's own output against the user's original request in the current session — did Claude do exactly what was asked, no more, no less? Checks requirements, styles, constraints, and flags scope creep (extras the user never asked for). Use when the user says "verify", "check your work", "did you follow my request", "audit this", "compliance check", or questions whether Claude improvised, mi
website-audit
Audits any website for SEO, AEO (Answer Engine Optimization), GEO (Generative Engine Optimization), and Structured Data. Crawls with Playwright, runs Lighthouse, checks Perplexity citations, applies research-backed rules, scores deterministically, and produces a prioritised fix list with letter grades. Use this skill whenever the user mentions a domain or URL and wants to know what's wrong with it
long-form-monthly-devlog
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.
long-form-weekly-newsletter
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.
review
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-carousel-li
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.