554 件 ・ 関連度順
概要と使いどころ
Load when diagnosing a bug, exception, regression, wrong result, failing flow, or unknown root cause in repository code using callers/callees, execution flows, recent changes, and impact analysis; not for implementing a known fix without investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Time-boxed throwaway investigation to answer one hard question. Use when facing technical uncertainty before committing to a frontier item or scoped slice — the output is knowledge, not production code.
日本語の概要は準備中です。原文の説明を表示しています。
Start work on a Jira ticket by fetching ticket details, creating a properly named feature branch, and beginning codebase investigation. Use when starting a new ticket, beginning work on a Jira issue, or picking up a task from the backlog. Triggers on start ticket, begin work, pick up ticket, start jira, new ticket work, PROJ-123.
日本語の概要は準備中です。原文の説明を表示しています。
- Entry point for open-source intelligence, investigation and verification work. Use when asked to investigate, research, verify, vet, check out, look up, background-check, trace, attribute or find someone or something; when a request involves due diligence, KYC or KYB, counterparty or vendor risk, sanctions and PEP screening, AML, fraud, business email compromise
日本語の概要は準備中です。原文の説明を表示しています。
- Turn findings into a defensible intelligence product — BLUF key judgements, standardised estimative probability language, per-claim sourcing with timestamps and archived copies, separated observation, inference and assessment,… Use when writing an intelligence report, due-diligence memo, evidence pack or executive summary, or when asked to write up an investigation so it survives challenge
日本語の概要は準備中です。原文の説明を表示しています。
- Start-here router and tradecraft baseline for any investigation into a person, company, domain, image or selector.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate comprehensive SEO work across technical, content, schema, backlinks, local, ecommerce, programmatic SEO and AI-search/GEO. Use for full-site audits, SEO plans, or multi-specialist SEO investigations.
日本語の概要は準備中です。原文の説明を表示しています。
Apply poteto's rigorous engineering workflow to non-trivial coding, investigation, review, migration, and verification tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Crowdstrike — crowdStrike Falcon endpoint detection and response, threat intelligence, host management, and incident investigation. Covers detection queries, host inventory, IOC searches, real-time response sessions, and vulnerability assessment. Use when investigating security incidents, reviewing endpoint health, analyzing threat detections, or managing CrowdStrike Falcon sensors.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Chronicle — google Chronicle SIEM security operations, threat detection, asset investigation, and log analysis. Covers UDM search queries, detection rule management, asset and IOC lookups, reference list management, and retrohunt execution. Use when investigating security events, reviewing detection rules, searching for IOCs, or analyzing Chronicle data ingestion health.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Bmc Helix — bMC Helix ITSM platform management covering incident management, problem management, change management, and CMDB operations. Use when creating or updating incidents with categorization and assignment, managing problem investigation workflows, processing change requests through CAB approval, or querying CMDB for infrastructure configuration items and relationships.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Xray — aWS X-Ray trace analysis, service map generation, fault and error analysis, sampling rule management, and latency investigation. Covers trace summaries, segment analysis, annotation-based filtering, and group configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Aws Step Functions — aWS Step Functions execution analysis, state machine management, error tracking, and performance optimization. Covers execution history, failure investigation, state transition metrics, Express vs Standard comparison, and workflow visualization.
日本語の概要は準備中です。原文の説明を表示しています。
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 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 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 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 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 Aws Config — aWS Config compliance dashboard, rule evaluation status, conformance pack management, and resource timeline analysis. Covers configuration recorder status, compliance summary, non-compliant resource investigation, remediation tracking, and aggregator management.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, execute, and document validation, verification, and transfer of analytical procedures under the governing framework - ICH Q2(R2) and Q14, USP <1220>/<1225>/<1226>, ICH M10 bioanalytical, CLSI EP, or ISO/IEC 17025. Use for HPLC, LC-MS/MS, GC, CE, ICP-MS, dissolution, qNMR, qPCR, NIR, and ligand binding or cell-based assays whenever the question is whether a procedure is fit for its intended purpose. Triggers include "method validation", "analytical method validation", "AMV", "validation protocol", "acceptance criteria", "linearity", "reportable range", "accuracy and precision", "repeatability", "intermediate precision", "recovery", "LOD", "LOQ", "detection limit", "quantitation limit", "specificity", "robustness", "method transfer", "method comparison", "Deming", "Passing-Bablok", "Bland-Altman", "equivalence testing", "OOS investigation", "ICH Q2", "Q2(R2)", "Q14", "USP 1225", "ICH M10", "incurred sample reanalysis", "ISR", "CLSI EP", and any request to show that an assay works.
日本語の概要は準備中です。原文の説明を表示しています。
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
日本語の概要は準備中です。原文の説明を表示しています。
Configure and collect crash dumps for modern .NET applications. USE FOR: enabling automatic crash dumps for CoreCLR or NativeAOT, capturing dumps from running .NET processes, setting up dump collection in Docker or Kubernetes, using dotnet-dump collect or createdump. DO NOT USE FOR: analyzing or debugging dumps, post-mortem investigation with lldb/windbg/dotnet-dump analyze, profiling or tracing, or for .NET Framework processes.
日本語の概要は準備中です。原文の説明を表示しています。
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. Only activate in MSBuild/.NET build context. USE FOR: adding /bl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ / .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead). INVOKES: shell commands (dotnet build /bl:{}).
日本語の概要は準備中です。原文の説明を表示しています。
Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing.
日本語の概要は準備中です。原文の説明を表示しています。