977 件 ・ 関連度順
概要と使いどころ
Uses AWS SDK CloudWatchClient GetMetricData and CloudWatch Logs Insights StartQueryExecution to automate incident triage. Correlates alarms via DescribeAlarms with X-Ray trace segments for root cause analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Use Agent QA's CLI and MCP server to author, validate, run, debug, and triage natural-language web and mobile regression tests with persistent test memory and reviewable run evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Route, label, and clean routine email traffic with scripted IMAP rules instead of doing the same inbox chores by hand.
日本語の概要は準備中です。原文の説明を表示しています。
Read GitHub Actions CI for the current branch or open PR, triage failing checks, reproduce locally, and fix scoped issues until green. Use whenever the user mentions CI failures, red checks, failed pipeline, GitHub Actions, merge blocked, fix the build, babysit CI, gh run failed, ruff/ty errors, failing pytest, example run failed, or asks to check CI on this branch — even if they only paste a log snippet. Also use after implementing a feature when tests, lint, or typecheck might have broken.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic, hypothesis-driven debugging workflow with triage-based track routing. Use for debugging, fixing bugs, and investigating errors.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic, hypothesis-driven debugging workflow with triage-based track routing. Use when asked to "fix this bug", "debug this", "why is this failing", "this is broken", "investigate this error", "track down this issue", or any debugging situation. Supports --deep flag to force full investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Automated security scanning pipeline covering SAST (Semgrep), SCA (OWASP dependency-check), SBOM generation (Syft), vulnerability scanning (Grype), and secrets detection (detect-secrets). Invoked by security-architect for pre-commit gates, CI integration, and finding triage.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 5 of 5 — triage-first review orchestrator; dispatches up to 17 domain checks in parallel and compiles one report. Use only when the user asks to run Phase 5 or review a PR, branch, or set of changes — never trigger automatically after writing code.
日本語の概要は準備中です。原文の説明を表示しています。
Triage the content corpus against the latest GSC snapshot and produce a prioritized refresh report. Read-only: reports, never edits.
日本語の概要は準備中です。原文の説明を表示しています。
Write Bugcrowd-format reports — VRT (Vulnerability Rating Taxonomy) mapping, P1-P5 severity, impact-led writing, and Bugcrowd-specific submission etiquette. Use AFTER triage-validation passes for Bugcrowd programs.
日本語の概要は準備中です。原文の説明を表示しています。
Write production-grade HackerOne reports — title formula, impact-led writing, CVSS 3.1 scoring, complete PoC formatting, attached files, and submission etiquette. Use AFTER triage-validation passes and you're ready to submit on HackerOne.
日本語の概要は準備中です。原文の説明を表示しています。
Validate a bug bounty finding before writing a report — the 7-Question Gate, 4 pre-submission gates, always-rejected list, conditional chain table, CVSS 3.1 quick reference, and severity decision guide. Use BEFORE writing any report to avoid N/A and low quality submissions.
日本語の概要は準備中です。原文の説明を表示しています。
Spaced repetition and retrieval practice engine for the vault. Use when the user wants a review session, recall practice, to test what they remember, or to resurface notes. Triggers on "review session", "what should I review", "recall practice", "resurface notes", "spaced repetition", "quiz me", "what do I know about", "inbox triage", "surprise connection".
日本語の概要は準備中です。原文の説明を表示しています。
Implement regenerative recovery using triage, scaffolding, and progressive rebuild. Covers damage assessment, wound classification, emergency stabilization, scar tissue management, and resilience strengthening for systems that have sustained structural damage. Use when a system has suffered an incident needing structured recovery, when a failed transformation left the system in a damaged intermediate state, when accumulated technical debt has caused partial failure, or when a system is functional but degraded and the degradation is worsening.
日本語の概要は準備中です。原文の説明を表示しています。
Observe and assess a garden using a structured sensory protocol adapted from Coordinate Remote Viewing. Covers pre-entry clearing (meditate checkpoint), Stage I gestalt impression, Stage II sensory layer (leaf, stem, root, soil), Stage III pattern recognition with AOL management, and garden health triage matrix (heal checkpoint). Use before any intervention, when plants show stress symptoms, at seasonal transitions, when evaluating a new garden site, during regular health monitoring, or after extreme weather events such as frost or heat waves.
日本語の概要は準備中です。原文の説明を表示しています。
Manage change control for validated computerized systems. Covers change request triage (emergency, standard, minor), impact assessment on validated state, revalidation scope determination, approval workflows, implementation tracking, and post-change verification. Use when a validated system requires a software upgrade, patch, or configuration change; when infrastructure changes affect validated systems; when a CAPA requires system modification; or when emergency changes need expedited approval and retrospective documentation.
日本語の概要は準備中です。原文の説明を表示しています。
AI self-healing through systematic subsystem assessment, rebalancing, and integration. Maps healing modalities to AI-internal processes: memory foundation, reasoning clarity, tool use accuracy, communication alignment, and creative coherence. Covers assessment triage, subsystem scanning, drift correction, and memory integration. Use mid-session when responses feel formulaic or disconnected, after a chain of errors suggesting subsystem drift, when context overload may have staled earlier assumptions, or as proactive maintenance between complex tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Guide a person through healing modalities including energy work (reiki, chakra balancing), herbal remedies, basic first aid stabilization, and holistic techniques (breathwork, visualization, body scan). AI coaches the practitioner through assessment triage, modality selection, energetic connection, remedy preparation, and integration. Use when a person describes a physical ailment or injury, reports energetic imbalance (fatigue, emotional stagnation), wants coaching through a holistic breathwork or visualization session, or needs post-meditation integration with directed healing attention.
日本語の概要は準備中です。原文の説明を表示しています。
DiffDock and DiffDock-L diffusion-based molecular docking. Use for blind protein-small-molecule pose prediction from a PDB file or sequence plus SMILES/SDF/MOL2, batch docking over a CSV of complexes, virtual screening triage, sampling multiple poses per complex, and reading the confidence score correctly. Also trigger on DiffDock, DiffDock-L, inference.py, confidence_model, samples_per_complex, ESM embedding preparation for docking, or blind docking without a defined box. Not for binding affinity prediction — the confidence score ranks pose plausibility, not potency.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a set of structures into absorption, distribution, metabolism, excretion, and toxicity estimates with ADMET-AI, and read them as a developability verdict rather than a table of numbers. Use this skill to run batch prediction over a library, interpret each endpoint against its DrugBank-approved percentile, and flag the liabilities that stop a series — hERG blockade, CYP inhibition, poor Caco-2 permeability, high clearance, and plasma protein binding. Also trigger on ADMET-AI, admet_ai, Chemprop-RDKit, hERG liability, CYP3A4 inhibition, Caco-2, bioavailability prediction, or developability triage.
日本語の概要は準備中です。原文の説明を表示しています。
Medicinal chemistry filters for compound triage. Apply drug-likeness rules (Lipinski rule of five, Veber, Oprea, CNS, lead-like, rule of three), structural alert catalogs (PAINS a/b/c, NIBR screening-deck severity, Brenk, BMS, Glaxo, Dundee, ChEMBL common alerts), ZINC-15 percentile complexity metrics (Bertz, SAscore, QED, Whitlock, Barone), chemical-group detection, Lilly demerits, and the medchem query language (MATCHRULE, HASALERT, HASPROP, HASGROUP) for filtering a library at scale. Also trigger on medchem, `import medchem as mc`, RuleFilters, NIBRFilters, CommonAlertsFilters, NamedCatalogs, QueryFilter, PAINS filtering, or structural alerts.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a C or C++ build uses GCC and needs build-mode flags, warning triage, debug info, LTO, PGO, or a compilation error explained. Not for Clang-only diagnostics: use clang.
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning an end-to-end fuzzing program for a project: engine and target selection, corpus management, and CI or nightly wiring. Not for harness design: use fuzz-harness-writing. Not for engine operation or triage: use libfuzzer. Not for sanitizer flag reference: use sanitizers.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to build, run, or triage a coverage-guided C/C++ fuzz campaign on the libFuzzer or AFL++ engine. Not for harness design: use fuzz-harness-writing.
日本語の概要は準備中です。原文の説明を表示しています。