スキルを探す

Builds DRAFT user personas from the research notes, interview summaries, survey free text and support themes the user provides: for each persona the goals, pains, jobs to be done, context of use, quotes exactly as supplied with their participant codes, and the evidence count behind every attribute, with names, demographics and any detail no participant stated left UNKNOWN rather than invented. Use when the user asks to "build personas from these interviews", "who are our users based on this research", "draft user personas", "turn these research notes into personas" or "update our personas with the new interviews". Do not use for theming a batch of customer feedback into counts, use customer-feedback-theme-synthesis instead; for exit interviews, use exit-interview-synthesis; for the requirements those personas imply, use product-requirements-draft. Drafts for human review; never approves, authorises or signs off.

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

Synthesises training survey responses and manager notes into a DRAFT training needs report by role: coded needs with record counts per role (n of N), the evidence type behind each count, anonymised quotes cited to record codes, disagreements between what staff report and what managers observe, gaps where a role is under-represented or a required skill has no evidence, and follow-up questions to settle before any course is designed. Never rates an individual, ranks a team or turns a count into a competence verdict. Use when the user asks to "analyse this training survey", "what training do our teams need", "summarise the manager feedback on skills gaps", "build a training needs analysis by role" or "which roles have the biggest skill gaps". Do not use for turning an agreed need into a course, use course-outline-builder instead; for exit interviews, use exit-interview-synthesis. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT quiz from the training content the user supplies (slide deck, manual, e-learning script, session transcript, procedure): numbered questions with the correct answer, distractors drawn from the content itself, an explanation quoting the source passage with its location, a difficulty tag (Recall, Apply, Analyse) with its basis, and a coverage table showing which sections and objectives each question tests and which are left uncovered. Use when the user asks to "build a quiz from this deck", "write knowledge check questions for this module", "create an assessment from this training", "test understanding of this procedure" or "which sections does this quiz cover". Do not use for a reader-facing question and answer page built from documents, use faq-builder instead; for writing the procedure itself from notes or a walkthrough, use sop-drafter. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT course outline from a training need and audience: learning objectives with an observable verb, condition and standard, modules in a stated order with a duration basis and sources, activities and an assessment plan aligned objective by objective, and a coverage table showing what each objective still lacks. Never sets a pass mark, declares learners competent or invents content. Use when the user asks to "build a course outline", "design a training programme for", "turn this need into modules and objectives", "draft the curriculum for this workshop" or "what should this training cover". Do not use for quiz items from finished content, use training-quiz-builder instead; for needs from surveys and manager notes, use training-needs-synthesis; for a new starter's first weeks, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Flags where a P&ID draft raises a process safety question and points to the candidate evidence an engineer would review (HAZOP register, relief study, SIL assessment, isolation philosophy), as questions and quoted passages with UNKNOWN for missing documents, plus safety functions, relief devices and isolation requirements carried over as stated. Never rates, sizes, classifies, resolves or declares protection adequate. Use when the user asks to "write the process safety flags", "produce the process safety section of the P&ID enrichment", "list which protection questions this P&ID raises" or "map the HAZOP and relief study evidence to the draft" after gate G2, once the piping and instrumentation sections exist. Do not use for proposing loops, alarms or trips from the control philosophy, use instrumentation-and-control-enrichment instead; do not use for checking identifiers, use tagging-and-numbering. Drafts for human review; never approves, authorises or signs off.

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

Prepares a DRAFT leadership-meeting briefing pack from the reports, meeting notes, emails and dashboard exports the user provides: one headline, metrics exactly as stated with period and source, decisions the meeting must take, risks as reported, talking points with anticipated questions, a source reference on every line and UNKNOWN where the material is silent. Use when the user asks to "brief the leadership team", "prepare the exec pack", "pull together a briefing for the steering committee", "summarise these reports for the CEO", "what do I tell the board on Monday" or "build the pre-read for the management meeting". Do not use for a formal board or committee paper seeking a resolution, use board-paper-skeleton instead; for a personal one-page prep drawn from the user's own calendar and inbox, use meeting-prep-onepager. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT board paper skeleton from the sponsor's inputs: purpose, recommendation as the sponsor states it, options including do nothing, risks, financials exactly as provided, authority to decide and the decision sought, with every claim tagged evidenced, asserted or UNKNOWN so the sponsor sees what still needs support. Use when the user asks to "draft a board paper", "structure the committee paper", "prepare the decision paper for the investment committee", "skeleton the board memo" or "what goes in the paper for the audit committee". Do not use for a pre-read or briefing pack with no resolution sought, use executive-briefing-pack instead; to record a decision already taken in a discussion, use decision-memo-builder. Drafts for human review; never approves, authorises or signs off.

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

