#SkillRepo stars
- 1489Code Qualitysam-dumont/claude-skillsAutomatically triggered when setting up Python code quality tooling, configuring linters, adding type checking, improving code standards, running code quality checks, setting up pre-commit hooks, or auditing Python code for quality issues. Applies when discussing: ruff setup, mypy configuration, code formatting, linting rules, cyclomatic complexity, dead code detection, file length limits, pre-commit hooks, Makefile targets for quality, uv-based workflows, pyproject.toml configuration, or "check my code quality". Also triggers on: "set up linting", "add type checking", "configure ruff", "forma38
- 1490Code Walkthroughdariia-m/my_claude_skillsInteractive step-by-step code walkthrough for entire codebases (single or multi-file). Explains each section's logic, assumptions, and data transformations, then RUNS the code and shows actual output - dataframe dimensions, head(), model summaries, plot descriptions, file previews. Pauses after each section for questions. Use whenever the user says "walk through", "explain", "go through", "break down", "review", "understand", "what does this code do", "help me understand this script", "annotate", "explain step by step", or "walk me through the codebase". Also trigger if someone just points at 36
- 1491Commenting Intentobra/clankComment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)43
- 1492Debug to FixElliotJLT/Claude-Skill-PotionsWhen debugging frustration appears ("why isn't this working?", "it should work", "I don't understand"), orchestrate the full debug cycle: clarify → investigate → fix → verify. Prevents the common failure of jumping to fixes before understanding the problem. An elixir that chains rubber-duck and prove-it with investigation.62
- 1493Designing Before Codingobra/clankDesign in pseudocode first, iterate approaches, then translate to code43
- 1494Domain Focused Namingobra/clankName code by what it does in the domain, not how it's implemented or its history43
- 1495Encapsulating Complexityobra/clankHide implementation details behind interfaces - work at domain level (what), not implementation level (how)43
- 1496Exploring Alternativesobra/clankTry 2-3 different approaches before implementing - don't settle for first design you think of43
- 1497Keeping Routines Focusedobra/clankEach routine does one thing and does it well - extract when routines have multiple responsibilities43
- 1498Localizing Variablesobra/clankDeclare variables in smallest possible scope, initialize close to first use, minimize span and live time43
- 1499Maintaining Consistent Abstractionsobra/clankClass interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns43
- 1500Naming Variablesobra/clankChoose names that fully and accurately describe what the variable represents43
- 1501Pair ModeElliotJLT/Claude-Skill-PotionsWhen activated, Claude becomes a pair programming partner rather than a code-generation tool. Explains reasoning, teaches patterns, asks questions that build understanding, and adjusts depth based on the person's goals. Balances getting work done with building lasting knowledge. Activate with "let's pair on this" or by setting a learning focus at session start.62
- 1502Pre MortemElliotJLT/Claude-Skill-PotionsBefore starting ANY significant task (feature build, refactor, integration, migration, or architectural change), first imagine the project has failed. Generate 3-5 specific failure scenarios, assess risk levels, identify mitigations, then adjust the implementation plan to address high-risk items FIRST. Do not start coding until the pre-mortem is acknowledged.62
- 1503Reducing Complexityobra/clankManaging complexity is software's primary technical imperative - all other goals are secondary43
- 1504Refactoring Safelyobra/clankRefactor with tests first, one change at a time, never mix refactoring with bug fixes or new features43
- 1505Requesting Code Reviewobra/clankDispatch code-reviewer subagent to review implementation against plan or requirements before proceeding43
- 1506Safe RefactorElliotJLT/Claude-Skill-PotionsWhen refactoring, rewriting, or migrating critical code paths, orchestrate a safe cycle: assess risks → implement → verify → document. Chains pre-mortem and prove-it with built-in implementation phase. Prevents "refactor broke production" disasters. Activates on "refactor", "rewrite", "migrate", or "clean up" for non-trivial code.62
- 1507Sams Architecturesam-dumont/claude-skillsAutomatically triggered when designing system architecture, planning new projects, creating implementation plans, conducting architecture reviews, or auditing existing codebases for consistency. Applies when discussing: system design, technology choices, architectural patterns, infrastructure decisions, API design, testing strategies, CI/CD pipelines, security architecture, or code organization. Works for Python web APIs, infrastructure/DevOps, Garmin/embedded systems, and frontend projects. Distinguishes between personal projects (strict standards) and client work (adaptive approach).38
- 1508Simplifying Control Flowobra/clankFlatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levels43
- 1509Single Purpose Variablesobra/clankUse each variable for exactly one purpose - no hybrid coupling or hidden meanings43
- 1510Stay in LaneElliotJLT/Claude-Skill-PotionsBefore making changes, verifies they match what was actually requested. Activates when about to modify files, add features, or refactor code. Catches scope creep before it happens - no "while I'm here" improvements.62
- 1511Trace ItElliotJLT/Claude-Skill-PotionsBefore modifying shared code (utilities, types, configs, base classes), traces all callers and dependents first. Activates when editing files in shared/, utils/, lib/, or anything imported by 3+ files. Prevents "fixed one thing, broke three others.62
- 1512Validating Inputsobra/clankCheck all external inputs for validity - garbage in, nothing out, never garbage out43
- 1513Zero inElliotJLT/Claude-Skill-PotionsBefore searching a codebase, forces you to zero in on the target: what exactly are you looking for, what would it look like, where would it live, what else might it be called. Activates on "find", "where is", "search for", or when exploration begins. Prevents grep-and-pray.62
- 1514Client CompatibilityAzure-Samples/agent-skills-dotnet-demoPlatform detection and adaptive spawning for CLI vs VS Code vs other surfaces45
- 1515Code ReviewerAzure-Samples/agent-skills-dotnet-demoReview code for best practices, potential bugs, and improvements. Use when asked to review, analyze, or critique code quality.45
- 1516Debug Replayamplitude/mcp-marketplaceTurns bug reports into reproducible steps by finding error sessions in Amplitude Session Replay, extracting interaction timelines, and identifying the common action sequence that precedes the failure. Use when a user reports a bug, an error event spikes, someone says "how do I reproduce this", "what happened to user X", "repro steps", or you need to understand what a user did before an error occurred.48
- 1517Debugging with Evidenceokgrit/done-is-a-claimDiagnose unexpected behavior with a reproduction, competing explanations and experiments that separate them before fixing. Use for bugs, failed checks or repeated unsuccessful fixes; attribute branch failures only with suitable comparison evidence.33
- 1518Nist Csfscytale-labs/GRC-Claude-SkillsUse when the user asks about NIST Cybersecurity Framework — the CSF 2.0 six Functions (Govern, Identify, Protect, Detect, Respond, Recover), Categories and Subcategories, Implementation Tiers (1–4), Profiles (Current and Target), Organizational Profile, or using CSF as a structuring lens for a security program. Voluntary framework — useful for any sector, often paired with sector-specific regulation.33
- 1519Squad ConventionsAzure-Samples/agent-skills-dotnet-demoCore conventions and patterns used in the Squad codebase45
- 1520Typescript Advanced Types0xranx/agentbriefMaster TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.43
- 1521Architecturekorchard333/claude-power-platform-communityPower Platform Solution Architecture. Use when: selecting app type (Code App vs Canvas vs Model-Driven), designing solution structure, environment strategy, integration patterns, security architecture, DLP policies, capacity planning, Architecture Decision Records (ADRs).52
- 1522Ascii Art Beautifiermiolamio/claude-skillsBeautifies and generates ASCII art diagrams in markdown files. Use when user says "beautify ascii", "fix ascii art", "align ascii", "выровняй разметку", "причеши ascii", "сделай разметку ровной", "fix diagram", "clean up ascii", or points to a markdown file with messy ASCII art in code blocks. Also generates new clean ASCII art from text descriptions when asked.35
- 1523Code Appskorchard333/claude-power-platform-communityPower Apps Code Apps Development (React + TypeScript + Vite). Use when: building Code Apps, three-layer architecture, PAC CLI workflow, Zustand state management, TanStack Query, shadcn/ui components, router basename, provider stack, form patterns, Dataverse integration from React.52
- 1524Code Reviewerkorchard333/claude-power-platform-communityPower Platform Critic and Quality Reviewer (Razor). Use when: reviewing architecture, reviewing code, code review, accessibility audit, WCAG compliance check, UX review, ALM review, Dataverse schema review, Power Automate review, Canvas App review, security review. Provides severity-rated findings (S1-S4). Trigger when user says "review this", "check this code", "audit", "is this architecture solid", or after any significant implementation is complete.52
- 1525Dataverse Web APIkorchard333/claude-power-platform-communityDataverse Web API reference. Use when: CRUD operations, OData queries, FetchXML, bulk operations, batch requests, metadata operations, Custom APIs, file/image columns, change tracking, solution management via API, schema creation, programmatic builds.52
- 1526Env Strategykorchard333/claude-power-platform-communityPower Platform environment strategy and topology. Use when: environment types, developer environments, sandbox, production, environment groups, environment routing, naming conventions, environment provisioning, environment topology, Managed Environments, environment lifecycle, multi-geo, environment variables across environments.52
- 1527Licensingkorchard333/claude-power-platform-communityPower Platform licensing and cost optimization. Use when: license types, per user, per app, pay-as-you-go, premium, Copilot Studio licensing, Power Automate licensing, AI Builder credits, Copilot Credits, Managed Environments licensing, capacity, API request limits, cost optimization, feature-to-license mapping.52
- 1528Perf Optimisekorchard333/claude-power-platform-communityPower Platform performance optimization. Use when: performance, slow, optimization, delegation, caching, indexing, query performance, API limits, throttling, virtual scrolling, lazy loading, concurrent, batch operations, form load.52
- 1529Power Bikorchard333/claude-power-platform-communityPower BI Development. Use when: building reports, TMDL semantic models, DAX patterns, PBIR report definitions, Fabric REST API, Direct Lake, incremental refresh, Dataverse as data source, Power BI Embedded in Code Apps, CI/CD for Power BI.52
- 1530Telegram CLImiolamio/claude-skillsInteract with Telegram directly from Claude Code - send/read messages, manage chats, search conversations, download media, manage contacts, and automate Telegram workflows. Use when the user needs to send a Telegram message, read chat history, search messages, manage groups/channels, download or upload media, work with contacts, or perform any Telegram operation.35
- 1531Web Resourceskorchard333/claude-power-platform-communityDataverse Web Resources (JavaScript/HTML). Use when: writing form scripts, Xrm Client API, formContext patterns, HTML web resources, ribbon/command bar customization, RibbonDiffXml, web resource deployment, event handlers.52
- 1532Architecture Strategistratacat/claude-skillsUse this agent when you need to analyze code changes from an architectural perspective, evaluate system design decisions, or ensure that modifications align with established architectural patterns. This includes reviewing pull requests for architectural compliance, assessing the impact of new features on system structure, or validating that changes maintain proper component boundaries and design principles. <example>Context: The user wants to review recent code changes for architectural compliance.\ user: "I just refactored the authentication service to use a new pattern"\ assistant: "I'll use59
- 1533Beautiful Mermaid Asciiratacat/claude-skillsRender Mermaid diagrams as readable ASCII/Unicode art in the terminal (from .mmd/.mermaid files, stdin, or Markdown ```mermaid fences). Use when installing or using lukilabs/beautiful-mermaid, creating a CLI renderer for Mermaid-to-ASCII output, previewing Mermaid diagrams in terminal, or extracting/rendering Mermaid blocks from Markdown files.59
- 1534Clean Coderatacat/claude-skillsUse when writing, reviewing, or refactoring code. Apply when naming variables or functions, structuring classes, handling errors, writing tests, or when code feels complex or hard to understand. Based on Robert C. Martin's Clean Code.59
- 1535Code Simplicity Reviewerratacat/claude-skillsUse this agent when you need a final review pass to ensure code changes are as simple and minimal as possible. This agent should be invoked after implementation is complete but before finalizing changes, to identify opportunities for simplification, remove unnecessary complexity, and ensure adherence to YAGNI principles. Examples: <example>Context: The user has just implemented a new feature and wants to ensure it's as simple as possible. user: "I've finished implementing the user authentication system" assistant: "Great! Let me review the implementation for simplicity and minimalism using the59
- 1536Data Systems Architectureratacat/claude-skillsUse when designing databases for data-heavy applications, making schema decisions for performance, choosing between normalization and denormalization, selecting storage/indexing strategies, planning for scale, or evaluating OLTP vs OLAP trade-offs. Also use when encountering N+1 queries, ORM issues, or concurrency problems.59