Loading...
Loading...
Found 3,719 Skills
Lambdatest integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lambdatest data.
Run vercel-plugin eval scenarios in Vercel Sandboxes instead of local WezTerm panels. Provisions ephemeral microVMs with Claude Code + plugin pre-installed, runs benchmark prompts, extracts hook artifacts, and produces coverage reports.
E2E 시나리오를 Claude Code에서 실행하는 스킬. "시나리오 실행", "e2e 실행", "E2E 돌려", "시나리오 돌려" 키워드로 트리거.
Test coverage analysis, identify gaps, and generate missing tests to achieve over 80% coverage. Trigger conditions: user requests for test coverage analysis, test coverage improvement, and test writing.
NoSQL injection playbook. Use when MongoDB-style operators, JSON query objects, flexible search filters, or backend query DSLs may allow data or logic abuse.
Microcks integration. Manage data, records, and automate workflows. Use when the user wants to interact with Microcks data.
Use when the user wants a quality review, interaction audit, or to test the workflow against realistic scenarios.
Systematically audit, improve, and enforce test coverage in any repository. Use when asked to improve coverage, add missing tests, set up coverage thresholds, audit test gaps, or wire coverage into CI/hooks. Works across ecosystems (TypeScript, Python, Go, Rust, etc.). Composes with the hk skill for pre-commit enforcement. Triggers on: test coverage, missing tests, coverage threshold, coverage report, untested code, coverage gap, coverage audit.
Calculate Value at Risk to estimate maximum portfolio loss at a given confidence level. Use this skill when the user needs to quantify downside risk, set risk limits, or report regulatory risk measures — even if they say 'worst case loss', 'portfolio risk', or 'how much could we lose'.
Debugging and Root Cause Localization for AscendC Operator Precision Issues. Used when operator precision tests fail (such as allclose failure, result deviation, all-zero/NaN output, etc.). Process: Error Distribution Analysis → Code Error-Prone Point Review → Experimental Isolation → printf/DumpTensor Instrumentation → Fix Verification. Keywords: precision debugging, precision issue, result inconsistency, error localization, allclose failure, output deviation, NaN, all-zero, precision debug.
Execute YAML test plan, stop on first failure, output rich debug prompt
Use when implementing features with test-driven development, writing tests before code, building domain-rich business logic, or following hexagonal architecture