793 件 ・ 関連度順
概要と使いどころ
Assesses physical and transition climate risk for CRE properties and portfolios. Translates hazard exposure (flood, wind, wildfire, extreme heat, sea level rise) and regulatory/market shifts into financial impacts on NOI, cap rates, insurance costs, and tenant demand. Produces dollar-denominated risk, not abstract hazard scores.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze agricultural climate risk systems for weather impact modeling, crop insurance, drought/flood prediction, soil moisture, and carbon tracking. Use when: 'assess crop climate risk', 'evaluate weather yield models', 'review crop insurance integration', 'audit drought prediction', 'check carbon sequestration tracking', 'analyze farm adaptation planning', 'evaluate DSSAT or APSIM models'.
日本語の概要は準備中です。原文の説明を表示しています。
Regulatory compliance guidelines for life insurance policy administration transactions. Use when processing address changes (state-change impacts), beneficiary changes (community property, ERISA, minors), or any transaction that may trigger compliance review. Covers NAIC model regulations, state-specific rules, OFAC screening, and suitability requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Route new policy briefing, policy update, regulatory update deck, regulatory change deck, compliance change summary, legal update deck, or legal/product policy presentation requests here before generic AIPPT. Use this whenever the user wants a new policy interpretation deck with timelines, impacts, risks, and recommended actions. Do not use this scene pack for email memos, FAQ-only outputs, compliance copy polishing, or non-deck legal writing.
日本語の概要は準備中です。原文の説明を表示しています。
Map current AI safety controls — filter inventory, coverage gaps, latency impact, incident history. Use when asked "what AI safety controls do we have", "find guardrail coverage gaps", or "map our filters".
日本語の概要は準備中です。原文の説明を表示しています。
Designing interventions, systems, and policies for sustainability. Covers renewable energy (solar, wind, hydro, geothermal), sustainable agriculture (agroecology, permaculture, integrated pest management), conservation strategies (protected areas, corridors, rewilding), lifecycle analysis, circular economy principles, and policy instruments (carbon pricing, cap-and-trade, regulation). Use when evaluating or designing interventions that aim to reduce environmental impact while maintaining human well-being.
日本語の概要は準備中です。原文の説明を表示しています。
Human modification of Earth's systems and the geographic dimensions of environmental change. Covers climate change science (greenhouse effect, feedback loops, projections), deforestation and land use change, desertification and soil degradation, water resource management, biodiversity loss and conservation geography, pollution and environmental justice, and sustainability frameworks. Use when reasoning about human impacts on the environment, environmental policy, conservation planning, climate adaptation, or the spatial distribution of environmental risks.
日本語の概要は準備中です。原文の説明を表示しています。
Climate physics, forcing, feedback, and attribution. Covers the greenhouse effect and radiative forcing, climate sensitivity, fast and slow feedbacks, the paleoclimate record, detection and attribution science, regional climate impacts, and the distinction between weather, climate variability, and forced climate change. Use when reasoning about global warming mechanisms, interpreting temperature or CO2 records, evaluating attribution claims for extreme events, or distinguishing signal from natural variability.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a skill by running a paired probe — the same task once with the skill loaded and once without — segment both traces into goal-directed phases, align phases, and emit a SIP report (surface anchoring, template copy, excess planning, task recovery, off-task artifact). Use whenever a skill is created, modified, or proposed for retirement. Pass-rate is BLIND to most skill effects: CTA (arxiv 2605.11946v1) shows a single skill can produce 522 measurable behavioural changes across 49 tasks while pass-rate moves only +0.3%. Triggers: "audit this skill", "is this skill helping", "retire skill", "before shipping skill", "behavioural impact of skill X", or any skill review event.
日本語の概要は準備中です。原文の説明を表示しています。
ANIMA as limit construction over condensed skill applications. Formalizes prediction markets as belief ANIMAs, structure dishes as condensation media, and impact as equivalence class change. Use for understanding agency at maximum entropy, compositional world modeling, or applying Scholze-Clausen condensed mathematics to AI.
日本語の概要は準備中です。原文の説明を表示しています。
Validate whether an implementation plan can achieve its stated outcome before execution. Use to check requirement coverage, task contracts, dependencies, data/artifact flow, testability, ownership, impact coverage, and executable ordering without checking whether implementation already exists.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesis step in the multi-angle technical research pipeline. Receives structured outputs from all four research angles (api-state, ecosystem-research, impact-measurement, codebase-auditor), applies cross-angle signal weighting and conflict resolution, and produces a single synthesized Research section. Invoked by the technical-researcher orchestrator after all angle skills complete. Returns content to the orchestrator — does not write to the backlog.
日本語の概要は準備中です。原文の説明を表示しています。
Grooms a GitHub milestone for parallel execution — batch-grooms ungroomed items, assesses scope gaps, analyzes cross-item dependencies via Impact Radius overlap, builds conflict groups, assigns items to execution waves, and persists the dispatch plan via dispatch_create_plan MCP tool. Calls dispatch_wave_start per wave to register state. Use when preparing a milestone for /work-milestone execution. Pass the milestone number as the first argument. Requires milestone items assigned via /group-items-to-milestone.
日本語の概要は準備中です。原文の説明を表示しています。
One-line definitions of development-harness (dh) plugin terminology — RT-ICA, ARL, SAM, the S1-S7 pipeline stage names, Impact Radius — each with a pointer to its canonical source file. Use when a dh skill, agent, or workflow step references a term without defining it, before guessing what the term means from its observed outputs, or when asked what a dh concept or acronym stands for.
日本語の概要は準備中です。原文の説明を表示しています。
Development harness plugin documentation index. Use when looking up SAM pipeline, backlog lifecycle, SDLC layers, task/plan schema, plan artifacts, quality gates, impact analysis, or dispatch schema documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Track and analyze US government shutdown liquidity impacts by monitoring TGA (Treasury General Account), bank reserves, EFFR, and SOFR data from FRED API. Use when user wants to (1) analyze current or past government shutdown effects on financial markets, (2) track liquidity conditions during fiscal policy disruptions, (3) assess "stealth tightening" effects, (4) compare shutdown episodes across different monetary policy regimes (QE vs QT), or (5) generate liquidity stress reports with historical context. Recommended usage frequency is weekly on Wednesdays after TGA/reserve data releases.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for journal recommendation, 选刊, 投稿期刊筛选, 期刊匹配, 适合投稿的期刊, 投哪个期刊, or wants 3-5 suitable journals for a manuscript based on an abstract, discipline, CAS/JCR ranking, impact factor, Aims & Scope, review speed, OA/APC, and publication-risk checks.
日本語の概要は準備中です。原文の説明を表示しています。
Expert error coordinator specializing in distributed error handling, failure recovery, and system resilience. Masters error correlation, cascade prevention, and automated recovery strategies across multi-agent systems with focus on minimizing impact and learning from failures.
日本語の概要は準備中です。原文の説明を表示しています。
Your Personal Finance Manager for Canadians — an AI financial planning partner that conducts thorough financial interviews, builds complete plans, generates interactive dashboards, and provides ongoing coaching. Use this skill whenever someone asks about budgeting, saving, investing, debt strategy, retirement planning, tax optimization, government benefits, insurance, RRSPs, TFSAs, RESPs, CPP, OAS, or any aspect of personal finance in a Canadian context. Also triggers for "should I buy this?", "can I afford this?", financial check-ins, plan updates, life change impacts on finances, or any request to build or review a financial plan. Even if the user just says "help me with my money" or "I need a budget", this skill should activate. Canada-focused.
日本語の概要は準備中です。原文の説明を表示しています。
Write the postmortem for an incident, in its incident channel, once it is mitigated or resolved. Use on "write up this incident", "postmortem", "incident summary", "what happened here for people who weren't around", "draft the retro", or when the oncall memory says incidents of this severity get one. Reads the incident channel (and the alert thread it came from), the investigation findings and the data behind them, and writes a one-screen, zero-context write-up: what happened, impact with numbers, detection, timeline with durations, why it happened, what fixed it, follow-ups with proposed owners, and one before/during/after chart. Posted and pinned in the incident channel as its final pinned post, with edit requests updating that one pinned post in place — unless the person or the team's conventions say write-ups live elsewhere, in which case it is written there and only a link is posted, nothing pinned. A person edits and publishes it; never assigns blame.
日本語の概要は準備中です。原文の説明を表示しています。
Run the oncall handoff for a rotation window — the whole handoff, not just a document: build the summary (what the incoming oncall needs first, what's still open, incidents with impact numbers, alert and page counts, hygiene suggestions, every number traceable to a source), post it for the outgoing oncall to correct, walk the incoming oncall through the open items in the thread, update the list as they respond, and note when they acknowledge. Runs mainly in the team's standing oncall / monitoring channel, normally as a scheduled routine firing at rotation change so the report is waiting when the shift turns over; can also be run by hand and works from an incident channel. Use when a handoff routine fires, or on "handoff", "hand over", "oncall summary", "weekly oncall report", "what happened this shift / this week". Re-running for the same window updates the report rather than duplicating it. Unattended runs carry a run-summary block and at least one chart.
日本語の概要は準備中です。原文の説明を表示しています。
Post a sitrep (situation report) for a live incident, in its incident channel: a short fixed-layout update for people who haven't read the whole channel — the current picture and what moved since the previous update. Use on "sitrep", "status update", "where are we", "what's the latest", "catch me up", "summarize the incident so far", when asked to keep posting on a schedule ("post a sitrep every hour until resolved"), or when the oncall memory sets an update cadence for this severity and the incident owner asks Claude to keep it. Reads the channel, alert thread and findings posted, re-reads the one key signal, and writes: status line, TL;DR, impact, what changed since the last sitrep, what's in progress and who has it, what's needed, when the next update comes, one chart. Facts come only from what people said or Claude read first-hand; cause and recovery time are never guessed. Fits one phone screen. Not investigation (`incident-investigate`) or the write-up afterwards (`incident-postmortem`).
日本語の概要は準備中です。原文の説明を表示しています。
Conversion rate optimization audit — analyze a landing page, signup flow, or checkout funnel using the 5-layer CRO stack (technical performance, traffic quality, offer/pricing, design/layout, copy/messaging). Produces prioritized fix list with expected impact. Use when "CRO audit", "conversion audit", "why isn't this converting", "improve conversion rate", "landing page not converting", "optimize funnel", "signup flow audit", or any request to diagnose and fix conversion problems.
日本語の概要は準備中です。原文の説明を表示しています。
Build and query architecture-aware code search, dependency graphs, call flows, impact analysis, and belief maps for Python, TypeScript, TSX, Rust, C#, Java, Go, Ruby, and Ruby on Rails repositories. Use before non-trivial code changes to find module boundaries, blast radius, architecture violations, and the minimal source files to read.
日本語の概要は準備中です。原文の説明を表示しています。