「mission」の検索結果

顧客や取引先が参加するチャットで、エージェントの応答条件と送信内容を定めるスキル。呼びかけへの応答、内部情報の保護、承認用の下書きへの切り分けを扱います。

• 顧客グループでの応答ルール設定
• 取引先への返信から内部情報を守りたいとき
• 価格や契約の回答を承認用下書きに分ける

Node.js、Express、Next.jsのAPIとデータ処理を設計・レビューするスキル。DBへの問い合わせ、キャッシュ、認証、エラー処理を整理します。

• API設計と業務処理・データ取得の分離
• 重複するDB問い合わせを減らしたいとき
• キャッシュと非同期処理の導入

AIが修正したコードで同じ不具合が再発しないよう、APIの必須項目や処理分岐を自動テストで確認し、テストとビルドを先に行うレビュー手順を整えるスキル。

• バグ修正後に再発防止テストを足したいとき
• API応答の必須項目を確認したいとき
• テスト用と本番用の応答を見直したいとき

機械学習・AIの研究論文を、関連文献の調査から実験設計、結果分析、執筆、投稿準備まで支援します。引用の検証や査読への対応も扱います。

• 既存のコードや結果から論文を書きたいとき
• 研究の主張を裏づける実験を計画したいとき
• 関連研究と引用を確認したいとき

A contract for what the agent does when a long, messy, stream-of-consciousness ramble arrives (usually voice dictation): act on nothing until the echo brief is approved. The echo audits the entire transfer, mission, locked decisions and constraints, open questions, flips and parked tangents, with the model's inferences and guesses quarantined away from the user's own phrasing, so the user verifies what the model believes, not just what it doubts. Use when the user says "let me think out loud" or wants to ramble a bit before building anything, when a message opens with a speech-to-text preamble like "switching to voice, sorry for typos", when input is a long weakly punctuated stream with restarts and mid-message reversals ("actually no, wait, scrap that idea entirely"), or when the user asks to be interviewed about a fuzzy half-formed idea. Includes an optional capture mode for rambles spread across several messages and an optional targeted interview.

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

Check a GitHub, GitLab, or Perforce PR/MR/CL for review comments, failing checks, and PR-body gaps. Use when asked to inspect, fix, or prepare a change for submission.

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

Autonomously yeet a brief, unstructured complaint about agent tooling or doing agent work. Preserve the raw voice. Submit proactively without permission, preview, or announcement, then continue the primary task.

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

Quietly suggest a concrete improvement after observing material, generalizable friction in agent work. Submit proactively without permission, preview, or announcement, then continue the primary task.

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

Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the accessibility tree, and logcat. For an iOS simulator use the iOS emulator skill; build the APK with Gradle first.

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

Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.

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

Walk through a complete GAIA benchmark→submit flow — from key resolution through HAL-compatible package generation

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

Scan inputs for prompt injection, unsafe content, and adversarial attacks using AIDefence. Use when processing untrusted input (user submissions, API payloads, webhook data, tool outputs) before passing it to a model or executing it.

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

Use when auditing PWA readiness, adding an install prompt, or preparing a web app for submission to Microsoft Store or Google Play via PWA Builder.

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

Use when reviewing HTTP response headers for defense-in-depth security hardening on any web application.

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

Read this skill before the first step that uses Claude in Chrome, the browser extension whose tools are named mcp__claude-in-chrome__* (also called Chrome, the browser extension, or the external browser) and which acts in the person's real Chrome with their own sign-ins; before those tools are turned on there may be a single enable__mcp__claude-in-chrome tool instead. It covers loading the tools in one ToolSearch call, checking the person's open tabs and working in a new tab, site permissions, GIF recordings, console logs, dialogs to avoid, and when to stop and ask. It is not for the built-in browser (mcp__Claude_Browser__* or mcp__remote-devices__Claude_Browser__* tools), which has its own skill, and it does not decide which browser to use.

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

Clarify a material user-owned product decision before substantive implementation commitments. Use only when request and named/governing evidence still leave a choice that would materially change scope, platform support, user-facing surface, data/API contract, domain values, project placement, or cross-system architecture; also use when a truncated request omits such a choice. On the initial turn, inspect only named or governing requirements evidence, then ask directly without loading: prefer structured input; ask one blocking outcome question or at most three coupled questions; wait. After the answer, load the body before write or delegation. Do not use for implement/build/fix/debug/refactor work when expected behavior is settled, plan/design deliverables owned by Plan, complexity/greenfield/integration alone, agent-owned technical choices, locally discoverable facts, reversible defaults, permission to begin, or stop/no-tool turns. Never re-ask supplied facts or turn clarification into refusal.

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

Use for questions about Muse's general early access program, requests to join it, checking or withdrawing a join request, and admission updates.

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

Automates your Chrome browser to interact with web pages - clicking elements, filling forms, capturing screenshots, reading console logs, and navigating sites. Opens pages in new tabs within your existing Chrome session. Requires site-level permissions before executing (configured in the extension).

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

Health-check the user's Claude Code setup and fix issues: diagnose installation health — what the `claude doctor` terminal diagnostics cover — from local data (duplicate or leftover installs, PATH, unparseable settings files, broken or colliding agent definitions, skills whose frontmatter fails to parse); find unused skills, MCP servers, and plugins versus their context cost and disable dead weight; deduplicate local CLAUDE.md files against checked-in ones; trim checked-in CLAUDE.md files by cutting content a session could derive from the codebase (directory layouts, tech-stack lists, architecture overviews) while keeping gotchas, rationale, and non-standard conventions; migrate always-loaded CLAUDE.md guidance into lazy skills and nested CLAUDE.md files; flag slow hooks and context-heavy extensions; check the installed version is current; make auto mode the default permission mode; and pre-approve frequently denied read-only commands. Use when the user asks for a doctor run, checkup, audit, tune-up, or cleanup of their Claude Code setup or configuration.

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

Understand the capabilities and restrictions of each Remotion Studio mode. Use when implementing or reviewing Studio actions, permissions, availability, or UI across interactive, detached, deployed, and browser-based Studios.

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

Automated Cherry Studio review for local branches, PRs, commits, files, architecture docs, and repository skills. Use for code or documentation reviews that need project-specific naming, main/renderer/shared placement and dependency rules, IpcApi and DataApi boundaries, lifecycle/service ownership, renderer hooks, React/UI conventions, and tests. Review depth adapts to diff size and runtime subagent capability (single-agent or multi-agent reviewer-verifier). Report-only by default; code fixes and GitHub submission each require explicit invocation-time authorization (`fix` / `submit`). Normal-review prompts and safe interruption behavior follow the interaction contract below. To diagnose gaps in the skill after a review session, run `/gh-pr-review diag`.

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

Stateful CLI harness for JumpServer bastion host management. Supports asset, user, permission, account, session, audit, and operations management via REST API, with both one-shot and interactive REPL modes.

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

Prepares journal manuscripts, conference papers, research posters, and grant documents using venue-specific formatting guidance and bundled LaTeX scaffolds. Supports selecting an official template, checking current page or anonymity rules, adapting academic writing to a venue, or inspecting a submission PDF.

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

Drafts, revises, and audits scientific manuscripts or reports with explicit evidence provenance, reporting-guideline coverage, authorship accountability, confidentiality controls, and local consistency checks. Use for manuscript sections, references, declarations, tables, figures, or submission preparation when scientific accuracy and traceability matter.

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