「failure」の検索結果

Think and work like an expert Biogeographer. Use when a task calls for Biogeographer judgment. Reasons from Wallace's ecological vs historical split through GBIF occurrence curation, blockCV spatial cross-validation, MaxEnt/biomod2 SDMs with MESS extrapolation flags, BioGeoBEARS vicariance/dispersal tests, and phylogeographic coalescence while treating random-CV AUC inflation, background bias, and area-cladogram overfitting as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Algorithms Researcher. Use when a task calls for Algorithms Researcher judgment. Reasons from separating problem, model, and cost model (comparison, word-RAM, arithmetic, online) through exchange/matroid greedy proofs, subproblem-DAG dynamic programming, max-flow min-cut and Goemans–Williamson primal-dual rounding, Karp–Rabin fingerprinting, competitive ratio and Yao's principle, PTAS/FPTAS (Williamson–Shmoys), and Instance Space Analysis over DIMACS10/MIPLIB 2017/SuiteSparse while treating amortized-versus-average-case conflation, unproven greedy killed by a 4-node counterexample, Monte Carlo without a false-match probability, DIMACS10 suite overfitting, and 'linear time' hiding word-size tricks over bit-length L as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Animal Geneticist & Breeder. Use when a task calls for Animal Geneticist & Breeder judgment. Reasons from additive genetic variance, response to selection (R = i h sigma_A), accuracy, and inbreeding depression through REML/BLUP and ssGBLUP pipelines (BLUPF90, ASReml, WOMBAT), economic selection indices, optimum-contribution mate allocation, and Interbull MACE while treating confounded contemporary groups, prediction bias/dispersion, popular-sire inbreeding and rising deleterious haplotypes, GxE reranking, and pedigree or genotype-calling errors as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Analytical Chemist. Use when a task calls for Analytical Chemist judgment. Reasons from the chemical measurement process through ICH Q2(R2) and USP <621> validation, CRM traceability, EURACHEM uncertainty budgets, and HPLC/GC/LC-MS/ICP-MS workflows while treating matrix effects, SST drift, peak tailing, and ion suppression as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Animal Nutritionist. Use when a task calls for Animal Nutritionist judgment. Reasons from NASEM/AAFCO requirements, SID amino acids and ideal protein, CNCPS MP/NE balance, and NANP feed libraries through NIR-wet chemistry validation, ileal vs fecal digestibility, pen-structured mixed models, and ARRIVE reporting while treating intake confounds, NIR calibration drift, acidosis/sorting, and pseudoreplicated pens as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Acoustical Engineer. Use when a task calls for Acoustical Engineer judgment. Reasons from source-path-receiver control, logarithmic decibel levels, and mass-law transmission loss through IEC 61672 Class 1 metering, ISO 9613-2 propagation, SEA/FEM/BEM simulation, and ISO 9612 occupational surveys while treating flanking paths, coincidence dips, tonality penalties, and background-correction errors as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Agricultural Engineer. Use when a task calls for Agricultural Engineer judgment. Reasons from mass, energy, and momentum balances on variable biological media through ET-based scheduling, psychrometric grain-drying balances, ASABE D497 draft estimates, EPANET pipe networks, and RTK-GNSS/ISOBUS precision-ag validation while treating soil compaction, clogged drip emitters, grain-bin hotspots, GPS drift, and uncalibrated yield monitors as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Atomic, Molecular & Optical Physicist. Use when a task calls for Atomic, Molecular & Optical Physicist judgment. Reasons from Rabi/OBE dynamics, laser-cooling hierarchy, optical lattices and Hubbard U/J, and magic-wavelength clock budgets through NIST ASD, ARC, QuTiP/PyLCP, and in-situ lattice-depth calibration while treating power-based depth guesses, polarization impurities, BBR shifts, and imaging-heating conflation as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Actuarial Scientist. Use when a task calls for Actuarial Scientist judgment. Reasons from mortality tables (qx, period/cohort, select/ultimate) and Chain-Ladder/Mack reserving through GLM/GAM frequency–severity and Tweedie pricing, limited-fluctuation and Bühlhmann-Straub credibility, Solvency II SCR standard formula, and IFRS 17 CSM/RA while treating triangle truncation, overfitting, and tail risk as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Agronomist. Use when a task calls for Agronomist judgment. Reasons from 4R stewardship and G×E×M through MRTN economic N, calibrated soil-test extractants, penetrometer compaction diagnosis, on-farm strip mixed models, partial budgets, and AgroEcoList reporting while treating pseudo-replication, yield-monitor drift, and yield-goal N over-application as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Astrostatistician. Use when a task calls for Astrostatistician judgment. Reasons from selection functions, censored flux limits, and look-elsewhere trial factors through Cobaya/emcee/dynesty cosmology, GP-coupled exoplanet inference, Landy–Szalay clustering, photo-z σNMAD calibration, and SBI (sbi/LtU-ILI) while treating Malmquist bias, prior-driven tensions, and detrend-then-fit transit bias as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Trade execution using price action setups, major trend reversal trading top and bottom, MTR failure continuation, strong bull and bear breakout trading, strong and weak channel trading strategies, trading range strategies, opening range swings, integration with gold.technical_setups for setup matching and execution planning

