「iab」の検索結果

Hook system fundamentals — all events, configuration structure, matchers per event type, environment variables, execution behavior, security, and debugging. Use when creating hooks, understanding hook events, matchers, configuration locations, environment variables, or troubleshooting hook issues.

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

This skill should be used when the user encounters "var-annotated" mypy errors, asks to "fix var-annotated errors", "add type annotations to variables", or mentions "Need type annotation for" errors. Provides workflow for fixing missing variable type annotations while respecting forbidden type constraints (no Any, dict[str, Any], list[Any], etc.).

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

Reads model uncertainty from token log-probabilities. Covers collecting logprobs and aggregating multi-token labels, confidence tiers and margins for triage, calibration assessment with ECE, Brier scores, and reliability diagrams against human labels, responsible downstream use of confidence, and reproducibility archives. Use when the user asks about classifier confidence by item, logprobs, top-k tokens, calibration, ECE, Brier, reliability diagrams, or routing low-confidence cases to human review. Codebook and validation design go to text-classification.

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

Turns a theory into falsifiable, pre-registerable hypotheses, covering the DGP and DAG, identification, SATE versus PATE, counterfactual and directional framing, named estimands, justified SESOIs, the choice among NHST, equivalence, interval, and minimum-effect tests, scope conditions, and primary, secondary, and exploratory tiers. Use when the user asks to turn a research question or theory into hypotheses, whether a prediction is falsifiable, what the estimand is, or how to predict a null. Framing goes to narrative-building, the plan to pre-registration-writing.

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

Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.

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

Challenge a thesis by playing "Devil's Advocate" (Latin: "Advocatus Diaboli"). Use when the user wants a thesis or statement relentlessly challenged or criticised.

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

Use when refactoring code with poor names, when asked to improve naming, or when a user struggles to name a class/method/variable. Symptoms include -Manager/-Util suffixes, single-letter variables, process/handle/do verbs, primitive obsession, god methods with multiple responsibilities. Two modes — audit (broad scan, list opportunities) and improve (walk one specific identifier through the process).

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

Assesses going-concern viability with 13-week cash flow models, liquidity runway, and critical vendor analysis. Use when evaluating liquidity crises, building 13-week models, or assessing near-term solvency.

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

Evaluates environmental liability exposure with remediation cost estimation, regulatory compliance requirements, and insurance coverage assessment. Use when analyzing environmental liabilities, estimating cleanup costs, or assessing environmental risk.

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

Evaluates uptier exchanges, drop-down transactions, and covenant-stripping maneuvers as aggressive liability management tools. Use when analyzing LMTs, evaluating creditor-on-creditor violence, or assessing cooperation agreement strategies.

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

Evaluates asset retirement and decommissioning liabilities with cost estimation, timing analysis, and funding adequacy assessment. Use when analyzing decommissioning costs, evaluating ARO exposure, or assessing abandonment liability.

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

Deploy and manage Netlify projects using Next.js with serverless functions, environment variables, and continuous deployment. Use this skill when working with Netlify deployments, configuring netlify.toml, managing Netlify Functions, debugging webhooks, setting environment variables, or troubleshooting deployment issues for Next.js applications on Netlify. Essential for Twilio-Aldea and similar serverless SMS/telephony projects. v2.0 includes official Netlify documentation, production patterns from Twilio-Aldea (webhook timeout solutions, background functions), and TypeScript code examples.

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

8つの専門エージェント（市場規模分析・トレンド調査・競合インテリジェンス・投資シグナル・日本市場・ユーザー需要分析・規制調査・データ検証）が ディスカッション型でアプリ/デジタルプロダクトの市場調査を実施するスキル。 エージェント同士が対話・批判し合い、data-critic がライブモデレーターとして矛盾を検出・収束を判定する。 トライアンギュレーション（データ・方法論・調査者・理論の4種類）をディスカッションに組み込み、 確証バイアスを排除した信頼度付きレポートを出力する。 Gate 1（全員参加の合意形成）→ Gate 2（最終検証 + Devil's Advocate）の2段階ゲートで品質を担保。 コンテキストファイルで過去のセッションを引き継げる。 Use when: 市場調査をしたい、TAM/SAM/SOMを算出したい、市場の成長性を調べたい、 参入タイミングを判断したい、競合市場を分析したい、規制リスクを調べたい。 Triggers: "市場調査", "market research", "TAM", "SAM", "SOM", "市場規模", "市場分析", "market analysis", "参入", "market entry", "市場性", "market viability", "市場トレンド", "market trend"

