Loading...
Loading...
Found 818 Skills
Agent Infrastructure: Bridge any skill or directory of skill collections to Claude Code (~/.claude/skills) and Codex (~/.codex/skills). Supports skills in the dbskill repository as well as absolute paths to external skills. Connect source directories via symlinks, with both ends synchronized when the source directory is modified. Supports batch bridging by skill name, relative path, absolute path, or skills directory, as well as unbridging and checking bridge status. Triggers: /dbs-bridge, /bridge, "bridge this skill", "bridge this skills directory", "connect this skill to Claude Code and Codex", "make this skill callable by both Claude and Codex", "unbridge", "check bridge status" Bridge any skill folder or directory of skill folders to Claude Code and Codex using symlinks. Supports dbskill skills and external skill directories. Use when the user wants one or many skills callable from both agents, or wants to unlink/check bridge status. Trigger: /dbs-bridge, /bridge, "bridge this skill", "bridge this skills directory", "make this skill available to Claude Code and Codex", "unlink this skill", "check bridge status"
Testing strategies for JavaScript applications. Use when writing unit tests, integration tests, or setting up testing infrastructure. Covers Vitest, Jest, React Testing Library, and mocking patterns.
Use when managing test state and infrastructure with reusable Playwright fixtures and lifecycle hooks for efficient test setup and teardown.
Implement centralized logging with ELK Stack, Loki, or Splunk for log collection, parsing, storage, and analysis across infrastructure.
Guides agents and users through migrating from Gemini API in Google AI Studio to Gemini Enterprise Agent Platform (formerly Vertex AI). Use this skill when moving applications to Google Cloud, to leverage Cloud credits, or to unify inferencing with other Cloud infrastructure (IAM, billing, telemetry).
Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows. Use PROACTIVELY for monitoring infrastructure, performance optimization, or production reliability.
AWS/GCP cloud infrastructure: Well-Architected, security, cost, observability. Use when working with Terraform outputs, IAM policies, VPC design, load balancers, or cloud architecture decisions.
Guide Enable Banking Control Panel workflows for account signup, API application registration, sandbox/production setup, dedicated infrastructure selection, browser-generated or externally provided keys, production activation, account-link restricted mode, request logs, application statistics, application sharing, ASPSP status, Data Insights, Mock ASPSPs, and MFA. Use when Codex needs to explain or implement operational steps that depend on Enable Banking Control Panel configuration.
DataWorks Infrastructure Management: Create and query operations for Data Sources (51 types), Compute Resources, and Serverless Resource Groups, plus connectivity testing and resource group binding/unbinding. Uses aliyun CLI to call dataworks-public OpenAPI (2024-05-18). Trigger keywords: DataWorks data source, compute resource, resource group, datasource, data source, compute resource, resource group, mysql/hologres/maxcompute data source, holo/mc/flink resource, Serverless resource group, DataWorks infra, create/list datasource, DW environment config, infrastructure initialization, connect database to DataWorks, database connection failure, configure holo/mc resource. Not triggered: data development tasks, scheduling configuration, MaxCompute table management, data integration tasks, ECS/RDS/OSS operations, workspace member management, data quality monitoring, data lineage, data preview.
Design and implement scalable test automation frameworks with Page Object Model, fixtures, and reporting. Use for test framework, page object pattern, test architecture, test organization, and automation infrastructure.
Reviews, audits, and modifies CockroachDB cluster settings. Self-Hosted has full control over all settings and start flags. Advanced/BYOC can modify most SQL-level settings but infrastructure settings are managed by CRL. Standard has limited settings access — session variables are the primary tuning mechanism. Basic has minimal settings — use session variables and Cloud Console. Use when auditing configuration, tuning performance, or troubleshooting settings-related issues.
Use when conducting security audits, reviewing code for vulnerabilities, or analyzing infrastructure security. Invoke for SAST scans, penetration testing, DevSecOps practices, cloud security reviews.