3,743 件 ・ 関連度順
概要と使いどころ
Flow Orchestration admin: stage configuration, step assignment, background steps, interactive steps, evaluation flows, work items, pause/resume. NOT for approval routing a standard approval process would handle — use admin/approval-processes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when gathering or evaluating requirements for a Salesforce Commerce Cloud digital storefront — branding strategy, content management approach, personalization, mobile experience, and accessibility compliance. Trigger keywords: SFRA branding, PWA Kit storefront, composable storefront, storefront accessibility, WCAG Commerce Cloud, overlay cartridge branding, mobile storefront, storefront personalization, content slots. NOT for building the site in Business Manager — use admin/b2c-commerce-store-setup. NOT for SCAPI design, Managed Runtime and caching strategy — use architect/headless-commerce-architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Identify, score, and prioritize Salesforce AI use cases before any implementation begins — opportunity identification, Impact-Effort matrix scoring, feasibility evaluation across Technical/Operational/Data/Risk dimensions, and ROI framing. NOT for the license checks and enablement steps once a use case is approved — use agentforce/agentforce-service-ai-setup or agentforce/agentforce-sales-ai-setup. NOT for making the data model AI-ready — use architect/ai-ready-data-architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Detects review-blocking configuration issues including sub-1.0 version numbers, beta in app name, staging endpoints, and missing demo credentials that prevent reviewers from evaluating the app, violating Guidelines 2.1 and 2.3.
日本語の概要は準備中です。原文の説明を表示しています。
How to write good tests. Use when writing tests, improving test coverage, or evaluating test quality. Also invoked by other skills — BDD at RED phase, tdd-review at GREEN gate, refactor at PROTECT phase, and debug. Core test quality knowledge across all workflows.
日本語の概要は準備中です。原文の説明を表示しています。
AI นักวิเคราะห์ทางการเงิน — DCF Valuation, Financial Model, Investment Memo, Equity Research, Ratio Analysis
日本語の概要は準備中です。原文の説明を表示しています。
Franchise Owner Playbook — franchise evaluation, SOP, multi-unit operations, franchisor relationship, ROI analysis สำหรับเจ้าของแฟรนไชส์ไทย
日本語の概要は準備中です。原文の説明を表示しています。
Influencer marketing AI — brief, pitch, rate evaluation, performance review แบบ data-driven
日本語の概要は準備中です。原文の説明を表示しています。
Reporting workflow for a working journalist, using web research and Apify's X scraper (social signals). Onboards the journalist, monitors their beat and builds digests, evaluates story pitches, finds and vets sources, and prepares interviews. Use for any newsroom task, such as "what's new on my beat", "is this pitch any good", "who should I talk to about X", "prep me for this interview", or "turn these notes into a draft".
日本語の概要は準備中です。原文の説明を表示しています。
Number theory expert covering primes, divisibility, modular arithmetic, Diophantine equations, and cryptographic applications
日本語の概要は準備中です。原文の説明を表示しています。
Expert in ODEs and PDEs covering solution methods, qualitative analysis, and applications to physics and engineering
日本語の概要は準備中です。原文の説明を表示しています。
Aggregate friction log files across a time period to identify recurring patterns, classify each cluster by intervention type, produce a prioritized action plan with success criteria, and calculate convergence metrics. Complements `skmtc-retro` (which captures per-session signal) by acting as the system's actuator: turning accumulated observations into decisions. The primary output is a review document that makes the "is it getting better?" question answerable. Use this skill when the user asks to "review retros", "review friction", "run a retro review", "what's the pattern across sessions", "what should we fix next", or on a periodic cadence (monthly, pre-release). Also run after a cluster of sessions on the same feature area to surface systemic issues before they compound. Distinct from `skmtc-retro` — that skill captures per-session observations; this skill synthesizes them into decisions. Do not run this skill as a substitute for a per-session retro.
日本語の概要は準備中です。原文の説明を表示しています。
Writes, rewrites, and reviews Chinese technical documentation, product copy, and UI microcopy using ruanyf/document-style-guide, STE-inspired Chinese methods for procedural passages, and separate product and UI extensions. Use for 中文技术写作, README, API documentation, 操作指南, 安装部署说明, 故障排查文档, 运维 Runbook, 工具描述, Agent 指令文案, 产品介绍, 功能说明, 界面文案, 按钮, 空状态, and 错误提示 when the task concerns meaning, structure, or wording. Delegates requested formatting checks to daftai-chinese-copywriting. Pure punctuation or spacing tasks belong to that skill; personal essays and author-voice articles do not belong here.
日本語の概要は準備中です。原文の説明を表示しています。
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
日本語の概要は準備中です。原文の説明を表示しています。
Execute a Prometheus work plan in Codex with Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and Stop-hook continuation. Use after planning when the user says start work, execute plan, continue plan, resume plan, or asks to run a .omo/plans plan.
日本語の概要は準備中です。原文の説明を表示しています。
Navigator and help guide for the UniKit framework — use when the user is unsure what to do next, where to start, or which unikit skill fits their situation. It diagnoses intent and points to the right skill or pipeline: starting a project, writing code, testing, planning, the spec-driven code workflow, authoring or detailing game design, finding a new mechanic, or deciding what game to build. Trigger on questions like "what do I do next", "where do I start", "how do I start coding", "how do I test my code", "how do I create the game design", "how do I detail a system", "how do I find a new mechanic", "which unikit skill should I use", "how does the code pipeline relate to game design", "I'm lost in unikit", "help me with unikit". Read-only — it explains and points to the right command, it never edits project files. For technical code research use /unikit-explore; for game-design research use /unikit-gd-explore; to initialize the framework use /unikit.
日本語の概要は準備中です。原文の説明を表示しています。
Abductive reasoning about causes. Takes a phenomenon, separates observations from interpretations, then spawns diagnosticians applying different reasoning lenses (technical, human-factors, process, incentive-structure, environmental, temporal, measurement-artifact, statistical) in isolation. Orchestrator evaluates candidate causes for fit-against-evidence, calibrates confidence honestly, and reports leading candidate(s) with distinguishing evidence needed. Produces feedback only — no code, no tickets, no artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when assessing body fat percentage from skinfold measurements, calculating body density, or interpreting body composition results using Durnin-Womersley or Jackson-Pollock equations.
日本語の概要は準備中です。原文の説明を表示しています。
Verify a native LLM voting advisor before trusting advisor-sensitive evaluations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when monitoring Crewrift evaluations, rounds, or rankings across turns with a persistent poller.
日本語の概要は準備中です。原文の説明を表示しています。
Use when classifying a stuck, failed, empty, or zero-scoring evaluation as infrastructure or policy failure.
日本語の概要は準備中です。原文の説明を表示しています。
Use before evaluations or after roster churn to resolve live policy versions and restore the champion flag.
日本語の概要は準備中です。原文の説明を表示しています。
GAN-inspired Generator-Evaluator agent harness for building high-quality applications autonomously. Based on Anthropic's March 2026 harness design paper.
日本語の概要は準備中です。原文の説明を表示しています。