Recall past work across Claude Code and Codex sessions. Finds decisions, research, fixes, and conversations by intent; with only a project and no question, orients on that project's recent state.

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

AI-first web search via Exa — semantic/neural ranking, category-scoped results, fresh content retrieval, and one-shot answer synthesis with citations. Use when the user needs current web information better ranked than general web search, or a grounded answer with sources.

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

Collective research memory for AI coding agents — search prior research before hitting the web, save findings back to the shared cache, view karma stats. Use when the user asks a library/API/framework question, before running WebSearch/WebFetch, or after deep web research so the next agent doesn't repay the cost. Talks directly to the hosted MCP endpoint via JSON-RPC — no local MCP server required.

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

Cursorで研究テーマを必要な資料収集・集約・分析・仮説形成へ進める。Web/ローカル資料は問いに必要な場合だけ調べ、確認事実と推測を分ける。ユーザーが /research と入力したときに使う。

難しい意思決定や論点を、必要な探索・独立したコンテキストでの熟考・統合・十分性確認へ分けて考える。single/panelの方式を使い、親だけで熟考を完了させない。調査はresearch、実装やbug修正はpir2/debugを使う。ユーザーが /deepthink と入力したときに使う。

明示されたリポジトリのSkill・Agent・呼出し・生成配布を点検または移行する。通常の実装・レビュー・調査では起動しない。

要件や設計の選択肢を整理し、実装前の決定事項を明確にする対話スキル。曖昧な要件、複数の設計案、既存パターンからの逸脱を検討するときに使う。十分に明確な小さな依頼では不要な調査や質問を追加しない。ユーザーが /brainstorm と入力したら使う。

ユーザーが明示的に /chat と入力したときの深掘り対話。問いの文脈に合わせ、必要な最新確認・ローカル確認・比較・具体例を加えて回答する。通常の短い会話を自動で重い調査へ変えず、利用可能な実際のruntime操作だけを使う。

Jev hooks の運用を支援する。「Jevの状態を診断」「利用量や費用を確認」「モードを変更」「判定を評価」「配備や不具合を調査」といった依頼で使う。該当する依頼では明示的なスキル名がなくても使い、ユーザーが /jev と入力したら必ず使う。

研究テーマを、必要な資料収集・集約・分析・仮説形成へ進める親向けスキル。Webやローカル資料は問いに必要な場合だけ調べ、確認事実と推測を分ける。実装・バグ修正・デバッグは対象外で、ユーザーが /research と入力したときに使う。

Navigate the user through reading code stop by stop to pay down understanding debt left by AI tooling. Explicit invocation only.

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

Tutor the user step by step on a plan, implementation, codebase, or topic to pay down understanding debt left by AI tooling. Explicit invocation only.

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

新しいソフトウェア/デジタルプロダクトのコンセプトを対話で固め、競合・類似プロダクトを並列調査し、軽量な仕様ドラフトを作るオーケストレーションスキル。/product-spec <一言のプロダクトアイデア> で明示的に呼び出されたときのみ使用する。

Nix パッケージがバイナリキャッシュから降ってこずローカルビルドになる原因を調査する。

既存プロダクトへの機能追加の仕様を対話で固め、既存コード・既存仕様との整合を調査して REQ-# 契約付きの docs/dev/<対象>/spec.md を作成・改訂するスキル。/feature-spec <対象名> で明示的に呼び出されたときのみ使用する。

Quiz the user on a plan, implementation, or codebase to pay down understanding debt left by AI tooling. Explicit invocation only.

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

倫理的かつ効率的な英語論文執筆を支援するスキル（水本 2025; langtech.jp/ai-writing/ に基づく）。 論文の英語化，校正，構成相談，査読対応，AI利用申告の作成を，学術的誠実性のガードレール付きで行う。 以下のような場面で必ず使用すること： 「論文の英語を直して」「英語論文を書きたい」「この段落を校正して」「査読コメントに返事を書きたい」 「AI利用の申告文を作りたい」「Introduction/Methods/Results/Discussionを書きたい」 「カバーレターを書きたい」「論文の構成を相談したい」「英文を洗練したい」 「日本語を英語にしたい」「表現の候補を出して」「時制をチェックして」 英語論文に関するあらゆる執筆支援タスクで使用する。