「agent-skill」の検索結果

Proposes tag and number structures for the new lines and instruments in a P&ID draft according to the project's numbering procedures, checks every tag extracted from the PFD against the quoted procedure format, and lists cross-section identifier mismatches and the registry checks a human must run. Never invents a numbering convention, never alters a PFD tag and never assigns a sequence number the procedure reserves for the registry. Use when the user asks to "run the tagging and numbering section", "check the tags against the numbering procedure", "propose the tag structure for the new lines and instruments" or "list the registry checks before validation" after the process safety flags. Do not use for validating the four sections, use validation-and-review-package instead; do not use for instrument content, use instrumentation-and-control-enrichment. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or plan in character as a Chief Financial Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, finance risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CFO review", "pressure-test the numbers in this business case", "what would a CFO say about this", "challenge the payback and run costs" or "prepare this for the investment committee". Do not use for delivery or capacity questions, use coo-reviewer instead; for architecture or vendor questions, use cto-reviewer; for positioning or demand, use cmo-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT interface register between disciplines or parties from meeting notes, action lists and drawings or document lists: one row per interface with the requesting and providing party, the information needed, the related document number, the need-by date with its source, the status as minuted and a quoted source, plus UNKNOWN and questions where the notes are silent. Never sets a date, rates priority, assigns ownership beyond what the notes state or closes an interface. Use when the user asks to "build an interface register from these minutes", "list the interfaces between piping and civil", "who owes what to whom on this package", "update the interface register from this week's meeting" or "turn these action items into an interface list". Do not use for recording a design or document change raised in a meeting, use management-of-change-intake instead. Drafts for human review; never approves, authorises or signs off.

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

Reads one spreadsheet, CSV export or pasted table together with the user's question and drafts an insight pack: a data profile, observations cited to named columns and values and framed as leads, caveats, and suggested charts and follow-up analyses. Every figure carries the label "as read, verify in source"; correlation is never stated as causation. Use when the user asks to "profile this spreadsheet", "what does this data say", "find anomalies in this extract", "give me a first read on this CSV" or "summarise this table". Do not use for a purchase order log or spend extract, use purchase-order-anomaly-review instead; for actuals versus budget, use budget-variance-explainer instead; for a report that arrives by email on a schedule, use report-attachment-analyzer instead. Drafts for human review; never approves, authorises or signs off.

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

Reads a cash forecast (spreadsheet, model export, pasted table or the narrative that accompanies it) and returns a DRAFT assumptions sheet: every assumption the forecast rests on, stated or implied by the figures, with its value as read, its location in the model, the cash lines it drives, its stated source or "not stated", the evidence that would test it, an owner, and one neutral challenge question, so a reviewer can work through the assumptions one by one. Use when the user asks to "list the assumptions behind this cash forecast", "what is this cash flow forecast assuming", "prepare the challenge questions for the treasury review", "pull out the drivers of the 13-week cash forecast" or "build an assumptions register for the liquidity plan". Do not use for actuals against budget by line, use budget-variance-explainer instead; do not use for the case behind a capital request, use capex-request-pack instead. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or product plan in character as a Chief Product Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, product and adoption risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CPO review", "pressure-test this product plan", "what would a CPO say about this", "challenge the user evidence" or "check the roadmap opportunity cost". Do not use for positioning, messaging or launch marketing, use cmo-reviewer instead; for internal staff adoption of a rollout, use frontline-skeptic-reviewer; for what a change asks of paying customers, use customer-advocate-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Drafts a document transmittal (header, one line per document with revision and purpose of issue, distribution with action required, blank acknowledgement block) from a document list and the project's transmittal template, with UNKNOWN for anything not stated and questions for document control. Never assigns a transmittal number, changes a revision or marks anything issued. Use when the user asks to "draft a transmittal for these documents", "fill in the issue sheet" or "prepare the document issue note". Do not use for checking a register or deliverables list, use master-document-register-check instead. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or plan in character as a Chief Data Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, data and AI governance risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CDO review", "pressure-test the data governance in this plan", "what would a CDO say about this", "check the metric definitions and data sources" or "prepare this for the data governance board". Do not use for security controls or third-party security risk, use ciso-reviewer instead; for contract, liability or regulatory terms, use general-counsel-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Pre-checks one expense claim or travel plan, line by line, against the expense or travel policy the user supplies, and returns a DRAFT precheck sheet: the policy clause matched to each line, the limit quoted as the policy states it, whether the amount sits within, at or outside that limit, missing receipts, pre-approvals or justifications, and neutral questions for the approver and the claimant, with UNKNOWN wherever the policy or the claim is silent. Use when the user asks to "check this expense claim against policy", "pre-check my travel request", "is this claim within policy", "review these expenses before I submit them", "what receipts or approvals are missing" or "prepare the approver's questions for this claim". Do not use for a purchase order log or spend extract, use purchase-order-anomaly-review instead; do not use to compare a policy against a standard or regulation, use policy-gap-review instead. Drafts for human review; never approves, authorises or signs off.

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

