1.2万 件 ・ 関連度順
概要と使いどころ
Analyze an incident response program for playbook coverage, MTTR optimization opportunities, evidence collection readiness, root cause analysis quality, and post-incident review effectiveness. Triggers: building a SOC, assessing IR maturity, optimizing detection-to-recovery timelines.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze fraud detection systems including rule engines, ML scoring models, real-time transaction monitoring, alert triage workflows, false positive management, SAR/CTR regulatory reporting, adversarial robustness testing, and adaptive retraining pipelines for payment fraud, account takeover, identity theft, and AML compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Audit legal case prediction systems for bias, fairness, accuracy, and ethical guardrails. Use when: 'check my prediction model for bias', 'audit case outcome fairness', 'evaluate legal ML model', 'review sentencing prediction ethics', 'analyze bail risk algorithm', 'fairness metrics for justice system AI'.
日本語の概要は準備中です。原文の説明を表示しています。
Build a structured Quarterly Business Review deck for a customer account. Use when user says "QBR", "quarterly business review", "prep my QBR", "build the deck", "renewal prep", "executive check-in", "90-day review", or "customer business review" - even if they don't use the acronym. Applies to CSMs preparing for executive-level customer meetings focused on value delivered, health, and next quarter alignment.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate page content for usefulness, E-E-A-T, readability, thinness, and AI citation readiness, plus last-mile draft cleanup (AI-typical phrasing and invisible Unicode watermark characters). Use for content-only analysis, not full-page technical checks.
日本語の概要は準備中です。原文の説明を表示しています。
Documenting As-Is and To-Be business processes for a Salesforce project as swim-lane diagrams — one lane per actor, explicit decision points, parallel and exception/sad paths, and per-step automation-tier annotations that drive downstream build decisions. Trigger keywords: As-Is To-Be salesforce process, swim lane salesforce, business process map, automation candidate identification, sad path documentation, process actor mapping, manual residue. NOT for Opportunity stage and exit-criteria design — use admin/sales-process-mapping. NOT for picking Flow vs Apex for one requirement — use admin/process-automation-selection.
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning, sequencing, or troubleshooting an org-wide migration from Salesforce Classic to Lightning Experience. Covers the LEX Transition Assistant Readiness Check, asset triage matrix (Visualforce, JavaScript buttons, page layouts, Knowledge, email templates, list views, AppExchange), pilot/wave rollout sequencing, end-user adoption telemetry, and cutover criteria. Triggers: 'lightning experience transition', 'classic to lightning migration plan', 'LEX readiness check', 'why are some users still on Classic', 'turning on Lightning for everyone'. NOT for individual asset migrations like a single VF page (use lwc/visualforce-to-lwc-migration), a single JavaScript button (use admin/custom-button-to-action-migration), or Knowledge article migration (use admin/knowledge-classic-to-lightning) — this skill orchestrates the program. NOT for Lightning App Builder page design (use admin/lightning-app-builder-advanced).
日本語の概要は準備中です。原文の説明を表示しています。
Use when configuring or troubleshooting a Salesforce B2C Commerce (SFCC) storefront — including Business Manager site creation, SFRA cartridge path setup, customer groups, search index rebuilding, and key quota limits. Trigger keywords: SFCC, Commerce Cloud, Business Manager, storefront, cartridge, SFRA, site preferences, replication. NOT for B2B Commerce on Lightning (WebStore, BuyerGroup) — use admin/b2b-commerce-store-setup. NOT for choosing SFCC vs B2B Commerce — use architect/b2b-vs-b2c-architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive Japanese grammar expert covering particles, verb conjugations, sentence patterns, and the nuances between spoken and written Japanese
日本語の概要は準備中です。原文の説明を表示しています。
Expert in pan-Asian cuisines and modern fusion techniques across Chinese, Japanese, Thai, Vietnamese, and Korean cooking
日本語の概要は準備中です。原文の説明を表示しています。
Create or update a strategic project roadmap with major milestones. Generates .unikit/ROADMAP.md — a high-level checklist of project goals. Use when user says "roadmap", "project plan", "milestones", "what to build next", "strategic goals", or wants to see big-picture progress. Also use when the user asks to check which milestones are done or wants to plan the overall project direction.
日本語の概要は準備中です。原文の説明を表示しています。
Mechanical documentation hygiene. Spawns a doc-maintainer agent to audit all project documentation and fix correctness, completeness, freshness, and consistency issues autonomously within its authority. Surfaces anything requiring user judgment for approval.
日本語の概要は準備中です。原文の説明を表示しています。
Checks and fixes Chinese copywriting with autocorrect-backed workflows for text and single-file Markdown/TXT inputs. Use when user asks to normalize Chinese punctuation, spacing, or full-width/half-width usage. Also triggers for "校对", "检查排版", "中英文空格", "全角半角". Does not rewrite document structure, product claims, or UI messaging.
日本語の概要は準備中です。原文の説明を表示しています。
GAN-inspired Generator-Evaluator agent harness for building high-quality applications autonomously. Based on Anthropic's March 2026 harness design paper.
日本語の概要は準備中です。原文の説明を表示しています。
Use after a verified Decisions harness audit when the user asks to apply safe fixes to harness drift, dead references, stale projected skills, duplicate routing, bloated state files, or invalid local config.
日本語の概要は準備中です。原文の説明を表示しています。
ADHD-friendly life management assistant for OpenClaw. Helps with daily planning, task breakdown, time management, prioritization, body doubling, dopamine regulation, and maintaining routines. Use when the user asks for help organizing their life, staying on top of tasks, beating procrastination, planning their day/week, managing overwhelm, or mentions ADHD-related challenges like time blindness, forgetfulness, difficulty starting tasks, or emotional dysregulation.
日本語の概要は準備中です。原文の説明を表示しています。
ADMET (Absorption, Distribution, Metabolism, Excretion, Toxicity) prediction for drug candidates. Use for assessing drug-likeness, PK properties, and safety risks early in drug discovery. Keywords: ADMET, PK, toxicity, drug-likeness, DILI, hERG, bioavailability
日本語の概要は準備中です。原文の説明を表示しています。
Launch Marcus multi-agent experiments with independent CLI agents in tmux panes. Use when the user says "build X with Marcus", "run a Marcus experiment", "spawn N agents with Marcus", "/marcus", or references the Marcus multi-agent framework. This skill handles experiment setup, config generation, and spawning independent agent CLI processes that coordinate via the Marcus MCP server. Each agent runs in its own tmux pane with full autonomy. NOT for ClawTeam — this is specifically for the Marcus MCP-based multi-agent system. NOTE: "Marcus" is also the name of the MCP server that agents use for coordination. The /marcus skill launches experiments that USE the Marcus MCP server — they are complementary, not competing. The MCP server must be running before invoking this skill. The Marcus MCP server is agent-agnostic; this skill supports both Anthropic's claude CLI and OpenAI's codex CLI as agent harnesses (selected via --harness).
日本語の概要は準備中です。原文の説明を表示しています。
Launch Marcus multi-agent experiments with independent CLI agents in tmux panes. Use when the user says "build X with Marcus", "run a Marcus experiment", "spawn N agents with Marcus", "/marcus", or references the Marcus multi-agent framework. This skill handles experiment setup, config generation, and spawning independent agent CLI processes that coordinate via the Marcus MCP server. Each agent runs in its own tmux pane with full autonomy. NOT for ClawTeam — this is specifically for the Marcus MCP-based multi-agent system. NOTE: "Marcus" is also the name of the MCP server that agents use for coordination. The /marcus skill launches experiments that USE the Marcus MCP server — they are complementary, not competing. The MCP server must be running before invoking this skill. The Marcus MCP server is agent-agnostic; this skill supports Anthropic's claude CLI, OpenAI's codex CLI, and Google's gemini CLI as agent harnesses (selected via --harness).
日本語の概要は準備中です。原文の説明を表示しています。
Research process for comparing frontier harnesses (Claude Code, Codex, OpenClaw, autoresearch, Prime Agent) with the original/upstream implementation and performing GAP analysis before feature implementation. Triggered by "research" ("리서치"), "gap", "frontier", "harness", "case study" ("사례 조사"), "pattern exploration" ("패턴 탐색"), "comparative analysis" ("비교 분석") keywords.
日本語の概要は準備中です。原文の説明を表示しています。
Heart rate variability biometrics and emotional awareness training. Expert in HRV analysis, interoception training, biofeedback, and emotional intelligence. Activate on 'HRV', 'heart rate variability', 'alexithymia', 'biofeedback', 'vagal tone', 'interoception', 'RMSSD', 'autonomic nervous system'. NOT for general fitness tracking without HRV focus, simple heart rate monitoring, or diagnosing medical conditions (only licensed professionals diagnose).
日本語の概要は準備中です。原文の説明を表示しています。
Organizing digital life for legacy, emergency access, and death preparedness. Specializes in password management, account documentation, digital asset preservation, and ensuring loved ones can access what they need.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesize code harnesses for agent action validation — AutoHarness-inspired verifier/filter/policy generation
日本語の概要は準備中です。原文の説明を表示しています。
Quantitative agent evaluation using 4-metric framework (correctness/step_ratio/tool_call_ratio/latency_ratio) with ideal trajectory annotation and capability-categorical taxonomy. Use when measuring agent efficiency, comparing agent variants, or gating new agents through correctness→efficiency phases. Complements harness-eval (SE benchmarks) and evaluator-optimizer (qualitative rubric).
日本語の概要は準備中です。原文の説明を表示しています。