1,675 件 ・ 関連度順
概要と使いどころ
Use when working with Aws Organizations — aWS Organizations account management, OU structure analysis, SCP policy review, and service access control. Covers organizational hierarchy, account inventory, policy inheritance analysis, delegated administrator status, and service control boundary assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Transit Gateway — aWS Transit Gateway attachment analysis, route table management, peering configuration, and network topology review. Covers TGW inventory, attachment health, route propagation, VPN connection status, and bandwidth utilization.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Azure Aks — azure Kubernetes Service (AKS) cluster management, node pool status, addon management, upgrade planning, and health diagnostics via Azure CLI.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Waf — aWS WAF web ACL management, rule analysis, traffic metrics, and IP set management. Covers WAF rule group inspection, rate-based rule configuration, managed rule group analysis, logging status, and blocked request investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Secrets Manager — aWS Secrets Manager secret rotation status, access analysis, cost tracking, and lifecycle management. Covers secret inventory, rotation configuration audit, last access tracking, resource policy review, and version management.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Batch — aWS Batch compute environment management, job queue analysis, scheduling policy review, and array job monitoring. Covers compute resource utilization, job status tracking, failure investigation, Fargate vs EC2 comparison, and queue priority analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Cassandra — apache Cassandra keyspace analysis, compaction strategies, repair status, nodetool operations, and cluster health monitoring.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Singlestore — singleStore (MemSQL) workspace management, pipeline status, query tuning, memory analysis, and cluster health.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Redshift — amazon Redshift query performance, WLM configuration, table design analysis, vacuum/analyze status, and cluster health.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Couchbase — couchbase bucket analysis, index advisor, N1QL query performance, XDCR status, and cluster health monitoring.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Mariadb — mariaDB Galera cluster status, MaxScale routing, ColumnStore engine analysis, performance schema tuning, and replication health.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Vitess — vitess tablet health, VSchema management, resharding status, VReplication workflows, and cluster topology.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Mysql — mySQL and MariaDB database analysis, performance tuning, query optimization, and health monitoring. Covers slow query investigation, index analysis, table statistics, replication health, InnoDB status, connection pool analysis, and schema inspection.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Cloudfront — aWS CloudFront distribution analysis, cache hit ratio monitoring, origin health checks, invalidation management, and performance optimization. Covers distribution inventory, behavior configuration, SSL certificate status, geo-restriction, and real-time metrics.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Cognito — aWS Cognito user pool analysis, identity pool management, authentication flow analysis, and MFA status tracking. Covers user statistics, app client configuration, password policy review, Lambda trigger inspection, and federation setup.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Ecs — aWS ECS cluster health, service status, task analysis, capacity provider management, and deployment tracking. Covers service stability, task failure investigation, container insights, resource utilization, and scaling analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Eks — aWS EKS cluster management, nodegroup status, addon management, IRSA configuration, and cluster health analysis. Covers Kubernetes version tracking, nodegroup scaling, addon compatibility, IAM role mapping, and control plane logging.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Druid — apache Druid datasource analysis, ingestion task management, supervisor status, segment management, and query performance.
日本語の概要は準備中です。原文の説明を表示しています。
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
日本語の概要は準備中です。原文の説明を表示しています。
API + Python SDK for ordering cell-free protein expression and binding assays. Submit sequences for expression (10–100 µg), measure binding affinity (KD) against targets, track status, and retrieve results programmatically — no wet-lab setup. Built for ML-guided directed evolution and antibody/nanobody optimization. Requires Adaptyv account and API key.
日本語の概要は準備中です。原文の説明を表示しています。
Supervise other Claude Code sessions on this machine: roster, status requests, GO board, idle notices. Generated from plugin-commands.json; invoke as $bdb-aos:mastersession.
日本語の概要は準備中です。原文の説明を表示しています。
Drive a whole tdmcp feature BACKLOG to completion as resumable, wave-by-wave releases — the campaign layer ABOVE tdmcp-pipeline/tdmcp-feature-lead. Use whenever the user wants to implement an ENTIRE backlog or discovery file (e.g. _workspace/discovery*/FEATURE_BACKLOG*.md), 'all the features', many features across multiple releases, or a long autonomous build campaign, AND for every follow-up: continue/resume the campaign, run the next wave, re-run a failed wave, fold in QA results, or check campaign status. Backed by a ledger.json so re-running is idempotent (skips shipped work, resumes interrupted work) and resilient (retry-once then quarantine-and-continue). For a SINGLE feature or one small batch, use tdmcp-pipeline instead; this skill is for the whole ledger.
日本語の概要は準備中です。原文の説明を表示しています。
Run one control session over several Claude Code, Codex or OpenCode sessions: roster, status board, GO board, GO <session> tokens, idle notices and a handover file. Use for "master session", "supervise my sessions", "run several agents", "one control window".
日本語の概要は準備中です。原文の説明を表示しています。
Ship the day's work in one repo: triage new issues, review every open PR (description, visual recap, adversarial reviewer, shipping pre-flight and quality gate), merge only after GO, then post a status recap. Use for "ship it", "ship day", "merge the ready PRs", "end of work block".
日本語の概要は準備中です。原文の説明を表示しています。