Loading...
Loading...
Found 4,081 Skills
Manage database, file system, and API connections for Sling. Use when setting up connections, testing connectivity, discovering tables/files, or configuring credentials.
Interactive Code Review: Inspect architecture, code quality, testing, and performance section by section. Can review git diff, specified files, or entire PRs. Trigger words: /code-review, review code, code review, code review
Comprehensively reviews Python libraries for quality across project structure, packaging, code quality, testing, security, documentation, API design, and CI/CD. Provides actionable feedback and improvement recommendations. Use when evaluating library health, preparing for major releases, or auditing dependencies.
Manage CloudSync Master WordPress plugin via WP-CLI. This skill should be used when configuring, testing, monitoring, or operating CloudSync Master (media offloading to cloud storage). Covers account setup for S3/R2/GCS/DigitalOcean/Backblaze/Wasabi/Vultr/Linode, plugin settings, queue management, object management, license activation, migration from competitors, and wp-config.php configuration export. Use when the user mentions CloudSync Master, cloud media offloading, wp cloudsync commands, or needs to set up WordPress media on cloud storage.
Design test cases based on requirements. Use when users need test case design, testing strategy, or QA planning. Triggers on keywords like "test cases", "test design", "unit test", "integration test", "e2e test".
[Testing] Autonomous subagent variant of code-review. Use when reviewing code changes, pull requests, or performing refactoring analysis with focus on patterns, security, and performance.
Whole-codebase vulnerability analysis leveraging 1M context window. Loads entire project source, runs deep security analysis in a single pass. Opus 4.6 found 500 zero-day vulnerabilities in pre-release testing — this skill weaponizes that capability.
Cognitive science-based deep source code understanding assistant (Chinese improved version). Supports three analysis modes: Quick (overview), Standard (comprehension), Deep (mastery, automatically uses parallel processing for large projects). Integrates elaborative interrogation, self-explanation testing, and retrieval practice to help truly understand and master code.
Orchestrate a specialized software development agent team. Receive user requests, classify task type, select the matching workflow, delegate each step to specialist agents via the Agent tool, and assemble the final output. Use when the user needs multi-step software development involving architecture, implementation, testing, security review, or code review. Also use for production incident investigation — when the user reports a live system issue, service outage, pod crash, data anomaly, or needs root cause analysis using kubectl, psql, argocd, or docker. Trigger this skill whenever a task involves more than one concern (e.g., "add a new endpoint" needs BA + Architect + Developer + QA + Security), when the user mentions team coordination, agent delegation, or when the work clearly benefits from multiple specialist perspectives rather than a single implementation pass.
Use this skill when building dbt models, designing semantic layers, defining metrics, creating self-serve analytics, or structuring a data warehouse for analyst consumption. Triggers on dbt project setup, model layering (staging, intermediate, marts), ref() and source() usage, YAML schema definitions, metrics definitions, semantic layer configuration, dimensional modeling, slowly changing dimensions, data testing, and any task requiring analytics engineering best practices.
Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session. Opens an interactive picker UI where you select which cookie domains to import. Use before QA testing authenticated pages.
Use when the user asks to create a pull request. Build a complete PR using best-practice structure with rich details on changes, verification, QA evidence, risks, and rollout notes. Include issue linkage and clear testing commands/results in the PR body.