4,063 件 ・ 関連度順
概要と使いどころ
Deep research on technical topics using EXA tools with intelligent two-tier caching. Use when user asks to research a topic, investigate best practices, look up information, find patterns, or explore architectures. Also invoked by /research command. Triggers: "research", "look up", "investigate", "deep dive", "find information about", "what are best practices for", "how do others implement".
日本語の概要は準備中です。原文の説明を表示しています。
Pre-publish (or retroactive) content-quality gate implementing Google's official self-assessment questions from the creating-helpful-content doc, plus 2024 spam-policy red flags. Verdict: PUBLISH / REVISE / RETHINK. Use when user says "helpful content", "people-first", "content self-assessment", "is my content helpful", or "content quality gate".
日本語の概要は準備中です。原文の説明を表示しています。
Systematic technical debt analysis across architecture, testing, documentation, and infrastructure. Investigates the codebase, scores findings by impact and effort, and generates a prioritized TECH_DEBT.md remediation plan. Delegates to specialized skills for code quality (scout) and linting (lint-fix). Use when assessing overall project health, planning cleanup sprints, or onboarding to an unfamiliar codebase.
日本語の概要は準備中です。原文の説明を表示しています。
Runs a 4-phase compliance pipeline: security scan, GDPR audit, dependency vulnerability check, and penetration test, producing a unified pass/fail compliance report. Triggers: on: "compliance check", "compliance gate", "run compliance", "pre-release compliance", "security and compliance".
日本語の概要は準備中です。原文の説明を表示しています。
Set up an end-to-end test suite in any repo, following practices that make e2e a reliable per-PR gate: real flows over bypass, layered assertions, a reusable auth/session helper, video+trace evidence, and a compounding suite. Use when a repo has no e2e (or weak e2e) and you want system-level tests — "set up e2e", "add end-to-end tests", "scaffold a test gate".
日本語の概要は準備中です。原文の説明を表示しています。
Maintain Yuzu's protobuf wire contracts, code generation, and gateway proto mirrors. Use when editing `.proto` files, `proto/gen_proto.py`, `proto/meson.build`, `proto/buf.yaml`, or any file under `gateway/priv/proto`.
日本語の概要は準備中です。原文の説明を表示しています。
Designs, deploys, and secures Google Cloud Agent Gateway solutions. Use when the user needs to configure multi-agent security, ingress (CLIENT_TO_AGENT), or egress (AGENT_TO_ANYWHERE) patterns involving Model Armor, IAP, and Agent Registry. Don't use for general Cloud Load Balancing or basic VPC setup not related to Agent Gateways.
日本語の概要は準備中です。原文の説明を表示しています。
Troubleshoots Google Cloud Gemini Enterprise Agent Platform issues (Agent Gateway, Registry, Identity, Policies, Model Armor, Identity-Aware Proxy (IAP)). Use when agent requests fail with 403 (especially unauthorized egress), Agent Runtime queries return 500, or gateway/IAP logs show permission errors. Don't use for general Google Cloud Identity and Access Management (IAM) debugging or networking issues unrelated to the Agent Platform stack.
日本語の概要は準備中です。原文の説明を表示しています。
Wire the current repository through the Caveman Cloud gateway so every LLM request is measured — cost, tokens, latency — with zero behavior change. Use when the user pastes the Caveman setup prompt, says "set up caveman", or wants LLM spend observability added to an app. Requires the gateway URL and a Cave API key (the setup prompt carries both).
日本語の概要は準備中です。原文の説明を表示しています。
Inspect Caveman Cloud's eval-gated experiment lifecycle and block unsafe execution. Use when the user asks to start, approve, cancel, promote, or roll back a Caveman experiment, or asks what action an experiment's evidence supports. Read evidence first; do not execute lifecycle mutations until server-authoritative transition and evidence gates ship.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when writing, debugging, or optimizing SAQL queries in CRM Analytics — covering pipeline syntax, aggregation, windowing functions (rank, dense_rank, moving_average), cogroup joins, rollup subtotals, piggyback queries, and REST API execution. NOT for SOQL GROUP BY aggregates in Apex — use apex/apex-aggregate-queries. NOT for dashboard JSON steps and bindings — use admin/analytics-dashboard-json.
日本語の概要は準備中です。原文の説明を表示しています。
Configuring User Access Policies (UAP) to automatically assign or revoke permission sets and permission set groups based on user attributes. Use when automating permission provisioning on user create/update without Apex triggers. Covers policy configuration, filter criteria, evaluation order, and PSL assignment. Also covers booleanFilter OR logic, the `in` operator for multi-value filters, the `order` tiebreak between competing policies, actions incl. permission set / permission set group / permission set licence / package licence / queue / public group grant and revoke, the UserAccessChange audit object, and deploying the UserAccessPolicy metadata type. NOT for permission set design — use admin/permission-set-architecture. NOT for delegated user admin — use admin/delegated-administration.
日本語の概要は準備中です。原文の説明を表示しています。
Eliciting and documenting a sales process before it is built in Salesforce: stage sequencing, entry/exit criteria per stage, win/loss analysis requirements, and stage transition rules. Trigger keywords: sales process design, stage discovery, entry criteria, exit criteria, stage gate, win/loss categorisation, sales methodology, pipeline stages, opportunity stage mapping, stage ladder, probability ladder, forecast category mapping, required fields per stage, stage swim lane, discovery workshop, handoff brief. NOT for configuring OpportunityStage, Sales Processes or Path in Setup — use admin/opportunity-management. NOT for cross-functional swim-lane maps — use admin/process-flow-as-is-to-be.
日本語の概要は準備中です。原文の説明を表示しています。
Produce a researched long-form article from a topic prompt via an orchestrated pipeline - research agent (first-person sources, working-definition gate), narrative-architecture outline, writer/cold-reviewer loop with an explicit ACCEPT/REVISE verdict contract, then a catalog-deslop pass with a regression gate. The orchestrator dispatches subagents only; the writer never judges its own draft. Use when the user says "article factory", "write an article about X", "run the article pipeline", or asks for a researched long-form piece produced end-to-end. For essays and micro posts in the user's own voice without a research stage, use the prose skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate work as a cyclic directed graph of subagent-executed nodes with transition criteria on edges, budgeted cycles, and per-node gates (runtime verification, metric, or artifact). Use when the user says "workgraph", "run this as a graph", "graph this work", or when a goal has parallel branches, feedback loops, or mixed gate types that a linear loop cannot express. Every node is sized to a 64k context budget, so small goals run as a two-node do/verify graph and large goals scale out without caps. For clock-driven or metric-driven single loops, timeboxed-iterating and autoresearch remain lighter.
日本語の概要は準備中です。原文の説明を表示しています。
Verify-before-done — exercise the current change end-to-end against its acceptance criteria (the SDD plan's, or the ticket's) and report a per-criterion PASS/FAIL verdict, then record the outcome to memory. This is the concrete action that satisfies moflo's verify-before-done gate (`gates.verify_before_done` / `/flo -v` / `/flo -sd`). Use before `gh pr create` when the change must be proven to work, not just tested in passing. Verifies only — it does not fix; on FAIL it reports the gaps and stops.
日本語の概要は準備中です。原文の説明を表示しています。
Enter explore mode for technical work — a thinking partner for {{engine_name}} code, architecture, and implementation decisions before you write any code. Use it to investigate a technical solution, design the architecture of a feature, choose between frameworks or libraries, compare implementation approaches, analyze how existing code or a system works, or deeply root-cause a complex bug without fixing it yet. The ultra mode adds adaptive artifacts (a C4 view, ADRs, a dependency graph) to the research folder — run it on "ultra research", "ultra explore" or "ultraresearch"; otherwise run the default. Trigger on "let's explore this technical solution", "how should we architect this feature", "which framework should we use", "run an ultra research on the save system", "investigate this error deeply". Research and analysis only — it never writes code. This is the CODE / engineering explorer — for GAME-DESIGN, GDD, mechanics, or balance research (no code) use /unikit-gd-explore.
日本語の概要は準備中です。原文の説明を表示しています。
Run the retrieval recall gate with dead-gold triage and the binary A/B regression test. Required before release tags; use after any retrieval-adjacent merge.
日本語の概要は準備中です。原文の説明を表示しています。
Acuity Scheduling API integration with managed OAuth. Manage appointments, calendars, clients, and availability. Use this skill when users want to schedule, reschedule, or cancel appointments, check availability, or manage clients and calendars. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).
日本語の概要は準備中です。原文の説明を表示しています。
ActiveCampaign API integration with managed OAuth. Marketing automation, CRM, contacts, deals, and email campaigns. Use this skill when users want to manage contacts, deals, tags, lists, automations, or campaigns in ActiveCampaign. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key.
日本語の概要は準備中です。原文の説明を表示しています。
Design, configure, debug, and optimize OpenClaw AI agent deployments. Master guide for gateway configuration, openclaw.json settings, model routing and fallback chains, skills development and publishing, cron job scheduling, memory systems (Qdrant, Neo4j, SQLite), Docker infrastructure, and Tailscale VPN networking. Includes config analyzer that audits your openclaw.json and suggests improvements, plus health checker that validates all OpenClaw subsystems. Built for AI agents — Python stdlib only, no dependencies. Use for OpenClaw setup, gateway debugging, skill building, cron management, model optimization, cost reduction, and infrastructure troubleshooting.
日本語の概要は準備中です。原文の説明を表示しています。
planning-review-activation-safety-check에 run-gate 보존 확인 추가
日本語の概要は準備中です。原文の説明を表示しています。
contract-gate-parity-check
日本語の概要は準備中です。原文の説明を表示しています。
diagnostic-monitor-read-only-gate
日本語の概要は準備中です。原文の説明を表示しています。