「quest」の検索結果

コード実装や不具合修正、PRレビューをBlackbox AIに委任します。複数モデルの結果を評価して選び、長時間の作業の監視や保存地点からの再開も扱うスキル。

• 機能実装や不具合修正の委任
• PRの不具合とセキュリティ確認
• 複数AIモデルの実装比較

機能追加やコード整理、PRレビューをGrok Build CLIに任せるスキル。単発実行と対話セッションを使い分け、長い作業の監視や続きの依頼も扱います。

• 機能の実装を任せたいとき
• 既存コードのリファクタリング
• PRの変更内容をレビュー

システムの構成やデータの流れを、クリックして詳しく読める立体的なHTMLマップに整理します。同じデータから説明文も生成し、設計上の判断や未解決の質問を管理します。

• システム構成とデータの流れの説明
• 新しい設計をチームで検討したいとき
• レビュー中の未解決の質問の管理

Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.

日本語の概要は準備中です。原文の説明を表示しています。

Add a new Paperclip issue-thread interaction kind end-to-end. Use when repo work introduces or extends interaction cards like request_confirmation, checkbox confirmations, ask_user_questions, or suggest_tasks.

日本語の概要は準備中です。原文の説明を表示しています。

A Frequently Asked Questions (FAQ) page with collapsible accordion sections, search functionality, and category filtering. Use when the brief asks for "FAQ", "help center", "questions", or "support page".

日本語の概要は準備中です。原文の説明を表示しています。

Create pull requests for ant-design using the repository's official PR templates. Use this skill when the user asks to create/open a PR, draft PR title/body, summarize branch changes for a PR, or otherwise prepare PR content. Judge by intent rather than fixed phrases; short colloquial requests still count if they are about creating a PR rather than discussing PR concepts.

日本語の概要は準備中です。原文の説明を表示しています。

Opens a pull request from the current branch using the PR template. Use when the user asks to open a PR, create a pull request, or invokes /open-pr.

日本語の概要は準備中です。原文の説明を表示しています。

Creates a pull request following Storybook conventions. Use when creating PRs, opening pull requests, or submitting changes for review.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when the user requests to review, analyze, critique, or summarize academic papers, research articles, preprints, or scientific publications. Supports comprehensive structured reviews covering methodology assessment, contribution evaluation, literature positioning, and constructive feedback generation. Trigger on queries involving paper URLs, uploaded PDFs, arXiv links, or requests like "review this paper", "analyze this research", "summarize this study", or "write a peer review".

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when the user requests to generate, create, write, or draft a newsletter, email digest, weekly roundup, industry briefing, or curated content summary. Supports topic-based research, content curation from multiple sources, and professional formatting for email or web distribution. Trigger on requests like "create a newsletter about X", "write a weekly digest", "generate a tech roundup", or "curate news about Y".

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests like "document this code", "create a README", "generate API docs", "write developer guide", or when analyzing codebases for documentation purposes.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill instead of WebSearch for ANY question requiring web research. Trigger on queries like "what is X", "explain X", "compare X and Y", "research X", or before content generation tasks. Provides systematic multi-angle research methodology instead of single superficial searches. Use this proactively when the user's question needs online information.

日本語の概要は準備中です。原文の説明を表示しています。

Register, list, test, and remove webhook endpoints. Configure event subscriptions (request.completed, request.failed, quota.exceeded, etc.) and manage delivery retries.

日本語の概要は準備中です。原文の説明を表示しています。

GitHub workflow automation for issues, pull requests, CI, and releases. Use when: repository hosting actions are explicitly requested. Skip when: local git operations are sufficient or publishing is unauthorized.

日本語の概要は準備中です。原文の説明を表示しています。

Use when auditing slow page loads, heavy assets, or rendering delays related to Minimize HTTP requests. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

日本語の概要は準備中です。原文の説明を表示しています。

Use when auditing slow page loads, heavy assets, or rendering delays related to Minimize critical request chains. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

日本語の概要は準備中です。原文の説明を表示しています。

Explain how this assistant works and help users understand computer access, confirmation or login blocks, and Slack errors. Use for capability questions and confusing product limitations; verify the actual state and give a supported next step. Also use for questions about their avatar or profile picture (their icon or the picture at the top) or the color of messages they send (message color, chat bubble color, or text bubble color).

日本語の概要は準備中です。原文の説明を表示しています。

Create or edit requested Page/Space content, or use for prose you have already decided to save as a standalone Markdown file, only if the user did not explicitly request a Markdown file. Honor established formats, destinations, and repository documentation. A selected Page alone does not authorize a write.

日本語の概要は準備中です。原文の説明を表示しています。

On an explicit planning request, always call `read_skill` for this skill before answering. Research first, then return one concise inline plan; do not create a plan file unless the user explicitly asks or a governing workflow requires one. Start and end the reply by saying this is not a special mode and `go` executes the plan; do not implement in the planning turn. For ordinary implement, build, fix, debug, or refactor requests, work directly. When an explicit plan divides work into separate diffs, commits, or PRs and the user asks to publish, preserve that split and tell the user before deviating.

日本語の概要は準備中です。原文の説明を表示しています。

Use when creating, editing, or inspecting a spreadsheet or workbook (Excel, Google Sheets, or CSV), or when the task calls for a reusable budget, model, tracker, or structured data the user can sort, calculate, or update. Also use for questions that require inspecting an existing workbook; not for quick arithmetic or a small one-off table in chat unless requested as a spreadsheet.

日本語の概要は準備中です。原文の説明を表示しています。

Deliver a runnable local browser app so the user can operate it on the first handoff. This delivery skill does not choose whether a requested local system should be a browser app. On a current turn that explicitly says to implement a brand-new browser project now, load bundled:greenfield-project-scaffolding before project work only after no-peek or permitted top-level placement facts prove that no named or suitable current-folder target resolves the root; never hand off from planning or answer-only turns, existing work, a named or suitable target, or standalone or single-file delivery. Resolve user-blocking product or interface choices with an available interaction surface; resolving those choices alone never authorizes implementation. Always call read_skill for bundled:browser-app-delivery before creating or materially changing a local browser app that owns its start path or a playable browser game. Also load it when the user requests a paste-ready, single-file, offline, or immediately playable browser artifact, even if no local start path should remain, unless the user says they will open or check it themselves or explicitly declines verification. On completed local-server delivery, include exact start commands, a concrete local URL, and explicit browser-open wording. On completed standalone delivery, hand off the exact artifact path or paste URL and smoke result without inventing a server. Do not load it for a self-contained static file that has no owned start path if the user either says they will open or check it themselves or explicitly declines verification. Do not load it for component/style-only edits, deployed sites, backend/API-only work, browser QA, review, explanation, plan-only, or explicit stop/no-tool turns.

日本語の概要は準備中です。原文の説明を表示しています。

Read Instagram profiles, followers, posts, comments, likes, stories, feed, saved content, and account insights. Answer questions about posts, reels, and Instagram links. Manage interests and profile details, and publish stories, reels, posts, or carousels on request.

日本語の概要は準備中です。原文の説明を表示しています。

Render the user's morning brief as a styled HTML artifact, or set it up as a recurring weekday task. Use only when the user explicitly asks to run, see, or set up their morning brief, or if they invoke /morning by name. A question about their day, schedule, or calendar is not by itself a request for the brief; answer it directly instead.

日本語の概要は準備中です。原文の説明を表示しています。