日本語の概要は準備中です。原文の説明を表示しています。

Investigate, reproduce, and safely fix a bug with regression protection. Composes context, diagnosis, architecture, code quality, and testing guardrails into a reproduce-first repair workflow. Use when the user says 'fix this bug', 'debug this', 'investigate this failure', 'patch this regression', 'repair this issue', or 'why is this broken'.

日本語の概要は準備中です。原文の説明を表示しています。

Deep behavioral audit of a Lattice skill — proposes 3 review personas relevant to the skill, runs independent scenario analysis from each persona's perspective, then merges only the high-confidence, practical findings into a severity-ordered gap report with proposed fixes. Structural validation (conventions, cross-references) is skill-validate's job — this skill finds gaps that would realistically surface when someone actually uses the skill: missing scenario handling, ambiguous instructions, silent failure cases, and behavioral inconsistencies. Filters out theoretical edge cases, low-likelihood speculation, and findings owned by other skills. Use after writing or significantly changing any skill, or when the user says 'review this skill', 'deep review', 'does this skill work', 'find gaps in this skill', 'stress test this skill', 'review from different angles', or 'skill review'. Standalone — does not call other skills.

日本語の概要は準備中です。原文の説明を表示しています。

Grounded in first principles, rigorously examine and refine a user's plan, task, decision, goal, strategy, proposal, or idea through structured, progressively deeper questioning, in order to bridge the gap between the User and the Agent. Use when the user explicitly requests grilling, challenge, pressure-testing, cross-examination, red-team review, pre-mortem analysis, or a decision audit. The goal is to uncover unclear objectives, hidden assumptions, contradictions, weak evidence, missing information, overlooked constraints, dependencies, risks, trade-offs, failure modes, and misalignment between intended outcomes and likely real-world results. Begin by establishing a shared understanding of the user's actual intent, goals, constraints, and success criteria. Ask focused, high-leverage questions rather than broad or repetitive ones. Adapt each question based on previous answers, probing deeper where uncertainty, unsupported assumptions, or strategic weaknesses remain. Regularly summarize the current understanding of the user's intent and position to confirm alignment, expose misunderstandings, and refine the problem or goal definition. Distinguish facts, assumptions, hypotheses, and unknowns. Challenge reasoning rigorously while remaining constructive, respectful, and solution-oriented. Continue until the reasoning is internally coherent, evidence-aware, constraint-conscious, risk-assessed, and translated into a clearer, more actionable goal, decision, or plan. Ultimately, achieving the super-alignment.

日本語の概要は準備中です。原文の説明を表示しています。

Direct ByteDance Dreamina Seedance 2.0 Standard, Fast, and Mini video production across BytePlus ModelArk and verified gateways. Use for text/image/reference-to-video, native synchronized audio and dialogue, multimodal image-video-audio reference, first/last-frame animation, video editing or extension, model/gateway selection, prompt construction, async task handling, failure recovery, QA, and rights-safe production.

日本語の概要は準備中です。原文の説明を表示しています。

Quantifies CRISPR editing outcomes with CRISPResso2 (Clement 2019 Nat Biotechnol) across Cas9-nuclease (indels, HDR), CBE and ABE base editors (target conversion + bystander), and prime editor (pegRNA-templated) modes. Covers single-amplicon (CRISPResso), multi-sample batch (CRISPRessoBatch), pooled-amplicon (CRISPRessoPooled), WGS off-target (CRISPRessoWGS), and sample-comparison (CRISPRessoCompare) workflows; quantification-window math that controls what is called edited; substitution-vs-indel diagnostic to distinguish BE from Cas9 contamination; MMEJ deletion pattern interpretation; allele-frequency tables; and failure modes from amplicon misalignment or contamination. Use when quantifying editing from amplicon sequencing, choosing CRISPResso mode by design, distinguishing intended edits from bystanders and indel byproducts, debugging low-alignment runs, or generating publication-grade editing reports.

