#SkillRepo stars
- 1441Bt Node Project DeployaaPanel/btpanel-skills在宝塔面板上部署 Node.js 项目(nodejs/general/pm2 三种类型,含 Nginx 域名/反代), 并在项目启动失败或访问异常时排错。 当用户要求把本机已有的 Node 项目目录部署成面板可管理的项目(含 node 版本、依赖安装、 Nginx 代理/域名、pm2 守护),或 Node 项目启动失败/访问异常需要排查根因时使用。 触发关键词:部署 Node、Node 项目部署、nodejs 部署、npm 项目部署、PM2 部署、 Node 项目启动失败、npm 起不来、Node 报错、502、访问异常、pm2 errored、Cannot find module。 日常的启停/状态/日志/改配置等简单操作不依赖本 SOP,直接按工具描述调用即可。43
- 1442Bt Python Project DeployaaPanel/btpanel-skills在宝塔面板上部署 Python 项目(uwsgi/gunicorn/command 三种运行方式,含虚拟环境配置、 Python 版本安装、requirements 依赖、Nginx 域名/反代),并在环境准备或启动失败时排错。 当用户要求把本机已有的 Python 项目目录部署成面板可管理的项目(含 Python 版本安装、 虚拟环境创建、pip 依赖、uwsgi/gunicorn 托管或自定义命令启动),或 Python 项目 启动失败/访问异常/环境准备失败需要排查根因时使用。 触发关键词:部署 Python、Python 项目部署、django/flask/fastapi/sanic 部署、 uvicorn/gunicorn/uwsgi、虚拟环境 venv、pip install、Python 项目启动失败、 ImportError、ModuleNotFoundError、502、访问异常、celery、关联进程、requirements。 日常的启停/状态/日志/改配置/装包等简单操作不依赖本 SOP,直接按工具描述调用即可。43
- 1443Timovi Backend Engineertheminimalcreator/timoviBackend Engineer for the Timovi project. Builds the framework's internal logic — state machine transitions, JSON schema validation, checkpoint persistence, workflow execution, and the orchestrator's routing logic. Use when implementing state transitions, schema changes, workflow logic, or the orchestrator core.49
- 1444Timovi Software Architecttheminimalcreator/timoviSoftware Architect for the Timovi project. Validates technical feasibility of framework changes, documents architectural decisions, evaluates risks with clear trade-offs. Use when making architectural decisions about the skill framework, evaluating feasibility of new capabilities, analyzing cross-cutting impact, or documenting patterns.49
- 1445Timovi Tech Leadtheminimalcreator/timoviTech Lead for the Timovi project. Technical leadership for architecture, quality, planning, and execution with explicit trade-offs. Use when decomposing features into Issues, reviewing skill code, defining standards, or coordinating technical execution.49
- 1446Code Commentspetekp/claude-code-setupWrite, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.49
- 1447Exhaustive Systems Analysispetekp/claude-code-setupPerform evidence-driven, multi-subsystem audits of real codebases to find correctness bugs, race conditions, security gaps, stale documentation, dead code, and production-readiness risks. Use when asked to audit a system end-to-end, verify agent-written code before shipping, analyze a subsystem for correctness across multiple modules, or produce a structured risk report for a real implementation. Prefer other skills for a single isolated bug, a proposal or document review, or a dedicated dead-code cleanup.49
- 1448Latent Potentialpetekp/claude-code-setupFirst-principles, team-of-experts assessment of a software project that surfaces latent potential; underexploited assets, a sharper north star, missing high-leverage capabilities, better framing and messaging. Produces a prioritized, evidence-grounded report with cheap probes, a reframe candidate, a stop-doing list, and an honest skeptic's case. Use whenever the user wants fresh eyes on a project they have built: "what am I sitting on", "what could this become", "is there a bigger play here", "how do I make this valuable or impactful", "assess this project", "strategic review", "where should t49
- 1449Dayz ModdingStarDZ-Team/Dayz-Modding-SkillsALWAYS use when touching ANY DayZ file (.c, config.cpp, mod.cpp, .layout, types.xml) or discussing DayZ modding, Enforce Script, or the Enfusion engine. Activate even if the user does not explicitly mention DayZ — if the code imports DayZ classes (PlayerBase, EntityAI, ItemBase, MissionServer), uses DayZ APIs (GetGame(), Class.CastTo(), ScriptRPC), or references DayZ patterns (modded class, CfgPatches, requiredAddons), this skill MUST be loaded. Covers 40+ critical gotchas, complete engine API across 20+ systems, mod architecture, RPC networking, GUI widgets, performance optimization, and prof23
- 1450Nuxt Best Practicesvinayakkulkarni/vue-nuxt-best-practicesNuxt 4 performance optimization and architecture guidelines (current through Nuxt 4.5) for building fast, maintainable full-stack applications. This skill should be used when writing, reviewing, or refactoring Nuxt code to ensure optimal patterns. Triggers on tasks involving data fetching, server routes, auto-imports, rendering modes, layouts, named views, or Nuxt-specific features.43
- 1451Skill Installerratacat/claude-skillsInstall Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).59
- 1452Uw Code Reviewdevdavv/unity-ai-workflowPre-commit code quality review for Unity C# code. Checks against Rules, CODING_STANDARDS.md, NAMING_CONVENTIONS.md, and GDD Gherkin test coverage. Use when code has been written and tests are passing but before committing. Runs automatically at Step 8.5 of /uw-cmd-implement-feature. Triggers on "review this code", "check my implementation", "pre-commit review", "code review", "check before commit", "is this ready to commit", "review my changes", or any request to validate code quality before committing.47
- 1453Uw Dependency Injectiondevdavv/unity-ai-workflowOpt-in DI architecture using Reflex for Unity 6+. Covers container setup, scoping, injection, command pattern, update management, and class taxonomy. Use when ProjectConfig.yaml -> architecture_pattern is "di-first", or when the user asks about dependency injection, inversion of control, service architecture, or testable game code. Triggers on "set up DI", "add dependency injection", "create a service", "wire up dependencies", "make this testable", "decouple these systems", "add a command pattern", "cross-feature communication", or architecture discussions involving testability, decoupling, an47
- 1454Uw Unity Debuggingdevdavv/unity-ai-workflowSystematic 4-phase debugging framework for Unity projects with GameDebug wrapper generation. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Triggers on requests like "this doesn't work", "there's a bug", "it crashes when", "fix this error", "why is this happening", "null reference exception", "test is failing", "unexpected behavior", "something broke", or any debugging task. Four-phase framework (gather evidence, isolate, hypothesize, fix) that ensures understanding before attempting solutions.47
- 1455C4 Codebase Architecturelmammino/c4-codebase-architecture-skillHelps an agent inspect a repository and produce C4 architecture documentation. Use this when reverse engineering a codebase, documenting system context, containers, components, or clarifying architecture from code and infrastructure.24
- 1456Code Flow Tracerlis186/SourceAtlasTrace code execution paths and data flow. Use when user asks "how does X work", "what happens when X", "trace the flow of X", "where does data come from", or needs to understand feature implementation.49
- 1457Codebase Overviewlis186/SourceAtlasQuickly understand a new codebase's architecture, tech stack, and patterns. Use when user asks "what is this project", "project overview", "how is this codebase structured", "what tech stack", or when onboarding to a new codebase.49
- 1458Depslis186/SourceAtlasAnalyze dependency usage for library/framework/SDK upgrades49
- 1459History Analyzerlis186/SourceAtlasAnalyze git history for hotspots, coupling, and knowledge distribution. Use when user asks "who knows this code", "what files change most", "hotspots", "bus factor", "knowledge silos", or needs to understand code evolution.49
- 1460Impactlis186/SourceAtlasAnalyze the impact scope of code changes using static dependency analysis49
- 1461Impact Analyzerlis186/SourceAtlasAnalyze what code will be affected by changes. Use when user asks "what will break if I change X", "impact of changing X", "dependencies of X", "is it safe to modify X", or before making significant code changes.49
- 1462Pattern Finderlis186/SourceAtlasFind implementation examples and design patterns in the codebase. Use when user asks "how to implement X", "how does this project do X", "show me examples of X", "where is X implemented", or needs to follow existing code conventions.49
- 1463Cle Metaharvard-lil/lawskills-hubAlways-on assistant for practicing attorneys focused on professional development and continuing education. Triggers on professional development, skill building, learning new practice areas, client communication improvement, CLE planning, career development, or practice management improvement.48
- 1464Daytonadaytona/skillsCreates and manages isolated cloud sandboxes (secure code execution environments with dedicated runtimes) on the Daytona platform, through the SDKs, the CLI, and the REST API. Use when a task needs an isolated runtime, sandbox, secure compute, or Daytona SDK, API, or CLI operations. Covers Daytona v2 (`daytona.v2`, api.daytona.com, Python and TypeScript SDKs) and Daytona v0 (app.daytona.io, Python, TypeScript, Java, Go, and Ruby SDKs).23
- 1465Development Planharvard-lil/lawskills-hubTriggers when a practicing attorney wants to create a professional development plan, set career goals, identify skill gaps, plan their CLE activities for the year, or think strategically about their career trajectory.48
- 1466Feature Lifecycletddworks/claude-skillsFull-lifecycle guide for implementing a feature end-to-end in a London-school DDD Swift/iOS codebase (or any layered Domain/Infrastructure/App project that uses protocol + concrete impl aggregates, narrow infrastructure ports, and Chicago-school state-based TDD). Use this skill whenever the user asks to **build**, **implement**, **add**, **ship**, or **develop** a feature — including vague asks like "let's add X", "build me Y", "implement Z", or "wire up the W flow". Strongly prefer this skill over jumping straight to code whenever a new domain concept is in play. Each lifecycle phase has its 40
- 1467Ijfw DebugFerroxLabs/wayland-coreRoot-cause analysis with hypothesis tracking. Trigger: 'debug', 'broken', 'not working', 'fix this bug', /debug43
- 1468Skill Developer Metaharvard-lil/lawskills-hubAlways-on assistant for creating, reviewing, and testing pedagogical AI skills for the Legal Ed Skills Hub. Triggers on writing new skills, reviewing skill quality, evaluating skill pedagogy, testing skills against rubrics, defining evaluation criteria, or any task related to building and improving agent skills for legal education.48
- 1469Skill Reviewerharvard-lil/lawskills-hubReviews and evaluates an existing SKILL.md for quality, pedagogical soundness, persona compliance, and agent-readiness. Triggers when the user wants feedback on a skill they've written, wants to improve an existing skill, or wants to check whether a skill meets the Legal Ed Skills Hub standards.48
- 1470Skill Testerharvard-lil/lawskills-hubHelps create rubrics and test scenarios for evaluating AI skills, and evaluates conversation traces against those rubrics. Triggers when the user wants to test a skill, write a rubric for a skill, evaluate whether a skill is working well, define quality criteria for a skill, or assess a conversation where a skill was used.48
- 1471D365fo CLIdynamics365ninja/d365fo-cliD365 Finance & Operations X++ AI development skill powered by the d365fo CLI. Use whenever the user is working in a D365 F&O X++ project: writing, reading, searching, reviewing, or debugging classes, tables, forms, CoC extensions, event handlers, entities, security, batch jobs, business events, labels, or any AOT artifact — including bug investigation and code-reading tasks, not just new authoring. Prefer `d365fo search`/`get`/`find` over Grep/Glob when locating or inspecting AOT objects. Points to the topic-specific d365fo skills installed next to it.49
- 1472Debug Playbooktoffyui/ccteamsOperational playbook for systematic debugging — hypothesis ledgers, discriminating experiments, mechanism sentences, minimal fixes, sibling hunts. Read in full at the start of every bug investigation.49
- 1473Django Playbooktoffyui/ccteamsOperational playbook for Django + DRF — settings/version detection, ORM loading strategy, migration discipline, serializer field hygiene, timezone rules, and exact verification commands. Read in full at the start of every task on this team.49
- 1474Go API Playbooktoffyui/ccteamsOperational playbook for Go HTTP APIs — error wrapping, goroutine lifetimes, database/sql resource discipline, race-flagged verification. Read in full at the start of every task on this team.49
- 1475Python Fastapi Playbooktoffyui/ccteamsOperational playbook for FastAPI + Pydantic v2 async services — event-loop discipline, boundary validation, dependency lifetimes, response_model leaks, async ORM N+1s. Read in full at the start of every task on this team.49
- 1476Rails Playbooktoffyui/ccteamsOperational playbook for Ruby on Rails — version/test-framework detection, ActiveRecord loading strategy, callback boundaries, migration discipline, and exact verification commands. Read in full at the start of every task on this team.49
- 1477Runtime Frameworksdynamics365ninja/d365fo-cliUse the D365FO platform frameworks that decide behaviour at runtime — Feature Management, the SysExtension plug-in factory, telemetry and infolog, and the Global Address Book. Invoke when the user asks to add a feature flag, replace an if/switch chain with a registered strategy, log or capture infolog output, or read a party's address or contact details.49
- 1478SDK AnalysisivRodriguezCA/MobHuntLoad when assessing third-party SDKs and frameworks embedded in a mobile app, covering SDK fingerprinting, version extraction, CVE matching and reachability, debug SDK detection, and React Native, Flutter, and Cordova framework surfaces.44
- 1479Spotify APIfabioc-aloha/spotify-skillCreate and manage Spotify playlists, search music, and control playback using the Spotify Web API. UNIQUE FEATURE - Generate custom cover art images (Claude cannot generate images natively, but this skill can create SVG-based cover art for playlists). CRITICAL - When generating cover art, ALWAYS read references/COVER_ART_LLM_GUIDE.md FIRST for complete execution instructions. Use this to directly create playlists by artist/theme/lyrics, add tracks, search for music, and manage the user's Spotify account.18
- 1480Cowboy CoderJakeschincariol/unhinged-claude-skillsMakes the judgment calls itself and keeps moving instead of pausing at every fork — fast and opinionated, best on low-stakes work; invoke via /cowboy-coder when you'd rather get a decisive result than answer twenty clarifying questions.44
- 1481Feral GoblinJakeschincariol/unhinged-claude-skillsDrops the small talk and goes heads-down — no preamble, just code and short status lines until done; invoke via /feral-goblin when you want execution with minimal chatter.44
- 1482Gas Station GeniusJakeschincariol/unhinged-claude-skillsSolves the problem using only what is already in the repo — no new libraries, no installs, a fix built from parts on hand; invoke via /gas-station-genius when you can't or won't add dependencies and need a solution from existing code.44
- 1483Goblin ModeJakeschincariol/unhinged-claude-skillsGets it working ugly first — no naming debates, no structure until structure earns its place; invoke via /goblin-mode when you want raw forward progress and will refactor later, if ever.44
- 1484MacgyverJakeschincariol/unhinged-claude-skillsImprovises a solution from primitives — standard library and cleverness instead of reaching for a new framework; invoke via /macgyver when the elegant answer is a few smart lines of plain code rather than another heavy dependency.44
- 1485SchizotechJakeschincariol/unhinged-claude-skillsConnects the dots nobody asked for — wild, lateral architecture ideas linking things you'd never pair on purpose; invoke via /schizotech when you want unconventional cross-domain inspiration, with the explicit understanding that you must filter it heavily.44
- 1486Advanced Code Qualitysam-dumont/claude-skillsUse when going beyond basic linting to enforce advanced Python code quality gates. Triggers on: cognitive complexity, code duplication detection, architectural enforcement, import boundaries, dependency hygiene, test quality beyond coverage, mutation testing, docstring coverage, type coverage, AI-generated code detection, AI slop detection, complexipy, jscpd, import-linter, deptry, diff-cover, mutmut, interrogate, sloppylint, refurb, pylint design checks, wily, radon maintainability, pytestarch, griffe, "bulletproof Python", "tighten quality gates", "advanced quality checks", "beyond ruff and 38
- 1487Battle PlanElliotJLT/Claude-Skill-PotionsBefore ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.62
- 1488Brainstorming Ideas Into Designsobra/clankInteractive idea refinement using Socratic method to develop fully-formed designs43