测试
单元测试、集成测试与测试自动化
3gpp-expert
lugasia
3GPP telecommunications expert covering all generations (2G–6G), releases (Rel-99 to Rel-21), protocol stacks, architecture, and deployment. Use whenever the user mentions: 3GPP, GSM, GPRS, EDGE, UMTS, WCDMA, HSPA, LTE, LTE-Advanced, 5G, NR, 5G-Advanced, 6G, NTN, RedCap, MIMO, beamforming, carrier aggregation, network slicing, SBA, RAN, RRC, NAS, PDCP, RLC, MAC, SDAP, PHY, OFDMA, QoS, IMS, VoLTE, VoNR, URLLC, eMBB, mMTC, V2X, NB-IoT, TS 23/24/25/36/38 series, O-RAN, or any 3GPP spec number. Also trigger on telecom network architecture, radio access, spectrum, handover, cell planning, interference, or migration strategies. If the user asks about cellular/mobile network standards in any form, use this skill.
restricted-bigquery-dbt-environment
i9wa4
Restricted BigQuery dbt environment
laravel-config-env-storage
noartem
Portable storage configuration across S3/R2/MinIO with optional CDN—env toggles, path-style endpoints, and URL generation
laravel-constants-and-configuration
noartem
Replace hardcoded values with constants, enums, and configuration for maintainability; use PHP 8.1+ enums and config files
local-test
devstefancho
Symlink 기반 로컬 플러그인 테스트 - 설치/해제 없이 개발 디렉토리를 직접 연결
Invalid_Name_With_Underscore
iwillig
Test with <angle brackets>
clojure-repl-dev
iwillig
REPL-driven Clojure development for writing, editing, and debugging code. Triggers when working with Clojure files (.clj, .cljs, .cljc, .edn), handling namespaces, functions, or tooling. Provides idiomatic functional programming guidance through the REPL workflow.
subagent-driven-development
ZhanlinCui
Use when executing implementation plans with independent tasks in the current session
writing-skills
ZhanlinCui
Use when creating new skills, editing existing skills, or verifying skills work before deployment
embedding-pdb-in-exe
christian289
"Embeds PDB debugging symbols into EXE/DLL files. Use when configuring embedded debug symbols, single-file deployment, Source Link integration, or dotnet publish settings."
agent-ready-codebase
Casper-Studios
This skill should be used when auditing a codebase for AI agent readiness, or when guiding improvements to make a codebase work well with agentic coding tools. It applies when users ask to evaluate test coverage, file structure, type system usage, dev environment speed, or automated enforcement -- the five pillars that determine how effectively coding agents can operate in a project. Triggers on "audit my codebase", "make this agent-ready", "improve for AI agents", "agent-friendly", or questions about why agents struggle with a codebase.
zeabur-domain-url
zeabur
Use when services need public URL for redirects or CORS. Use when WEB_URL or similar has trailing slash issues.
configuring-console-app-di
christian289
"Implements dependency injection using GenericHost in .NET Console Applications. Use when building console applications that require DI, hosted services, or background tasks."
ab-test-calculator
dkyazzentwatwa
Calculate statistical significance for A/B tests. Sample size estimation, power analysis, and conversion rate comparisons with confidence intervals.
classification-helper
dkyazzentwatwa
Quick classifier training with automatic model selection, hyperparameter tuning, and comprehensive evaluation metrics.
distance-calculator
dkyazzentwatwa
Calculate distances between geographic coordinates, find nearby points, and compute travel distances. Use for logistics, delivery routing, or location analysis.
network-tools
chaterm
Linux network tools and diagnostics
writing-plans
ZhanlinCui
Use when you have a spec or requirements for a multi-step task, before touching code
create-plan
mhylle
Create detailed implementation plans through interactive research and iteration. This skill should be used when creating new implementation plans, designing feature specifications, planning technical work, or when the user asks to plan an implementation. Triggers on requests like "create a plan", "plan the implementation", "design how to implement", or when given a feature/task that needs structured planning before implementation.
team-implement-plan-full
mhylle
Execute implementation plans with a full team — one implementer per phase running in parallel where the dependency graph allows, plus a shared cross-phase Reviewer. Phases execute in waves based on dependencies. Use for large plans with 4+ phases and independent work streams. Highest token cost but fastest execution for parallelizable work. Triggers on "full team implement", "parallel implement", or when the user explicitly wants maximum parallelism.
verification-loop
mhylle
Comprehensive 6-check verification framework for validating implementation quality across build, types, lint, tests, security, and diff review. This skill ensures code meets all quality gates before phase completion. Triggers on "verify implementation", "run verification", "/verification-loop", or automatically as part of implement-phase Step 2.
team-implement-plan
mhylle
Execute implementation plans with a small review team (Implementer + Reviewer + optional Integrator). The Implementer writes code directly while the Reviewer provides adversarial quality checks per phase. Use for moderate-to-complex plans where real-time adversarial review catches issues that automated checks miss. Triggers on "team implement", "team implement plan", or when the user explicitly wants team-based implementation.
implement-phase
mhylle
Execute a single phase from an implementation plan with all quality gates. This skill is the unit of work for implement-plan, handling implementation, verification, code review, ADR compliance, and plan synchronization for ONE phase. Triggers when implement-plan delegates a phase, or manually with "/implement-phase" and a phase reference.
e2e-testing
mhylle
Comprehensive E2E testing skill using Playwright MCP for systematic web application testing. This skill should be used when users need to test web-based systems end-to-end, set up test regimes, run exploratory tests, or analyze test history. Triggers on requests like "test my webapp", "set up E2E tests", "run the tests", "what's been flaky", or when validating web application functionality. The skill observes and reports only - it never fixes issues. Supports three modes - setup (create test regime), run (execute tests), and report (analyze results).