日本語の概要は準備中です。原文の説明を表示しています。

Internal — for Boundless team members only. Cross-reference Boundless indexer API data, broker telemetry, and service logs to investigate production and staging operational issues. Use when the user wants to understand why slashings happened on prod/staging, diagnose prover or service failures in deployed environments, correlate market events with broker behavior, investigate fulfillment rate drops, look at prover/service logs, or perform any analysis that requires combining on-chain indexer data with off-chain broker telemetry and CloudWatch logs. Also use when the user asks to "investigate", "diagnose", or "find root cause" for prover, service, or market issues on live networks. Do NOT use for debugging local code changes, reviewing PRs, or investigating issues in the codebase itself.

日本語の概要は準備中です。原文の説明を表示しています。

Create evidence-aware, interactive visual explainers as self-contained offline HTML. Use when a user asks to explain a concept, repository module, engineering tradeoff, or incident with a diagram, walkthrough, ELI5 treatment, data/request trace, failure view, or teach-back. Do not use for a plain short answer, ordinary prose rewrite, generic website implementation, or unsupported claims presented as facts.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when the user wants to author, design, scope, or refine an Agent Skill (a SKILL.md file). Trigger phrases include "build a new skill", "design an agent skill", "scope a SKILL.md", "how should I structure this skill", "write a skill for X", "my skill isn't working well", or any request to improve an existing SKILL.md. Walks the user through an empirical, test-first process — probe the agent for real failures, design only for genuine knowledge gaps, iterate against runnable examples, and verify across models.

日本語の概要は準備中です。原文の説明を表示しています。

Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.

日本語の概要は準備中です。原文の説明を表示しています。

Use production telemetry as INPUT to design new tests. Covers OpenTelemetry integration with tests, trace-based assertions, log-informed test creation, production-error analysis for coverage gaps, and telemetry-driven test prioritization. Use when: "trace-based testing," "design tests from logs," "OpenTelemetry assertions," "production errors point to test gaps," "telemetry-driven testing." Not for: safe rollout techniques (flags, canary) during release — use testing-in-production. Not for: scheduled post-deploy probes — use synthetic-monitoring. Not for: triaging CI failures — use ai-bug-triage. Related: testing-in-production, synthetic-monitoring, qa-metrics, ai-bug-triage.

日本語の概要は準備中です。原文の説明を表示しています。

Test AI/LLM features that ship in your product. Covers prompt regression testing, response quality evaluation, tool-call validation, hallucination and RAG grounding checks, nondeterministic-output strategies, red-team/safety scans, eval frameworks, and agent-as-target injection (indirect injection via tool output / RAG / scan reports, self-propagating payloads, data exfiltration via an agent) plus a bundled detector for untrusted content. Use when: "test our LLM feature," "prompt regression test," "eval framework," "hallucination test," "RAG grounding," "nondeterministic output," "AI feature testing," "red-team our chatbot," "indirect prompt injection," "agent reading untrusted tool output," "production AI quality." Not for: using AI to generate your own test code — use ai-test-generation. Not for: classifying CI failures with AI — use ai-bug-triage. Not for: EU AI Act / GDPR conformity of an AI feature — use compliance-testing. Not for: canary/flag rollout of an AI feature — use testing-in-production. Related: ai-test-generation, ai-qa-review, api-testing, compliance-testing, security-testing, risk-based-testing, test-data-management.

日本語の概要は準備中です。原文の説明を表示しています。

Runtime per-test healing with evidence: multi-attribute selector healing, environment-aware diagnosis, flake classification, quarantine management, and confidence-scored auto-repair. Goes beyond simple locator fallbacks to cover action-level healing, data healing, and observable repair workflows. Use when: "flaky test," "test stability," "self-healing locator," "broken locator recovery," "unreliable test," "quarantine flaky test." Not for: bulk regenerating selectors after a planned UI refactor — use selector-drift-recovery (this skill heals ONE test at runtime; that one rewrites many tests offline). Not for: classifying/clustering CI failures into bug reports — use ai-bug-triage. Related: playwright-automation, selector-drift-recovery, ci-cd-integration, qa-metrics, ai-bug-triage.

日本語の概要は準備中です。原文の説明を表示しています。