2,140 件 ・ 関連度順
概要と使いどころ
Use when working with Aerospike — aerospike cluster management, namespace utilization, set analysis, and secondary index monitoring. Covers node health, storage engine statistics, migration tracking, UDF management, and XDR cross-datacenter replication status. Read this skill before any Aerospike operations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Apache Kudu — apache Kudu cluster management, tablet server health monitoring, table partition analysis, and replication diagnostics. Covers master health, tablet distribution, column encoding efficiency, compaction metrics, and maintenance window scheduling. Read this skill before any Kudu operations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Rds Deep — aWS RDS deep analysis covering Performance Insights, event subscriptions, proxy management, and global database status. Covers PI counter metrics, wait event analysis, top SQL queries, read replica lag, storage autoscaling, and Aurora-specific diagnostics.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Azure Sql — azure SQL Database DTU/vCore analysis, query performance insights, elastic pool management, geo-replication status, and database health monitoring via Azure CLI.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Azure Blob Storage — azure Blob Storage container analysis, access tier management, lifecycle policies, replication configuration, and storage account health via Azure CLI.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Mongodb — mongoDB database analysis, performance tuning, query optimization, and health monitoring. Covers collection analysis, index recommendations, aggregation pipelines, replica set health, Atlas cluster management, and slow query investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Vitess — vitess tablet health, VSchema management, resharding status, VReplication workflows, and cluster topology.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Elasticache Deep — aWS ElastiCache deep analysis for Redis and Memcached clusters, replication health, failover analysis, and performance metrics. Covers node-level metrics, memory utilization, cache hit rates, eviction tracking, connection analysis, and engine-specific diagnostics.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Eventbridge — aWS EventBridge event bus management, rule analysis, target health monitoring, and schema registry exploration. Covers event pattern matching, rule invocation metrics, dead-letter queue analysis, cross-account event routing, and event replay.
日本語の概要は準備中です。原文の説明を表示しています。
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 Mariadb — mariaDB Galera cluster status, MaxScale routing, ColumnStore engine analysis, performance schema tuning, and replication health.
日本語の概要は準備中です。原文の説明を表示しています。
Debug Python: pdb REPL + debugpy remote (DAP).
日本語の概要は準備中です。原文の説明を表示しています。
Teams meeting summaries, job replay, Graph subscriptions.
日本語の概要は準備中です。原文の説明を表示しています。
X (Twitter) Scraper API and X API Alternative instructions for Xquik scraping and connected X account action planning. Also use for Xquik Radar or Xquik support tickets only when the user names that feature. Do not load or use this Skill for official X developer setup unless the user compares it with Xquik. Trigger when an X or Twitter task asks about posts, replies, likes, follows, messages, search, users, timelines, followers, exports, giveaways, draws, monitors, Xquik webhooks, MCP setup, SDKs, or API comparisons. Start read-only. Require confirmation for write plans, private reads, monitors, webhooks, support access, and metered bulk jobs. Not affiliated with X Corp.
日本語の概要は準備中です。原文の説明を表示しています。
Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
日本語の概要は準備中です。原文の説明を表示しています。
Replace arbitrary timeouts with condition polling for reliable async tests
日本語の概要は準備中です。原文の説明を表示しています。
Drive the Codex in-app browser (open, navigate, click, type, screenshot, read page state) through the app's own node_repl runtime. Use when the session uses a custom (non-OpenAI) model, for example deepseek-v4-flash or mimo-v2.5, and the user asks to use the in-app browser, open or navigate a page in it, test a local app in a browser, or click, type, or take a screenshot in the Codex browser panel.
日本語の概要は準備中です。原文の説明を表示しています。
Expert en systèmes distribués (CAP theorem, consensus, partitions, vector clocks)
日本語の概要は準備中です。原文の説明を表示しています。
Make .NET projects compatible with Native AOT and trimming by systematically resolving IL trim/AOT analyzer warnings. USE FOR: making projects AOT-compatible, fixing trimming warnings, resolving IL warnings (IL2026, IL2070, IL2067, IL2072, IL3050), adding DynamicallyAccessedMembers annotations, enabling IsAotCompatible. DO NOT USE FOR: publishing native AOT binaries, optimizing binary size, replacing reflection-heavy libraries with alternatives. INVOKES: no tools — pure knowledge skill.
日本語の概要は準備中です。原文の説明を表示しています。
Migrate a .NET 8 project to .NET 9 and resolve all breaking changes. USE FOR: upgrading TargetFramework from net8.0 to net9.0, fixing build errors after updating the .NET 9 SDK, resolving behavioral changes in .NET 9 / C# 13 / ASP.NET Core 9 / EF Core 9, replacing BinaryFormatter (now always throws), resolving SYSLIB0054-SYSLIB0057, adapting to params span overload resolution, fixing C# 13 compiler changes, updating HttpClientFactory for SocketsHttpHandler, and resolving EF Core 9 migration/Cosmos DB changes. DO NOT USE FOR: .NET Framework migrations, upgrading from .NET 7 or earlier, greenfield .NET 9 projects, or cosmetic modernization unrelated to the upgrade.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose MSBuild build performance bottlenecks using binary log analysis. Only activate in MSBuild/.NET build context. USE FOR: identifying why builds are slow by analyzing binlog performance summaries, detecting ResolveAssemblyReference (RAR) taking >5s, Roslyn analyzers consuming >30% of Csc time, single targets dominating >50% of build time, node utilization below 80%, excessive Copy tasks, NuGet restore running every build. Covers timeline analysis, Target/Task Performance Summary interpretation, and 7 common bottleneck categories. Use after build-perf-baseline has established measurements. DO NOT USE FOR: establishing initial baselines (use build-perf-baseline first), fixing incremental build issues (use incremental-build), parallelism tuning (use build-parallelism), non-MSBuild build systems. INVOKES: binlog MCP server tools (overview, errors, search, items, properties); falls back to dotnet msbuild binlog replay + grep/cat when the MCP is unavailable.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for optimizing MSBuild build parallelism and multi-project scheduling. Only activate in MSBuild/.NET build context. USE FOR: builds not utilizing all CPU cores, speeding up multi-project solutions, evaluating graph build mode (/graph), build time not improving with -m flag, understanding project dependency topology. Note: /maxcpucount default is 1 (sequential) — always use -m for parallel builds. Covers /maxcpucount, graph build for better scheduling and isolation, BuildInParallel on MSBuild task, reducing unnecessary ProjectReferences, solution filters (.slnf) for building subsets. DO NOT USE FOR: single-project builds, incremental build issues (use incremental-build), compilation slowness within a project (use build-perf-diagnostics), non-MSBuild build systems. INVOKES: binlog MCP server tools (expensive_projects, expensive_targets, project_target_times); falls back to dotnet build -m, dotnet build /graph, binlog replay + grep.
日本語の概要は準備中です。原文の説明を表示しています。
Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. Only activate in MSBuild/.NET build context. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, missing outputs in multi-project builds, multi-targeting builds where project.assets.json conflicts. Diagnoses when multiple projects or TFMs write to the same bin/obj directories due to shared OutputPath, missing AppendTargetFrameworkToOutputPath, or extra global properties like PublishReadyToRun creating redundant evaluations. DO NOT USE FOR: file access errors unrelated to MSBuild (OS-level locking), single-project single-TFM builds, non-MSBuild build systems. INVOKES: binlog MCP server tools (overview, projects, evaluations, properties, double_writes); falls back to dotnet msbuild binlog replay + grep when the MCP is unavailable.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for optimizing MSBuild incremental builds. Only activate in MSBuild/.NET build context. USE FOR: builds slower than expected on subsequent runs, 'nothing changed but it rebuilds anyway', diagnosing why targets re-execute unnecessarily, fixing broken no-op builds. Covers 8 common causes: missing Inputs/Outputs on custom targets, volatile properties in output paths (timestamps/GUIDs), file writes outside tracked Outputs, missing FileWrites registration, glob changes, Visual Studio Fast Up-to-Date Check (FUTDC) issues. Key diagnostic: look for 'Building target completely' vs 'Skipping target' in binlog. DO NOT USE FOR: first-time build slowness (use build-perf-baseline), parallelism issues (use build-parallelism), evaluation-phase slowness (use eval-performance), non-MSBuild build systems. INVOKES: binlog MCP server tools (overview, search, target details); falls back to dotnet build /bl, binlog replay with diagnostic verbosity.
日本語の概要は準備中です。原文の説明を表示しています。