Triages a batch of customer support tickets (helpdesk export, shared mailbox, chat transcripts, web forms) into one row per ticket with category, urgency graded on the evidence in the ticket, suggested next action and owner, plus a DRAFT customer reply for every ticket that needs one, returned as one Markdown pack. Use when the user asks to "triage these tickets", "sort the support queue", "what needs an answer first", "categorise this backlog", "draft replies for these tickets" or "build today's queue review". Do not use for internal requests from colleagues, use request-intake-triage instead; for one long thread that needs handing over, use escalation-summary; for a personal mailbox, use inbox-triage. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT data dictionary from a schema export, table definition, sample rows or a partial existing dictionary: one row per field with the name as stated, type as stated or observed, meaning quoted from the documentation supplied, owner, allowed values, and UNKNOWN wherever no source defines the field, plus a gap list for the data owner. Never infers a definition from a column name. Use when the user asks to "build a data dictionary for this table", "document these columns", "what does each field mean", "turn this schema export into a dictionary" or "fill in the field definitions from these documents". Do not use for profiling values or finding patterns in the data, use dataset-insight-pack instead; for metric definitions, use kpi-definition-sheet; for logging data defects, use data-quality-issue-log. Drafts for human review; never approves, authorises or signs off.

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

Turns one long support ticket thread (helpdesk history, email chain, chat transcript, call notes) into a one-page DRAFT escalation summary: the customer's ask in their own words, account context as stated, a dated history, what was tried and the stated result of each attempt, the current state, and what is needed from whom by when, every line referenced to a message and every missing fact marked UNKNOWN. Use when the user asks to "escalate this ticket", "summarise this thread for tier two", "write the hand-over for this case", "what has been tried so far", "brief engineering on this customer issue" or "prepare the escalation note". Do not use for a batch of tickets, use ticket-triage-pack instead; for the review after an outage, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.

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

Maps every proposed P&ID object from an accepted enrichment draft to the generic family, catalogue class and required attributes the project's intelligent P&ID authoring tool would need, as a readiness table with UNKNOWN wherever the project catalogue extract is not provided, plus connectivity readiness per line and a numbered list of import blockers. Mapping only: it never writes to the tool, never produces an import file and never claims a class exists in the catalogue. Use when the user asks to "build the readiness map", "show how far the draft is from a sandbox import", "list what would block the import", "map the objects to the tool catalogue" or "check attribute readiness against the catalogue extract" after gate G3. Do not use for validating the discipline sections or assembling the review package, use validation-and-review-package instead. Drafts for human review; never approves, authorises or signs off.

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

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

明示されたCodex・CursorのSkill運用移行を、指定設計と既存点検に基づき適用する。通常の実装依頼では起動しない。

AIコーディングエージェント向けの共通コーディングルール。コードの実装・修正・リファクタリング・レビュー時に使用し、前提確認、最小限の変更、検証に加え、空行・処理の区切り・目的と理由のコメントによる人間が後で理解できる可読性を厳守する。

