Explorar skills

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.

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.

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.

Audit and remove stale, renamed, or duplicate skills across all installed agent platforms (Claude Code, Kiro, Codex, Windsurf, Gemini, Pi, and more). Handles symlink and copy installs, detects artifacts, and generates OS-correct removal commands. Use when skills list feels cluttered, after renaming a skill, after uninstalling a plugin, or when user says "clean up skills", "remove old skill", "prun

Core principles for technical communication such as commits, PR descriptions, branch names, and technical documentation. Use when writing or refining engineering-facing messaging and when other skills need a shared communication baseline.

Use when drafting, saving, formatting, validating, or repairing LinkedIn profile and content assets in this repository, including headlines, About sections, Experience descriptions, project copy, posts, articles, and LinkedIn image specs.

Push a development branch and create or update a pull request via gh CLI using type-specific templates. Optionally updates README, docs, and project tracking before opening the PR. Use after finishing development, when ready to open a PR, submit work for review, or push changes.

Use when creating a new pulse skill, editing an existing pulse skill, or verifying a skill works under pressure before deploying. Use when you need an agent skill to be bulletproof against rationalization. Do NOT use for project-specific AGENTS.md conventions or one-off solutions.

Use when repository documentation is stale and the user asks to refresh docs to match the current codebase and workflows.

Verify implementation plans before execution using a 4-agent pipeline. Use when you have a written plan (from /bdk:create-plan or manual) and want to check if it will actually work before writing code.

Use when existing architecture documentation needs refreshing after code changes, when running periodic doc maintenance, or when user asks to "update docs", "refresh documentation", or "sync docs with code".

Rules for writing and updating documentation. Use for any non-trivial documentation task in README.md, markdown files, text files, and code comments.