Loading...
Loading...
Found 3,719 Skills
Minimal voice design TTS smoke test for Model Studio Qwen TTS VD.
Generate a complete Model Context Protocol server project in Swift using the official MCP Swift SDK package.
Document undocumented public APIs in PyTorch by removing functions from coverage_ignore_functions and coverage_ignore_classes in docs/source/conf.py, running Sphinx coverage, and adding the appropriate autodoc directives to the correct .md or .rst doc files. Use when a user asks to remove functions from conf.py ignore lists.
Add custom local tools to ToolUniverse and use them alongside the 1000+ built-in tools. Use this skill when a user wants to: create their own tool for a private or custom API, add a local tool to their workspace, integrate an internal service with ToolUniverse, or use a custom tool via the MCP server or Python API. Covers both the JSON config approach (easiest, no Python needed) and the Python class approach (full control). Also covers how to verify tools loaded correctly and how to call them. Also covers the plugin package approach for reusable, shareable, pip-installable tool sets.
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Discover and execute repository test commands safely with evidence-based command selection and safety guardrails.
Setup and utility scripts for muapi.ai — configure API keys, test connectivity, and poll for async generation results
Specialized integration evaluator for the Evaluate-Loop. Use this for evaluating tracks that integrate external services — Supabase auth/DB, Stripe payments, Gemini API, third-party APIs. Checks API contracts, auth flows, data persistence, error recovery, environment config, and end-to-end flow integrity. Dispatched by loop-execution-evaluator when track type is 'integration', 'auth', 'payments', or 'api'. Triggered by: 'evaluate integration', 'test auth flow', 'check API', 'verify payments'.
Use when the user wants to validate that implemented code matches its specifications, generate integration tests from feature files, or check if code still satisfies existing scenarios. Trigger after implementation completes a feature. Also use when the user asks "does the code do what we specified?" or "generate tests from the feature files".
Generate Playwright tests. Use when user says "write tests", "generate tests", "add tests for", "test this component", "e2e test", "create test for", "test this page", or "test this feature".
Use when an agent is asked to define, review, or write acceptance criteria for a request or plan. Derives acceptance criteria from the current request context, confirms them with the user, and writes them into the plan file or a standalone acceptance_criteria.md file.
Creates complete VoltDB client applications with optimized table partitioning, DDL schemas, stored procedures, and integration tests. Use when user wants to create a VoltDB client, connect to VoltDB, create VoltDB schemas, write VoltDB stored procedures, or write VoltDB integration tests.