添付された複数の画像を一括で圧縮・リサイズするスキル。「画像を圧縮して」「このスクショを軽くして」「リサイズして」「画像を小さくして」などのリクエストで使用する。Pillowで長辺1920pxにリサイズし、JPEG/PNGで出力先ディレクトリに保存する。

AGENTS.md / CLAUDE.mdの作成・編集・整理を行うスキル。CLAUDE.mdを50行以下を推奨とし、詳細ルールはrules/やスキルにモジュール化して分割管理する。以下のリクエストで使用する: (1)「CLAUDE.mdを作って」「AGENTS.mdを整理して」などCLAUDE.mdの新規作成・編集、(2)「ルールを追加して」「rules/に分割して」などルールの追加・分離、(3)「ディレクトリ構成を更新して」など参照の更新、(4) 新しいディレクトリやルールファイルを作成した後のCLAUDE.md反映。

URL・画像・テキスト要件からAIコーディングエージェント向けのDESIGN.mdを生成するスキル。「example.comをDESIGN.md化して」「このサムネをDESIGN.md化して」「クールでポップなLP用のDESIGN.mdを作って」といったリクエストで使用する。Claude Code / Cursor / Stitch に渡せば一貫したUIを生成できる、getdesign.md / awesome-design-md 準拠の9セクション構成のデザイン仕様書を出力する。CSS解析・画像目視抽出・要件生成の3パターンに対応。

AI事業者ガイドライン（経済産業省・総務省、第1.2版、2026年3月31日）に基づいて、AIに関する取り組みのOK/NG判断・注意点・チェックリストを回答するスキル。以下のような質問で使用する: (1)「学習データに〇〇を使っていいか」「個人情報をAIに入力してもいいか」など具体的な行為のOK/NG確認、(2)「セキュリティ対策は何をすればいいか」「社内AIルールをどう作るか」などガバナンス構築の相談、(3)「AI開発者/提供者/利用者として何をすべきか」など立場別の取り組み確認、(4)「ガイドラインを更新して」などナレッジ更新の指示、(5)「グラレコ画像を生成して」「イラストにまとめて」などガイドライン内容の画像生成プロンプト作成

Implement Feature-First architecture with Riverpod state management and Flutter Hooks in Flutter applications

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

Next.js + Better Auth + PostgreSQL を Docker で構築し、Cloud Run へデプロイするスキル。ローカル開発環境のセットアップから Docker Compose、Dockerfile 作成、Cloud Run + Cloud SQL + Secret Manager を使った本番デプロイまでをカバーする。「Next.js と Better Auth でアプリを作りたい」「Docker で PostgreSQL を使いたい」「Docker で構築したい」「Docker Compose を使いたい」「アプリを Docker 化したい」「Dockerfile を書きたい」「Cloud Run にデプロイしたい」「Cloud SQL や Secret Manager を使いたい」ときに使う。

Nano Banana 2（Google Gemini gemini-3.1-flash-image-preview）を使って画像を生成するスキル。「画像を生成して」「〇〇のイラストを作って」「Nano Bananaで画像を作って」「グラレコ風の画像を生成して」などのリクエストで使用する。プロンプトを受け取りpythonスクリプトを実行、タイムスタンプ付きPNGを images/generated/ に出力する。

複雑なコードベースを体系的に分析し、アーキテクチャを可視化・ドキュメント化して新規開発者のオンボーディングを支援する汎用スキル。成果物は必ず `docs/` 配下に分割出力する。以下のリクエストで使用する：(1)「このコードベースを分析して」「全体像を教えて」など概要把握、(2)「アーキテクチャドキュメントを作って」「C4図を生成して」など設計ドキュメント生成、(3)「オンボーディング資料を作って」など新規開発者向け資料作成、(4)「技術的負債を洗い出して」など負債評価、(5)「機能一覧を出して」など機能インベントリ生成、(6)「この機能を操作したら何が起きるか追跡して」などユーザー操作フロー追跡、(7)「新機能の実装手順を出して」などフロント／バック横断の実装ガイド生成。特定の言語・フレームワーク・ディレクトリ構成に依存せず、どのリポジトリでも利用できる。