936 件 ・ 関連度順
概要と使いどころ
Act as an interactive data analyst for ClickHouse-backed analytics. Use when the user asks questions about internal data, metrics, dashboards, telemetry, active users, revenue, funnels, trends, distributions, or wants an analyst-style conversation, ad hoc SQL, charts, or a data export against ClickHouse (local or ClickHouse Cloud).
日本語の概要は準備中です。原文の説明を表示しています。
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
日本語の概要は準備中です。原文の説明を表示しています。
Search and browse Cline session history. Use when the user asks to find, list, inspect, or export Cline sessions by time period, prompt content, status, model, provider, source, mode, workspace, or other criteria. Also use when the user wants to read a session transcript or export sessions to a directory. Trigger phrases include "find my session", "search my session history", "show me past sessions", "what was that session where", "find the session that started with", and any mention of past Cline conversations.
日本語の概要は準備中です。原文の説明を表示しています。
Act as an interactive data analyst for ClickHouse-backed analytics. Use when the user asks questions about internal data, metrics, dashboards, telemetry, active users, revenue, funnels, trends, distributions, or wants an analyst-style conversation, ad hoc SQL, charts, or a data export against ClickHouse (local or ClickHouse Cloud).
日本語の概要は準備中です。原文の説明を表示しています。
Access the Anthropic product named Claude Design when the request contains that exact name, a claude.ai/design URL, or a .dc.html file. Also use for standalone-to-artifact migration and Claude Design artifact links. Use for projects, files, design systems, previews, conversations, comments, sharing, and code-to-design or design-to-code synchronization; otherwise stay inactive.
日本語の概要は準備中です。原文の説明を表示しています。
Generate an interactive HTML brand playground that shows your brand rendered live — palette, typography, logo, voice — with a social card and OG image preview that updates as you tweak tokens. Opens in browser. The visual approval step for the /cmo flow: /visual-style writes the brand, this skill shows it. Use when the user says "show me my brand", "brand playground", "preview my brand", "what does our brand look like", "visual preview", "brand kit", "see my colors", "how does my brand look", or after /visual-style completes and the user needs to approve the visual identity before moving to content generation. Also use when someone says "I want to see it" during any brand-building conversation.
日本語の概要は準備中です。原文の説明を表示しています。
First-run conversational setup wizard for marketing-cli. Use when /cmo detects no populated brand files and no cmo-preferences.md, when the user just installed marketing-cli for the first time, or when they say things like "set up marketing", "start marketing", "marketing wizard", "I just installed marketing-cli", "onboard me", "first time", "initial setup". Asks 3 sharp questions (identity, posture, distribution preferences), records the answers to brand/cmo-preferences.md, then hands off to /cmo's foundation flow which spawns 3 research agents in parallel. The user never has to type /mktg-setup directly — /cmo auto-routes here on first run.
日本語の概要は準備中です。原文の説明を表示しています。
Provision a zero-config, no-signup, temporary Upstash Redis database for an AI agent with a single POST to https://upstash.com/start-redis, with no account, API key, or SDK setup required. Use when an agent needs scratch Redis right now and the user has not provided credentials, for short-term memory across tool calls, conversation history, a sub-agent work queue, ranked recall, or a quick prototype or demo. Covers idempotent creation and re-fetching credentials, calling the database through the body-style REST API or the official SDKs, and telling the user how to claim it. The database lives 3 days unless the user claims it; not for production data, PII, or secrets.
日本語の概要は準備中です。原文の説明を表示しています。
Design AI chatbot conversation flows with fallbacks. TRIGGERS - Use when user needs help with ai-chatbot-flow related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Start or end a forked session for exploring rabbit holes without losing the main conversation's context.
日本語の概要は準備中です。原文の説明を表示しています。
対話コンテキストをimportする。 `.dev/contexts/` ディレクトリに保存された過去の対話コンテキストを読み込み、開発の継続やレビューに活用する。 ユーザーが「コンテキストを読み込んで」「対話コンテキストをimport」「.devのコンテキストを読んで」と言った時に使用する。
対話コンテキストをexportする。 会話で共有された目的・意図・設計判断・制約条件を `.dev/contexts/` ディレクトリに書き出し、PRが存在する場合はPRコメントにも投稿する。次の作業者（レビュワー、別セッションのAI、バグハンティングのAIなど）に引き継ぐ。 ユーザーが「コンテキストを書き出して」「対話コンテキストをexport」「会話した内容を.devに保存して」と言った時に使用する。
Import a memory export from another AI assistant (ChatGPT, Gemini, Claude, etc.) into this agent's memory — conversationally, additively, and with the pasted content treated as data. Use when the user wants to bring over what another assistant knows about them.
日本語の概要は準備中です。原文の説明を表示しています。
Enter talk mode — conversation and research, no repo changes. ONLY invoke when the user explicitly types `/talk` or `$talk`; never auto-select from a natural-language question or design discussion.
日本語の概要は準備中です。原文の説明を表示しています。
Makers 开发专家团 AI Agent 工程师 Skill — Claude Agent SDK、 OpenAI Agents SDK、LangGraph、DeepAgents、CrewAI 框架集成， SSE 流式响应、conversation store、EdgeOne Makers Agent Runtime。 触发词：AI Agent、聊天机器人、LLM 应用、多 Agent 系统、 Claude SDK、OpenAI Agents、LangGraph、CrewAI、SSE 流式、 智能助手、AI 推理端点。
日本語の概要は準備中です。原文の説明を表示しています。
Hand the current conversation off to a fresh background agent that picks up the work immediately.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
日本語の概要は準備中です。原文の説明を表示しています。
Compact the current conversation into a handoff document for another agent to pick up.
日本語の概要は準備中です。原文の説明を表示しています。
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
日本語の概要は準備中です。原文の説明を表示しています。
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
日本語の概要は準備中です。原文の説明を表示しています。
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
日本語の概要は準備中です。原文の説明を表示しています。
Build Azure AI Foundry agents using the Microsoft Agent Framework Python SDK (agent-framework-azure-ai). Use when creating persistent agents with AzureAIAgentsProvider, using hosted tools (code interpreter, file search, web search), integrating MCP servers, managing conversation threads, or implementing streaming responses. Covers function tools, structured outputs, and multi-tool agents.
日本語の概要は準備中です。原文の説明を表示しています。
Build conversational AI agents using Vercel AI SDK + OpenRouter. Use when creating Next.js frontends with streaming UI, tool calling, and multi-provider support.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
日本語の概要は準備中です。原文の説明を表示しています。