Claude Skills by wfukatsu

Google Slides デッキ生成を、スキル選択から検証・納品まで共通契約に沿って実行する 軽量なパイプラインルーター。

Author and maintain the slide templates in the slide-templates/analysis pack, including the drawing primitive a new framework needs. Use for: 分析フレームのテンプレートを追加・修正, add an analysis-framework template. Not: generic page templates (slide-template-creator); running an analysis (current-state-analysis).

Build the two maps a B2B deal turns on: an influence map of the buying committee and a discovery map of what is confirmed versus still assumed. Use for: ステークホルダーを整理, 関与者マップ, 意思決定者と承認経路, MEDDPICC, ディスカバリー, パイプラインレビュー, 提案前に何が未確認かを洗い出す. Not: the proposal deck itself (scalar-proposal-slides / google-slides-template); new reusable page templates (slide-template-creator).

Turn dated tasks and events into calendar slides — month grid, day-by-day gantt, or a day-by-day task list — with Japanese holidays, multi-day spans and automatic page splits. Use for: カレンダーでスケジュールを見せたい, 月間予定表, 日単位のガント, 日次タスク一覧, calendar slide, monthly calendar, daily gantt. Not: month-level plans (planning/gantt-schedule); milestone-only timelines (planning/milestone-timeline).

Run current-state and problem-identification frameworks on the user's material and render the results as slides: PEST, Five Forces, process pain-points, logic tree, KPI tree, why-why, fishbone, Pareto, As-Is/To-Be gap, impact-effort priority matrix, plus SWOT / 3C. Use for: 現状分析, 課題を特定・構造化, 真因分析, As-Is/To-Be 整理, 課題の優先順位付け, ヒアリングメモを分析スライドに. Not: authoring new templates (analysis-template-creator); deck generation mechanics (google-slides); visual QA (slide-qa).

Draw dense diagrams — cloud architecture (AWS/GCP/Azure), data flow, network — as draw.io files, export them to PNG headlessly, and place the PNG in a slide-forge deck. The editable .drawio source is archived in the deck's Drive folder so the user can keep editing it. Use for: draw.io で図を作って, クラウド構成図, データフロー図, ネットワーク構成図, cloud architecture diagram, or any diagram too dense for native Slides shapes.

Generate or update a Google Slides deck from a registered master template. The main deck-generation workflow — prefer it whenever a corporate master exists. Use for: テンプレートからデッキを作って, 提案資料を作成して, 既存デッキのこのページを直して, make a deck from our template, update slides 3 and 7, register this master. Not: a deck with no corporate master (google-slides); designing a new master (template-forge); filling only the empty image frames (image-slots).

Generate Google Slides decks and infographics from scratch, with no registered corporate master: spec-driven decks on a blank 16:9 template, or code-first decks with offline layout validation for diagram-heavy material. Use for: Google Slides を作って, スライドを生成, インフォグラフィクスを作って, create Google Slides, generate slides, create infographic.

Keep the hearing sheet as data and move it between Markdown, Excel and Google Spreadsheet in both directions — hand one to a customer or partner to fill in, read the answers back, and report what is still unconfirmed. Use for: ヒアリングシートを作って, ヒアリング項目を Excel で, スプレッドシートで顧客に渡したい, 記入してもらったシートを取り込んで, 何が聞けていないか. Not: slides that do the asking (hearing-slides); minutes and email into the record (scalar-deal-intake).

Slides whose job is to collect information rather than deliver it: the agenda of what you need to hear, a fill-in sheet for the meeting, an event poll, and the page that says where to send the answers. Driven by the gaps in a hearing sheet. Use for: 聞くためのスライド, ヒアリング用の資料, 足りない情報を集めるスライド, イベントで情報を集めたい, 記入してもらう資料. Not: internal "who do we ask next" pages (scalar-ae-materials / b2b-account-maps); the proposal itself (scalar-proposal-slides).

Fill the empty image slots of an existing Google Slides deck with AI-generated pictures composed for each frame's shape. Runs on any accessible deck URL, including decks slide-forge did not generate. Use for: 表紙に絵を入れて, 章扉の画像枠を埋めて, 空いている画像枠に画像を生成, fill the image placeholders. Not: decks still being generated (put aiImage in the spec instead); shape-drawn diagrams; replacing pictures already in place; verification (slide-qa).

Turn a nexus-architect project's reports and UI mocks into an explanation deck, even while the pipeline is still unfinished. Covers architect / product / infra / scalardb. Use for: nexus-architect のレポートを説明資料にして, 分析結果をスライドに, アーキテクチャ分析の報告資料, 途中まででいいので資料化. Not: producing the reports themselves (nexus-architect's own skills); new slide templates (slide-template-creator); visual QA (slide-qa).

Export a generated Google Slides deck to PowerPoint (.pptx) via the Drive API, preserving it exactly as generated. Invoked by the generation skills when the user chooses PPTX at intake, and runs standalone on any accessible deck URL. Use for: PPTX でも出力して, PowerPoint 形式でほしい, パワポで納品, export to PowerPoint. Not: authoring or editing PPTX files directly (document-skills:pptx); QA, which runs on the Slides deck via slide-qa before export.