Deploy a Next.js application to Vercel. Covers project linking, environment variables, preview deployments, custom domains, and production deployment configuration. Use when deploying a Next.js app for the first time, setting up preview deployments for pull requests, configuring custom domains, or managing environment variables in a production Vercel deployment.

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

Implement circuit breaker logic for agentic tool calls — tracking tool health, transitioning between closed/open/half-open states, reducing task scope when tools fail, routing to alternatives via capability maps, and enforcing failure budgets to prevent error accumulation. Separates orchestration (deciding what to attempt) from execution (calling tools), following the expeditor pattern. Use when building agents that depend on multiple tools with varying reliability, designing fault-tolerant agentic workflows, recovering gracefully from tool outages mid-task, or hardening existing agents against cascading tool failures.

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

Number antibody variable domains, annotate CDRs, and assess developability from sequence. Use this skill to apply IMGT, Kabat, Chothia, Martin, or AHo numbering with ANARCI, delimit CDRs and framework regions, scan for chemical liabilities (N-glycosylation sequons, deamidation NG, isomerisation DG, oxidation, unpaired cysteine, fragmentation), compute pI, net charge, extinction coefficient and hydrophobicity, and plan humanisation by CDR grafting. Also trigger on antibody, nanobody, VHH, scFv, Fab, CDR, framework, ANARCI, abnumber, IgBLAST, OAS, SAbDab, humanization, Vernier residues, or developability.

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

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.

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

Use when skill or knowledge activation is unreliable, or setup reaches activation reliability. Not for remote, credential, publish, deploy, or irreversible changes.

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

Before any multi-step work with a stated goal — a feature, a bugfix spanning multiple files, a QA sweep, a doc draft + iterations, a multi-day investigation — create an ATO Mission instead of doing it via bare `ato dispatch` calls. A Mission persists the goal + the verifiable success criteria, lets the coordinator tick drive the work across days, captures every event in a structured audit trail (SQLite + markdown narrative), and integrates parallel agents' work via merge strategies. Complement to `ato-warroom` (the cross-family decision before you start) and `ato-review` (the post-code-diff review). Missions is where multi-step work LIVES; war-rooms are where decisions ABOUT it get made; reviews are where the resulting commits get vetted. Fires when: the work has more than one decision point, a verifiable end state, or runs across more than one session. Use it for any ATO development that doesn't fit in a single dispatch.

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

Secure environment variable management with Varlock. Use when handling secrets, API keys, credentials, or any sensitive configuration. Ensures secrets are never exposed in terminals, logs, traces, or Claude's context. Trigger phrases include "environment variables", "secrets", ".env", "API key", "credentials", "sensitive", "Varlock".

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

Use when rating a source with the NATO Admiralty Scale, the user asks "is this reliable?" / "rate this source", or the tradecraft pipeline calls for source assessment before publishing. Reliability A-F, credibility 1-6.

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

Use when the user asks about initial access brokers (IABs), the access-listing market, ransomware-feeding-IAB pipelines, specific broker handles, or how access is priced and packaged. Self-updating knowledge cell.

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

Design reliable, safe, and trustworthy agent systems that fail gracefully and operate within bounds. Use when building guardrails, handling edge cases, preventing harmful outputs, monitoring for failures, implementing safety constraints, or designing error recovery. Covers failure modes, constraint systems, oversight mechanisms, and safety validation.

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

Generate Azure environment monthly report (Markdown + PowerPoint) from Azure Advisor and Cost Management API. Use when creating Advisor recommendations report, cost trend analysis, or security/reliability assessment for a customer subscription. Triggers on 'Advisor report', 'Azure monthly report', 'subscription report', 'Azure環境レポート', '簡易月次レポート'.