5,862 件 ・ 関連度順
概要と使いどころ
Analyze insurance claims workflow systems for intake optimization, adjudication rules, subrogation, litigation management, and settlement analytics. Use when: 'audit claims process', 'review FNOL workflow', 'evaluate claims automation', 'check subrogation recovery', 'assess claims fraud detection', 'optimize claims cycle time', 'review Guidewire ClaimCenter setup'.
日本語の概要は準備中です。原文の説明を表示しています。
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'.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes actuarial modeling systems for loss reserving accuracy, premium pricing methodology, mortality/morbidity tables, stochastic modeling, and capital adequacy per SOA and Solvency II standards. USE THIS SKILL WHEN: - You need to review or audit actuarial models (reserving, pricing, capital) - Someone asks about loss triangle analysis or reserve adequacy - You are evaluating IBNR calculations, chain ladder methods, or Bornhuetter-Ferguson - A project involves insurance pricing, GLM rating models, or ratemaking - You need to assess Solvency II SCR calculations or RBC compliance - Someone mentions actuarial opinions, ASOP compliance, or SOA standards - You are reviewing stochastic models, ESG configurations, or DFA frameworks - A codebase uses actuarial libraries (chainladder, lifetables, ChainLadder R package) TRIGGER PHRASES: "actuarial", "loss reserving", "IBNR", "chain ladder", "premium pricing", "mortality table", "Solvency II", "capital adequacy", "ratemaking", "GLM pricing", "risk-based capital", "reserve analysis", "actuarial opinion"
日本語の概要は準備中です。原文の説明を表示しています。
Despliega soluciones de IA para insurance claims automation con arquitectura modular, metricas auditables y decisiones alineadas al contexto del dominio.
日本語の概要は準備中です。原文の説明を表示しています。
Route OpenClaw design work to canonical brand, Carapace product-interface, marketing-page, or design-audit guidance. Use when a task touches OpenClaw visual identity, shared CSS tokens, product UI, public web pages, or Carapace compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Build or audit a financial model — 3-statement model (P&L, cash flow, balance sheet), scenario analysis, and sensitivity tables. Use when asked to "build a financial model", "model our growth scenarios", or "what happens to runway if we hire 5 people".
日本語の概要は準備中です。原文の説明を表示しています。
Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured. Use when asked to "what are we tracking", "audit our analytics", "what metrics exist", "analytics inventory", or before designing new metrics or instrumentation.
日本語の概要は準備中です。原文の説明を表示しています。
Analytics and BI engineer — dashboards, metrics design, reporting pipelines, and data storytelling. Use when asked to "build a dashboard", "design a metric", "write a report", or "audit our analytics".
日本語の概要は準備中です。原文の説明を表示しています。
Audit and improve unit economics — LTV, CAC, payback period, gross margin, contribution margin. Use when asked to "are our unit economics good", "what is our LTV/CAC", or "how do we improve gross margin".
日本語の概要は準備中です。原文の説明を表示しています。
Manage vendor relationships — vendor selection scorecard, contract review checklist, renewal tracking, and vendor consolidation audit. Use when asked to "evaluate this vendor", "review this contract", "track vendor renewals", or "reduce our SaaS spend".
日本語の概要は準備中です。原文の説明を表示しています。
Build or audit compliance program — SOC2, GDPR, HIPAA, or ISO 27001 readiness assessment, gap analysis, and remediation roadmap. Use when asked to "do we need SOC2", "are we GDPR compliant", "what does our compliance program need", or "build a security policy".
日本語の概要は準備中です。原文の説明を表示しています。
Audit or redesign responsive behavior of a layout — breakpoints, reflow, and content priority. Use when asked to "fix responsive behavior", "define breakpoints", or "how should this reflow on mobile".
日本語の概要は準備中です。原文の説明を表示しています。
Audit or refactor a design token system for color — naming, structure, and coverage. Use when asked to "refactor our color tokens", "fix color token naming", or "improve token coverage for color".
日本語の概要は準備中です。原文の説明を表示しています。
Survey existing cloud cost controls — tagging coverage, alerting, and FinOps maturity. Use when asked to "audit our cost controls", "is our tagging complete", or "assess our FinOps maturity".
日本語の概要は準備中です。原文の説明を表示しています。
Audit cloud infrastructure costs and produce a concrete optimization plan with specific changes and estimated savings. Use when asked to "how much is this costing", "reduce cloud spend", "cost optimization", "are we overpaying", "cloud bill", or "budget for this infra".
日本語の概要は準備中です。原文の説明を表示しています。
Run human-to-agent migration - audit which roles can be agent-assisted or replaced, design the transition playbook, and manage the offboarding of displaced roles. Use when asked to "which roles can agents replace", "how do we transition to AI-first ops", or "build our agent migration plan".
日本語の概要は準備中です。原文の説明を表示しています。
Expert 5-dimension design critique — philosophical, scored, actionable. Use when asked to "critique this design", "expert review", "score my design", "how does this look", "is this good design", "design feedback", or "review this UI". Different from /form-audit (which is technical QA for consistency/compliance) — form-critique evaluates design as a craft object: philosophy, hierarchy, execution, function, and innovation each scored 0–10 with a punch list. Add "as a report" or "give me a visual report" to produce an HTML file with SVG radar chart, evidence cards, and Keep/Fix/Quick-wins action lists — useful for design reviews and stakeholder presentations instead of CLI output.
日本語の概要は準備中です。原文の説明を表示しています。
Design or audit a feature store — serving, freshness, and sharing across models. Use when asked "do we need a feature store", "design a feature store", or "share features across models".
日本語の概要は準備中です。原文の説明を表示しています。
Usability review — evaluate an existing flow or UI against usability heuristics, flag friction points, and recommend fixes. Use when asked to "review the UX", "usability audit", "what's wrong with this flow", "UX feedback", "critique this design", or "why are users dropping off here".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing resilience — identify untested failure modes and chaos engineering gaps. Use when asked "how resilient are we", "what failure modes are untested", or "find our chaos engineering gaps".
日本語の概要は準備中です。原文の説明を表示しています。
Survey existing forecasting code or models in a codebase — find gaps, stale models, and missing validation. Use when asked "what forecasting models do we have", "audit our forecasts", or "find stale models".
日本語の概要は準備中です。原文の説明を表示しています。
Survey existing compliance artifacts — policies, audits, certifications. Use when asked "what compliance docs do we have", "survey our policies", or "inventory our compliance artifacts".
日本語の概要は準備中です。原文の説明を表示しています。
Design support metrics dashboard -- CSAT, FRT, TTR, ticket deflection rate, volume trends, and agent efficiency. Use when asked to "what metrics should support track", "build our support dashboard", "measure support quality", or "audit our support performance".
日本語の概要は準備中です。原文の説明を表示しています。
Elite frontend design taste for building, reviewing, and polishing web interfaces. Use whenever the user wants to design, redesign, shape, critique, audit, polish, or improve any UI (landing pages, portfolios, dashboards, product UI, components, forms, onboarding, empty states) or asks to make something look better / premium / modern, fix the styling, add or fix animations, or make a design feel less generic ("AI slop"). Covers typography, color, spacing, layout, visual hierarchy, motion, micro-interactions, component states, accessibility, responsive behavior, UX copy, and anti-pattern detection.
日本語の概要は準備中です。原文の説明を表示しています。