Maintain a per-customer sales ledger (account.json) for a Scalar Account Executive — what is confirmed, who decides, what is unknown, what to do next — rendered as a Google Slides activity plan whose URL never changes. Use for: 活動計画, アカウントプラン, 商談の記録, ステージ・フォーキャスト・BANT の レビュー, 次に確認すべきこと, アカウントの Drive 準備. Not: the annual Account Planning Session decks (scalar-account-planning-session); one visit's materials (scalar-ae-materials); the customer proposal (scalar-proposal-slides); the maps (b2b-acc...

Build the Account Planning Session decks for a customer that already has a ledger: a full Plan Document for the account team and a nine-page executive review deck, from one aps.json. Use for: APS, 年次・半期のアカウントレビュー, 役員向けレビュー資料, 企業グループの組織・役員・キーパーソンを整理. Not: the per-visit ledger and activity plan (scalar-account-plan); one visit's materials (scalar-ae-materials).

Build what a Scalar Account Executive needs for one customer visit, chosen by deal phase and audience: the customer-facing one-pager, the internal visit plan, the WPS win plan, and the Deal Desk approval packet. Use for: 訪問・面談の準備, フェーズ 0〜6 の会話に使う資料, visit plan, WPS, Deal Desk, 社内の承認やリソースを取りたい. Not: the standing activity plan (scalar-account-plan); the formal proposal (scalar-proposal-slides); the stakeholder maps (b2b-account-maps).

Turn raw deal material — meeting minutes, email threads, Slack, CRM exports, customer documents — into per-stage records and a hearing sheet. Extracts facts with a source and a confidence level, and turns every gap into a question with an owner and a due date. Use for: 議事録を整理して, メールから商談情報をまとめて, ヒアリングシートを埋めて, ステージごとに整理して, ステージを上げてよいかの判断. Not: the ledger and activity plan (scalar-account-plan); one visit's materials (scalar-ae-materials); the maps (b2b-account-maps); the proposal (scalar-propos...

Turn pre-deal signals — webinar and seminar attendance, inbound enquiries, download logs, community questions, event badge notes, partner referrals, CRM/MA exports — into segment definitions, five-stage nurture tracks and a content ledger. Works on segment types, never on named individuals. Use for: ナーチャリングを設計して, リード育成, 問い合わせからセグメントを起こして, ウェビナーの参加者を整理, コンテンツの棚卸し, MQL / SQO. Not: once a lead is handed over — per-customer records (scalar-deal-intake), the deck (scalar-product-slides), the propo...

Build Scalar Inc. decks end to end — company introduction, product introduction, feature catalog, use cases — researched from the official site and developer docs. Use for: 製品紹介スライド, 機能紹介スライド, 会社紹介スライド, Scalar 紹介資料, ユースケーススライド. Not: customer-specific proposals driven by a customer's challenges (scalar-proposal-slides); decks about anything other than Scalar (google-slides / google-slides-template); PPTX authoring (document-skills:pptx).

Build a customer-specific Scalar solution proposal: start from the customer's challenges (hearing notes, meeting minutes) and map them to ScalarDB / ScalarDL. Use for: 提案書を作って, 提案スライド, 顧客課題, ソリューション提案, 〈顧客名〉向けの提案資料. Not: introduction decks with no specific customer (scalar-product-slides); non-Scalar proposals (google-slides-template); PPTX authoring (document-skills:pptx).

Read and change the two slide-forge switches in config/settings.json: whether Gemini generates images at all, and whether the deliverable is Google Drive / Slides or a local folder of .pptx. Use for: 設定を変えたい, 設定を確認して, 画像生成をオフにして, 出力先をローカルにして, PowerPoint で出したい, Google Drive に出したい. Not: OAuth credentials and API keys, never read or written here; the Drive sales root in config/sales.json (scalar-account-plan); per-deck choices such as QA or template selection, which stay in intake; exporting an ...

Visual QA of a generated deck from thumbnails: inspect every page against a defect checklist (overflow, overlaps, wrong connectors, weak contrast) and drive the fix-and-regenerate loop. The generation skills invoke it when the user opts in (the default); it also runs standalone on any deck URL. Use for: スライドを検証して, デッキを QA して, サムネイルで確認して, visual QA. Not: pre-generation offline checks (--dry-run / validate_layout.py stay in the generation skills); content fact-checking; PPTX files (pptx-export).

Create, register, update and catalog reusable single-slide templates. These are content-level page templates, not Google Slides masters. Use for: ページテンプレートを追加, SWOT・比較・プロセスなどのスライド型を作って, 既存スライドやスクリーンショットをテンプレート化, 登録済みテンプレートの一覧と保守. Not: brand/master creation (template-forge); deck generation (google-slides / google-slides-template); visual QA of finished decks (slide-qa).

Generate line-item spreadsheets — estimates, BOMs, cost breakdowns, comparison tables — as Excel (.xlsx) and/or Google Spreadsheet from one JSON spec. Companion to a deck, and also standalone. Use for: 見積もりを作って, 見積書, 明細表, 費用内訳を Excel に, BOM をスプレッドシートに, cost breakdown spreadsheet. Not: free-form or existing-file xlsx work (document-skills:xlsx); reading or analyzing spreadsheets; tables drawn inside slides.

Create and register a brand-new Google Slides master from a design spec — brand colors, fonts, logo, footer — without touching the Slides UI, registered as templates/<id>.json. Use for: 新しいテンプレートを作って, ブランドに合わせたマスターを作成, 会社カラーのテンプレート, create a new master. Not: hand-tuning an existing master's design (Slides UI); PPTX/.potx templates (document-skills:pptx); generating decks from a template (google-slides-template).