Claude Skills by viktorbezdek

Authoritative guide to Claude Code hooks — event-driven scripts that execute before or after tool calls, session events, file changes, and more. Use when writing a PreToolUse hook to block dangerous commands, a PostToolUse hook to auto-format after edits, a SessionStart hook to inject context, a Stop hook for session loops, a Notification hook for desktop alerts, a FileChanged hook for reactive environments, a WorktreeCreate hook for custom worktree provisioning, or current documented hook ev...

Turns a vague "I want to build a Claude plugin" into a concrete, problem-first plugin idea — or tells you to not build it. Use when you want to build a Claude plugin, have an idea for a plugin and don't know if it's worth pursuing, are asking "should I build this as a plugin or is there already one", are exploring plugin ideas for your team, or are mining your workflow for repeatable pain points that could become plugins. Covers pain-point mining (what workflow pains become plugins), the prob...

Validates a plugin idea by surveying the marketplace, reading authoritative Anthropic sources, and deciding build-vs-fork-vs-skip before writing any code. Use when you want to research existing Claude Code plugins, check whether there is already a plugin for X, decide whether to build a new plugin or fork an existing one, run a marketplace survey before starting work, find authoritative documentation on a Claude Code feature, or gather primary sources for a plugin design. Covers the marketpla...

Validates the structural correctness of Claude Code plugins — plugin.json manifest fields, SKILL.md YAML frontmatter, reference cross-references, skill name-to-directory consistency, and plugin structure conventions. Use when checking whether a plugin is well-formed before shipping, when debugging "plugin won't load" errors, when setting up CI for a plugin repo, or when reviewing a third-party plugin for issues. NOT for functional evaluation (whether skills activate or produce correct output ...

Apply RICE, MoSCoW, ICE, and effort-impact frameworks to rank options and decide what to work on next. Use when the user asks to prioritize a backlog, rank features, decide what to build first, apply RICE or MoSCoW scoring, cut scope, or compare items by effort vs impact. NOT for defining success metrics or OKRs (use outcome-orientation). NOT for making a strategic bet under uncertainty (use strategic-decision workflow).

Apply outcome-over-output product thinking — separating what gets built from what actually changes for the user, running the "so what" test to climb from output to outcome to impact, choosing leading vs lagging metrics, and identifying a North Star metric. Use when the user asks whether something is an outcome or an output in a product context, wants to run the "so what" test on a deliverable, wants a North Star metric, needs to choose leading indicators for a product bet, or is debating whet...

Frame the real user or business problem (not a code/test bug) using Jobs-To-Be-Done, the 5-whys ladder, and problem-vs-symptom separation. Use when the user asks "are we solving the right problem", wants to write a problem statement, needs to separate problems from symptoms, wants to apply 5-whys to a product or organizational issue, suspects a brief conflates a feature with a problem, or wants to surface assumptions about what problem is actually being solved. NOT for ideating or brainstormi...

Analyze trade-offs between competing product options using cost-benefit, opportunity cost, reversibility (one-way vs two-way doors), and second-order effects. Use when the user faces a product choice with non-trivial trade-offs, asks "what are we giving up", weighs short-term vs long-term impact, or needs to frame a decision before committing. NOT for scored prioritization of a backlog (use prioritization). NOT for quantified risk assessment (use risk-management). NOT for strategic go/no-go (...

Identify what users actually need using functional/emotional/social jobs, needs-vs-wants laddering, latent-need surfacing, and job statements. Use when the user asks what users truly need, wants to write a job statement (When/I-want-to/So-I-can), wants to move past stated wants to underlying needs, needs to separate functional jobs from emotional or social ones, or wants to spot latent needs the user cannot articulate. NOT for persona demographics (use persona-definition). NOT for stakeholder...

Design a product value proposition using the Value Proposition Canvas (jobs, pains, gains, pain relievers, gain creators) and the Kano model. Use when the user asks to write a value proposition, map pains and gains to product features, apply VPC, distinguish basic/performance/delighter features (Kano), or articulate why a product matters to a specific customer. NOT for marketing copy or microcopy (use ux-writing). NOT for pitching the value prop to stakeholders (use storytelling-for-stakehold...

Design, evaluate, and iteratively improve prompts for LLMs — system prompts, few-shot examples, reasoning structures, and instruction templates. Use when the user asks to improve a prompt, write a system prompt, optimize LLM instructions, reduce hallucinations through prompt structure, test prompt variants, or apply prompting techniques (structured reasoning, ReAct, few-shot, structured output). NOT for building MCP tools or server implementation (use mcp-server). NOT for creating Claude Code...

Python development — use when the user works with .py files, pyproject.toml, uv, ruff, mypy, pytest, async/await, MicroPython, CLI tools, or PyPI publishing. Covers modern tooling, best practices, library architecture, functional patterns, and production workflows. NOT for TypeScript or JavaScript development (use typescript-development), NOT for React component patterns (use react-development).

React-specific development patterns including hooks (useState, useEffect, useReducer, useContext), component architecture, state management, shadcn/ui integration, JSX/TSX, React testing, and Bulletproof React auditing. NOT for Next.js routing, SSR, or server components (use nextjs-development). NOT for CSS design systems, Tailwind utilities, or accessibility patterns (use frontend-design).

Systematically assess and mitigate risks using risk registers, probability-impact matrices, mitigation strategies, and contingency plans. Use when the user asks to assess risks, build a risk register, plan for failure modes, evaluate downside scenarios, prepare contingency plans, or quantify uncertainty before a decision or launch. NOT for finding conceptual flaws or blind spots in ideas (use critical-intuition). NOT for security vulnerability auditing in code (use code-review). NOT for ident...

Author high-quality Claude Code SKILL.md files using philosophy-first design, evidence-based prompting, progressive disclosure, and anti-pattern prevention. Use when the user asks to write a skill file, create a new Claude Code skill, design a SKILL.md, review whether a skill's description will trigger correctly, or convert a workflow into a reusable skill. NOT for optimizing standalone prompts or system prompts (use prompt-engineering). NOT for full plugin development with hooks and MCP (use...

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction.

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms.

Presentation creation, editing, and analysis for working with .pptx files including layouts, comments, and speaker notes.

Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization.

You need a simple skill that formats JSON output for better readability.

Semantic image-text matching with CLIP and alternatives. Use for image search, zero-shot classification, similarity matching. NOT for counting objects, fine-grained classification (celebrities, car models), spatial reasoning, or compositional queries. Mention CLIP, embeddings, image similarity, or semantic search.

[TODO: Write comprehensive description in third-person. Start with "This skill provides..." or "This skill should be used when..."] [TODO: Add "Use when" scenarios - specific situations where Claude should use this skill] [TODO: Add keywords - technologies, use cases, error messages that should trigger this skill]

End-to-end workflow for taking an API from design through TDD, code review, CI/CD, and containerized deployment. Composes five phases — REST/GraphQL/gRPC design with schemas and error contracts (api-design), red-green-refactor on every endpoint (test-driven-development), multi-perspective code review (code-review), pipeline wiring with automated testing (cicd-pipelines), and Docker containerization with multi-stage builds and optimization (docker-containerization). Use when building a new API...

End-to-end workflow for authoring a Claude Code plugin from idea to validated, evaluated artifact. Composes six phases — ideation with a 7-criteria kill gate (plugin-ideation), marketplace survey and build-vs-fork decision (plugin-research), skill/hook/MCP/subagent/command decomposition (plugin-architecture), component implementation (plugin-hooks + plugin-composition + skill-creator), structural validation (plugin-validation), and trigger plus output evaluation with iteration loop (plugin-ev...

Funnel workflow for going from "I want an agent that does X" to a deployed, evaluated, cost-monitored agent. Runs through nine phases starting with the is-this-task-agent-appropriate check (agent-project-development), then prompt design with eval criteria first (prompt-engineering), tool design and consolidation (tool-design), architecture selection for multi-step work (multi-agent-patterns), persistence decisions (memory-systems), context-window management (context-optimization), evaluation ...

Layering workflow for building a knowledge base, CMS, documentation site, or structured content platform from scratch. Builds the data model first (content-modelling), adds a formal knowledge-graph layer if needed (ontology-design), establishes naming and taxonomy conventions (consistency-standards), designs information architecture (navigation-design), fine-tunes voice and microcopy (ux-writing), fills the structure with examples (example-design), and adds tooling for scale (documentation-ge...

Diagnostic-and-fix pipeline for systematic context engineering — fix agent context, context engineering, context optimization pipeline, diagnose context problems. Chains context-fundamentals (attention, budgeting), context-optimization (KV-cache, partitioning, observation masking), context-compression (summarization, anchored iterative, tokens-per-task), context-degradation (lost-in-middle, poisoning, clash diagnosis), and filesystem-context (scratch pads, plan files, dynamic loading). Use wh...

Loop workflow for debugging a complex issue you've been stuck on for more than 30 minutes. Runs systematic hypothesis formation (debugging skill), feedback-loop mapping when the bug looks like a dynamic problem (systems-thinking), context-pathology check when it's an LLM/agent bug (context-degradation), blast-radius assessment before any fix attempt (risk-management), and uses test-driven-development as the debugging oracle — write a failing test that reproduces the bug, then iterate fix → te...

Sequential-audit workflow for running a full UX review pass across an application or product. Walks through five phases — visual audit of design system adherence (frontend-design), navigation and information architecture review (navigation-design), microcopy and error-message audit (ux-writing), end-to-end journey validation (user-journey-design), and cross-product consistency check (consistency-standards). Use when launching a new product version, onboarding a design system, preparing for an...

Diagnostic-loop workflow for improving an underperforming AI agent. Starts with baseline measurement using rubrics and LLM-as-judge scoring (agent-evaluation), then diagnoses architectural problems like task-model mismatch and pipeline bottlenecks (agent-project-development), redesigns the agent topology — supervisor, swarm, or specialized agents (multi-agent-patterns), adds the right memory framework when persistence is the gap (memory-systems), and re-evaluates against the original baseline...

Use when evaluating a Claude Code plugin or single SKILL.md and a verdict is needed — ship-ready, needs improvement, or rework. Multi-pass audit workflow that composes plugin-dev's structural validation, plugin-evaluation's activation and output measurement, and skill-foundry's anti-pattern audit to grade quality across five dimensions: structure, activation reliability, content discipline, output behavior, and documentation completeness. Trigger phrases include "evaluate this plugin", "revie...

Loop workflow for making real progress on a legacy codebase without breaking production. Starts by generating a codemap so you actually understand what exists (documentation-generator), identifies feedback-center modules (systems-thinking), gets a second perspective on areas you'll touch (code-review), builds a test safety net before any changes (test-driven-development), plans changes with rollback options (risk-management), makes small atomic commits (git-workflow), and loops through debugg...

Funnel-with-gate workflow for reducing LLM costs without degrading quality. Starts with diagnosing the cost surface using cloud-finops (specifically the finops-for-ai and finops-anthropic references), then applies context-optimization to reduce context per call, context-compression to compress what can't be reduced, prompt-engineering for shorter prompts and better model selection, and uses agent-evaluation as a mandatory gate — if any optimization degrades quality, roll it back. Finishes wit...

Ramp-up workflow for understanding a new codebase fast — onboard to codebase, understand a repo, grok a project, ramp up on code. Generates a codemap so the structure is visible before you read any implementation (documentation-generator), then builds a system model of dependencies, feedback loops, and critical paths so you know which parts matter (systems-thinking), then traces key flows end-to-end through the code so you see how the pieces connect in practice (debugging), and finally builds...

Parallel-merge workflow for producing a pitch (investor deck, board proposal, internal funding request, customer sales narrative) in roughly a week. Runs three parallel streams (deep interviews via elicitation, market dynamics via systems-thinking, audience sharpening via persona-definition), merges them into a single storytelling spine, audits via critical-intuition, and polishes every line with ux-writing. Use when you have one week to produce a pitch that must actually land with a specific...

PM funnel workflow for turning user research into prioritized engineering stories — product story, user research to backlog, user needs to stories, PM workflow. Chains elicitation (deep interviews that surface real needs), user-journey-design (touchpoints, pain points, emotions), persona-definition (who we're building for), outcome-orientation (measurable success criteria), and prioritization (RICE/MoSCoW/ICE scoring). Use when translating user research into engineering work, when the backlog...

Systematic security audit workflow for hardening a codebase through structured multi-pass analysis. Composes four skills across five phases — threat surface mapping with attack vector identification (risk-management), security-focused code review targeting OWASP and language-specific vulnerabilities (code-review), boundary condition and validation gap analysis (edge-case-coverage), and security test suite construction with fuzzing and property-based tests (testing-framework). Use when hardeni...

Narrative-build workflow for turning data, technical results, or project outcomes into a compelling story for leadership, investors, or customers. Structures the narrative using proven story frameworks — 3-act, SparkLines, situation-complication-resolution (storytelling), finds the surprising angle through lateral thinking and reframing (creative-problem-solving), anchors every claim to measurable business impact using OKRs and outcome vs output framing (outcome-orientation), then iterates th...

Gate workflow for making a strategic decision under uncertainty when multiple options have merit and the stakes are high. Defines the success criteria first (outcome-orientation), maps what actually drives the outcome (systems-thinking), generates options including uncomfortable ones (creative-problem-solving), stress-tests each for blind spots and hidden assumptions (critical-intuition), assesses downside per option (risk-management), ranks using the original criteria (prioritization), and u...

Workflow for modifying an existing Claude Code plugin — adding a new skill, fixing activation issues, improving content quality, adding hooks, or restructuring components. Composes five phases: audit current state (plugin-validation + plugin-evaluation), classify the change type, implement using the appropriate plugin-dev skills (skill-foundry / plugin-hooks / plugin-composition / plugin-architecture), regression-check via re-validation and re-evaluation, then version bump and README update. ...

Funnel workflow for turning user interviews into actionable product direction that the team actually acts on. Designs the research conversations using elicitation frameworks (OARS, narrative identity, values elicitation, schema detection), synthesizes findings into grounded personas (persona-definition), places them in the organizational landscape (persona-mapping), maps their journeys with touchpoints and friction (user-journey-design), audits for what the research missed (critical-intuition...

Meta-workflow for creating your own Claude Code skill that actually activates when needed and delivers genuine value. Starts with skill-creator as the canonical starting point, adds elicitation frameworks when the skill is for a human/domain area (interviewing, research, therapy-adjacent), designs the examples that will illustrate the skill (example-design), aligns with repo conventions (consistency-standards), writes structural validation tests before the content (test-driven-development), a...

Expert guidance for writing, editing, and teaching stories across fiction, business, data, speech, UX, and interactive narrative. Covers canonical story structures (3-act, Hero's Journey, Story Circle, Save the Cat, Kishōtenketsu, Freytag, Fichtean), business narrative frameworks (StoryBrand, Pixar Spine, Before-After-Bridge), data storytelling (Knaflic, situation-complication-resolution), speech writing (Duarte SparkLines, TED, Monroe's Motivated Sequence), narrative craft (character, scene,...

Analyze complex problems through feedback loops, system dynamics, causal relationships, and leverage points to understand WHY a system behaves the way it does. Use when the user asks to map feedback loops, trace causal chains, identify why a problem keeps recurring, find leverage points for change, analyze emergent behavior, or understand a complex system before intervening. NOT for generating creative solutions (use creative-problem-solving). NOT for stress-testing specific assumptions (use ...

Engineer the distribution layer of a long-form technical article — title, dek (subtitle), meta description, social pull-quotes, and channel-specific framing. Most technical articles die at the title; this skill covers the craft of titles that earn the click without clickbait, deks that confirm the promise, social pull-quotes for X / LinkedIn / Hacker News / Reddit, open-graph metadata, and the practice of reframing the same article differently per channel. Use when the user asks to write a ti...

Apply proven copywriting techniques to long-form technical content so it holds attention from sentence to sentence — and humanize prose that reads AI-generated. Covers AIDA, PAS, Before-After-Bridge, Bencivenga's pyramid, Sugarman's slippery slide, Schwartz's awareness levels, hook engineering, voice and tonality calibration, the concrete-over-abstract discipline, and the AI-prose-tell catalog (banned high-frequency AI words like delve / underscore / pivotal / leverage; AI transitions like "t...

Polish a long-form technical draft for pacing, scan-ability, and tightness. Cover paragraph and sentence rhythm, the scan reader's experience (headings, callouts, pull quotes, white space, lists, tables), the 30% cut discipline for removing filler, and the read-aloud test for finding bumps. Distinct from short-form line-level editing — this skill works at the paragraph and section level for pieces of 1500-5000+ words. Use when the user asks to polish a long article, fix pacing, improve scan-a...

Structure long-form technical articles around the hook → promise → setup → development → payoff contract. Pick from canonical templates (deep-dive, tutorial, opinion, case study, whitepaper, technical narrative). Engineer section transitions and signposting. Match length to ambition (when 800 vs 1500 vs 3000 vs 5000+ words is right). Use when the user asks to outline a technical article, structure a deep-dive, plan a tutorial, organize a whitepaper, pick an article template, fix pacing across...

Research before craft for long-form technical content. Profile the audience (knowledge level, jobs-to-be-done, prior beliefs), tier sources (primary > peer-reviewed > authoritative > popular > vendor), triangulate every load- bearing claim across three sources, manage evidence types (data, expert quotes, demonstrations, case studies, source code), and apply citation discipline (when, how, link-rot mitigation, footnote vs inline). Use when the user asks to research a technical article, profile...

Guides the Test-Driven Development methodology: the Red-Green-Refactor cycle of writing failing tests before implementation code, then making them pass with minimal code, then refactoring. Use when the user asks to do TDD, practice test-driven development, follow red-green-refactor, write tests first, apply test-first methodology, or implement a feature using TDD workflow with pytest, Vitest, ERT, or Zod. NOT for choosing or setting up test frameworks (use testing-framework), NOT for finding ...