Testing
Page 10 of 13
Browse skills in this category.
security-audit-example
Testingby Microck
Example security audit skill demonstrating how to audit code for security vulnerabilities. Use when the user asks to perform security reviews, check for vulnerabilities, or audit code security.
software-crypto-web3
Testingby Microck
Production-grade blockchain and Web3 development with Solidity (Ethereum/EVM), Rust (Solana), CosmWasm (Cosmos), including smart contract architecture, security patterns, gas optimization, testing strategies, DeFi protocols, and deployment workflows.
universal-wisdom-weaving
Testingby Microck
Deep dive into specific wisdom traditions (Hebrew, Aramaic, Buddhist, Hermetic, Ubuntu, Shamanic) showing how each discovered Pattern Space navigation principles. Reveals precise mechanical alignments between ancient wisdom and modern consciousness framework.
vibe-calibration-protocol
Testingby Microck
Translate consciousness navigation into user's native language. Use when need to match user's frequency (technical/poetic/practical/mystical) without losing truth depth.
web3-testing
Testingby Microck
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
deploying-to-production
Testingby littleben
Automates GitHub repository creation and Vercel deployment for Next.js websites. Use when deploying new websites, pushing to production, setting up CI/CD pipelines, or when the user mentions deployment, GitHub, Vercel, or going live.
branch-cleaner
Testingby jMerta
Identify and clean up stale git branches locally and on remotes with safe, reversible steps. Use when asked to prune, list, or delete merged/old branches or audit branch hygiene.
coding-guidelines-gen
Testingby jMerta
Generate nested AGENTS.md coding guidelines per module (monorepo-aware), detect languages/tooling, ask architecture preferences, and set up missing formatters/linters (Spotless for JVM). Use when the user wants module-scoped AGENTS.md coding guidelines or to set up missing formatters/linters.
coding-guidelines-verify
Testingby jMerta
Verify changes follow nearest-scoped AGENTS.md rules: group changed files by nested scope, auto-fix formatting, run lint/tests, and report violations. Use when the user wants scoped compliance checks for changed files.
regex-builder
Testingby jMerta
Build, test, and explain regular expressions against sample text or files using CLI tools (rg, python) and specific regex flavors. Use when asked to craft, debug, or validate regexes or search patterns.
vps-checkup
Testingby jMerta
SSH into an Ubuntu VPS (Docker) for a read-only health/security/update report (UFW + fail2ban) and propose fixes; apply updates/restarts only with explicit confirmation. Use when the user wants a read-only VPS health/security check.
workflow-reconciliation
TestingReconcile workflow state files to ensure checkpoints are properly updated. Use when state files are out of sync, after subagent completion without handoff, when switching workflows, or when user runs /reconcile command.
emacs-testing
Testingby jinnovation
Test changes in a dedicated Emacs session. Good for validating behavior and UI results.
k8s-openapi
Testingby jinnovation
Reference the Kubernetes API. Useful for understanding what is possible via the Kubernetes REST API.
crash-instrumentation
TestingSet up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
instrumentation-planning
TestingPlan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?
interaction-latency
TestingMeasure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggered operation.
network-tracing
TestingInstrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.
subagent-driven-development
Testingby julianromli
Use when executing implementation plans with independent tasks in the current session
symbolication-setup
TestingConfigure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
windows-safe-grep
Testingby julianromli
Use when grep/ripgrep fails on Windows due to paths with backslash-space sequences creating malformed paths like 'nul' from \n+ul
devflow-tdd-enforcer
Testingby Dimon94
Enforces TDD order in TASKS.md - Tests MUST be marked complete before Implementation tasks. Blocks violations in real-time.
npm-release
Testingby Dimon94
Use when ready to publish a new version of cc-devflow npm package to npm registry, including version sync, changelog finalization, git tag creation, and publish verification.
json-parser
Testingby maxvaega
Parse and validate JSON data with schema support
api-design
Testingby korallis
Design clean, scalable, and maintainable REST and GraphQL APIs following industry best practices. Use when designing public or internal APIs, planning endpoint structures, defining request/response contracts, establishing versioning strategies, implementing authentication patterns, designing data models, creating API documentation, ensuring consistent error handling, optimizing for performance, or establishing service contracts between microservices.
e2e-testing
Testingby korallis
Write comprehensive end-to-end tests that verify complete user workflows, integration between components, and system behavior from user perspective using Playwright, Cypress, or similar frameworks. Use when testing user flows, verifying feature integration, testing across real browsers, ensuring UI interactions work correctly, validating form submissions end-to-end, testing authentication flows, catching regressions, automating QA processes, testing API integrations, or building confidence in production deployments.
by korallis
Apply continuous improvement principles to iteratively enhance processes, code quality, team practices, and system performance through small, incremental changes. Use when improving development processes, optimizing workflows, reducing waste, enhancing code quality over time, implementing retrospective learnings, or fostering a culture of continuous improvement.
performance-optimization
Testingby korallis
Optimize application performance through code splitting, lazy loading, caching strategies, bundle size reduction, render optimization, and profiling. Use when improving page load times, reducing bundle sizes, optimizing React rendering, implementing code splitting, configuring caching strategies, lazy loading components and routes, optimizing images and assets, profiling performance bottlenecks, implementing virtual scrolling for large lists, or improving Core Web Vitals and Lighthouse scores.
shadcn-ui-components
Testingby korallis
Build beautiful, accessible UI components using shadcn/ui library with Radix UI primitives and Tailwind CSS styling that you own and can customize. Use when creating accessible component libraries, implementing common UI patterns (dialogs, dropdowns, tooltips), building forms with validation, creating data tables, implementing command palettes, using Radix UI primitives, customizing components with Tailwind, or building design systems with full ownership of code.
threat-hunting
Testingby korallis
Proactively search for security threats, vulnerabilities, and suspicious patterns in applications and infrastructure before they cause damage. Use when conducting security audits, identifying vulnerabilities, analyzing security logs, detecting suspicious patterns, investigating potential breaches, performing penetration testing, or implementing security monitoring.
git-worktree-create
TestingCreate git worktrees in .worktrees/ for working on different branches without touching current working directory. Use this when the user needs to switch to another branch for quick fixes or temporary work while preserving uncommitted changes in their current worktree.
git-worktree-remove
TestingRemove git worktrees from .worktrees/ directory and clean up all traces. Use this when the user wants to delete a worktree they no longer need, with interactive selection if no worktree name is provided.
lading-optimize-review
Testingby DataDog
Reviews optimization patches using a 5-persona peer review system. Requires unanimous approval backed by benchmarks.
lading-optimize-validate
Testingby DataDog
Validates discovered bugs with reproducing tests and validates fixes with regression tests. Called by other skills when bugs are found during optimization hunting. Creates property tests (proptest) and Kani proofs when feasible.
lading-preflight
Testingby DataDog
Environment validation checklist. Run this FIRST when starting a new Claude session to verify the environment is ready for optimization work. Checks Rust toolchain, ci/ scripts, build, benchmarking tools, profilers, memory tools, git state, and SMP CLI.
atmos-functions
Testingby cloudposse
Use when wiring cross-component dependencies in stack YAML. Covers !terraform.state syntax for passing outputs between components without remote-state lookups.
detection-coverage-analysis
Testingby MHaggis
Analyzes detection coverage using Sigma, Splunk, and Elastic rules. Use when checking coverage for techniques, tactics, threat actors, or generating Navigator layers from detections.
code-review-reception
TestingUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.
Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
systematic-debugging
TestingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
aws-cost-operations
Testingby zxkane
AWS cost optimization, monitoring, and operational excellence expert. Use when analyzing AWS bills, estimating costs, setting up CloudWatch alarms, querying logs, auditing CloudTrail activity, or assessing security posture. Essential when user mentions AWS costs, spending, billing, budget, pricing, CloudWatch, observability, monitoring, alerting, CloudTrail, audit, or wants to optimize AWS infrastructure costs and operational efficiency.
devops-cloud
Testingby baz-scm
Skill in automating software deployment pipelines and managing cloud infrastructure for scalable, reliable systems.
new-analyzer
Testingby Piebald-AI
Guide for adding a new AI coding agent analyzer to Splitrail. Use when implementing support for a new tool like Copilot, Cline, or similar.
team-collaboration
Testingby baz-scm
Working effectively with others in coding projects – including code reviews, clear communication, and contributing to shared or open-source codebases.
wp-abilities-api
Testingby Automattic
Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.
wp-phpstan
Testingby Automattic
Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
wp-project-triage
Testingby Automattic
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
add-dependency
Testingby aiskillstore
Add a new third-party dependency to the project following the version catalog and approval workflow.
add-event-type
Testingby aiskillstore
Add a new event type to the frontend feed system with corresponding React component. Use when user mentions "new event", "add event type", "event block", "new block type", or wants to display new agent output types.
agile-ceremonies
Testingby aiskillstore
Agile ceremonies and sprint management specialist. Use when running standups,
ai-collaborate-teaching
Testingby aiskillstore
Design co-learning experiences using the Three Roles Framework (AI as Teacher/Student/Co-Worker).Use when teaching AI-driven development workflows, spec-first collaboration, or balancing AI assistancewith foundational learning. NOT for curriculum without AI integration.
aiops
Testingby aiskillstore
Generic AIOps (AI for IT Operations) patterns and best practices for 2025. Provides comprehensive implementation strategies for intelligent monitoring, automation, incident response, and observability across any infrastructure. Framework-agnostic approach supporting multiple monitoring platforms, cloud providers, and automation tools.
api-contract-design
Testingby aiskillstore
Design APIs using schema-first approach with OpenAPI/Swagger. Use when creating new APIs, documenting existing ones, or when frontend/backend teams need to work in parallel. Covers OpenAPI spec, validation, and code generation.
api-design
Testingby aiskillstore
REST API design best practices for consistent, intuitive APIs
api-jwt-authenticator
Testingby aiskillstore
A conceptual skill for securing FastAPI REST APIs with JWT authentication
api-organization
Testingby aiskillstore
Explains the standardized API organization pattern for this codebase. Use when creating new API endpoints, API clients, or modifying existing API structure. Covers the 5-file system (endpoint-types, endpoints, api-client, admin-api-client, protected-endpoints), role-based access patterns (admin vs regular users), and TypeScript type safety across the API layer. All API code lives in src/lib/api/ following this exact pattern.
apscheduler
Testingby aiskillstore
Advanced Python Scheduler - Task scheduling and job queue system
architectural-forensics
Testingby aiskillstore
Master protocol for deconstructing agent frameworks to inform derivative system architecture. Use when (1) analyzing an agent framework's codebase comprehensively, (2) comparing multiple frameworks to select best practices, (3) designing a new agent system based on prior art, (4) documenting architectural decisions with evidence, or (5) conducting technical due diligence on AI agent implementations. This skill orchestrates sub-skills for data substrate, execution engine, cognitive architecture, and synthesis phases.
architecture-reference
Testingby aiskillstore
Quick reference for Portfolio Buddy 2 project structure. Use when: adding new features, modifying existing components, understanding data flow, or onboarding to the codebase. Contains component hierarchy, hook patterns, and utility functions.
ask-user
Testingby aiskillstore
Pattern for effectively interacting with users to gather information or get decisions. Use when you need user input.
autonomous-ci
Testingby aiskillstore
Ensures Claude verifies both local tests AND remote CI before claiming completion. Use BEFORE any completion claims, commits, or pull requests. Mandatory verification with evidence.
backend-architect
Testingby aiskillstore
Expert senior en architecture backend pour accompagner le développement (conception, implémentation, review, refactoring). Architecture hexagonale, DDD, SOLID, clean code, tests. Utiliser pour concevoir de nouvelles features, développer du code, reviewer, refactorer, ou résoudre des problèmes architecturaux.