Loading...
Loading...
Found 999 Skills
Find, install, configure, and integrate Tool UI components in React apps using shadcn registry entries, compatibility checks, scaffolded runtime wiring, and troubleshooting workflows. Use when developers ask to add one or more Tool UI components, choose components for a use case, verify compatibility, or wire Tool UI payloads into assistant-ui or an existing chat/runtime stack.
Read this skill to write, generate, or add test code. Trigger when: (1) user asks to write, add, create, or generate tests of any kind (unit tests, integration tests, API tests, E2E tests, Playwright tests, Vitest tests); (2) user has code with missing or zero tests and wants coverage; (3) user just implemented a new service, endpoint, feature, or module and needs tests for it; (4) user refactored code and wants to verify nothing broke with tests; (5) user wants to improve or expand existing test coverage. This skill produces complete, pyramid-shaped test suites — reads the code, selects only the necessary layers (unit/integration/API/E2E), and generates every file needed (schema tests, service tests, factories, helpers, cleanup utilities, spec files) following strict Vitest and Playwright patterns. Skip this skill when debugging failing tests, asking how to use testing APIs or tools, explaining testing concepts, configuring test runners, reviewing existing test code, or migrating between test frameworks.
Prepare and route a document for e-signature — run a pre-signature checklist, configure signing order, and send for execution. Use when a contract is finalized and ready to sign, when verifying entity names, exhibits, and signature blocks before sending, or when setting up an envelope with sequential or parallel signers.
Natural language → SQL → execute read queries against the database. Auto-detects local connection, discovers project connectors for remote environments and domain knowledge. TRIGGER when: user asks a data question in natural language (count, list, show, verify, check, how many, cuantos, traeme, muéstrame), mentions database tables, or asks about data in any environment (production, staging, dev, local). DO NOT TRIGGER when: user provides raw SQL ready to execute.
Apply approved Xcode build optimization changes following best practices, then re-benchmark to verify improvement. Use when a developer has an approved optimization plan from xcode-build-orchestrator, wants to apply specific build fixes, needs help implementing build setting changes, script phase guards, source-level compilation fixes, or SPM restructuring that was recommended by an analysis skill.
Skrapp.io platform help — B2B email finder and data enrichment with 200M+ contacts and 20M+ company profiles. Use when finding emails by name and company, searching B2B contacts with filters (title, location, industry, seniority), enriching CSVs with email and firmographic data, extracting emails from LinkedIn via Chrome extension, verifying emails in bulk, or working with the Skrapp API. Do NOT use for general enrichment strategy (use /sales-enrich), deliverability/warmup (use /sales-deliverability), or building prospect lists strategy (use /sales-prospect-list).
README construction — initialize template structure, generate per-package READMEs from doc comments, plan writing tasks, assemble root README from docs/ and package READMEs via doc.json config, and verify edits with `plan drift`.
Verify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks. Combines /_next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running `next dev`.
Use when preparing a pull request for merge: inspect diffs, collect checks and review comments, classify findings, fix safe issues, verify, and loop until merge-ready.
Monitor Render services in real-time. Check health, performance metrics, logs, and resource usage. Use when users want to check service status, view metrics, monitor performance, or verify deployments are healthy.
Test local web applications with Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, or inspect browser logs.
Verify and enforce coding standards, AI guidelines, and workspace compliance across repositories. Use for standards propagation, compliance verification, and enforcing development best practices.