297 skills · sorted by relevance
Write focused Java unit tests with JUnit 5, including tests that repeat checks across different inputs. Covers clear test structure, exception checks, mock objects that replace dependencies, and ways to organize test suites.
Write C# unit tests with TUnit using clear test structure, asynchronous checks, and multiple input cases. Get guidance on setup and cleanup, execution controls, test organization, and converting existing xUnit tests to TUnit.
Review and improve .NET/C# code against project conventions. Cover public API documentation, dependency injection for supplying services to classes, asynchronous operations, tests, configuration, logging, and input validation, including guidance for Semantic Kernel integrations.
Write focused C# unit tests with XUnit, including tests that run against multiple input datasets. Apply consistent naming, setup, assertions, shared fixtures, and mock dependencies to keep tests readable, independent, and organized.
Write C# unit tests with NUnit using clear naming, focused assertions, and independent test cases. Covers project setup, testing with multiple input values, exception checks, and replacing dependencies with mocks to test components in isolation.
Investigate CUDA crashes in SGLang using logs and inputs saved before execution. Inspect tensor shapes, data types, and numerical anomalies, with guidance for separate process logs and additional CUDA debugging tools.
Write and register SGLang unit and end-to-end tests, from choosing models and file locations to reusing server fixtures. Follow project rules for meaningful assertions, CI registration, dependency mocking, and safe server cleanup after tests.
Rewrite lengthy prompts, tool descriptions, and agent instructions into compact text while preserving requirements, exceptions, and exact values. The process records removed content and compares token counts, the units models use to measure text length.
Approach engineering problems by checking assumptions, defining performance constraints, and choosing suitable tools before implementation. The skill guides algorithm analysis, complete code, performance optimization, and correctness checks through tests, assertions, or formal verification, meaning mathematical checks of correctness.
Create, update, and debug Docker-based end-to-end tests for the Composio CLI. Covers running the executable, keeping test data separate, checking command output, and maintaining package manifests within the CLI test suite.
Explore an existing Vitest 3.2 JSON test report to count results, search failed tests, and inspect file errors. Review original diagnostic details and keep tentative explanations separate from evidence, without launching tests.
Generate reusable test helpers for Godot, Unity, or Unreal projects. Create utilities for checking results, building test objects, and replacing dependencies, following the project's configured test framework and existing test patterns.
Create Playwright tests that capture table appearance and compare screenshots with reference images using reg-suit. The skill covers checking each state before capture, adding demo routes, and choosing themes, browsers, and framework variants to test.
Review Handsontable code changes for architecture, code quality, performance, accessibility, and test coverage. Findings include severity, confidence, and file locations, helping developers assess whether changes follow project rules and demonstrate the intended behavior.
Design and review TypeScript code with safer types and readable structures. Covers strict compiler settings, generics for reusable typed code, type guards for checking unknown values, and utility types for transforming existing definitions.
Build runnable Foundry tests that demonstrate smart contract vulnerabilities with before-and-after logs and assertions. Use fork tests, which copy blockchain state, and test helpers to reproduce known DeFi incidents or prepare evidence for a report.
Verify development results before reporting success or preparing commits and pull requests. Run checks that support each claim, inspect their actual output, and report remaining gaps instead of relying on assumptions or another agent’s success message.
Evaluate how well existing tests catch code changes, then combine the results with function relationships. Get a report separating harmless findings, missing unit tests, and targets for fuzzing, which tests many generated inputs.
Writes, reviews, and debugs property-based tests, which generate inputs to check general rules. Helps test conversions, parsers, normalization, and state invariants, assess whether existing assertions are meaningful, and distinguish faulty rules from implementation bugs.
Launch the real iPolloWork app on Daytona or locally and run scripted end-to-end tests through its debugging connection. Collect machine-checkable assertions, validated screenshots, and reports as evidence of the tested behavior.
Investigate MSBuild failures, measure slow builds, or review existing build definitions. Use binary logs, project settings, and comparable timing measurements to identify causes, propose focused repairs, and verify behavior without broad configuration changes.
Upgrade MSTest v1 or v2 projects to v3, including partially completed migrations. Update packages, repair affected assertions and test data, replace legacy settings, and compare test results while preserving the existing test runner.
Assess factual claims in AI-generated text by separating facts from opinions, choosing suitable independent evidence, and explaining what is supported or uncertain. Use it for a completed fact-check or an optional exercise in evaluating AI answers.
Investigate XXE, an XML parsing flaw, in APIs and document uploads. The skill guides entry point discovery, external callback checks, and evidence collection to establish whether files or internal services are actually exposed.