copilot-agent-workspace: Skill for Claude Code

.github/skills/customer-research/SKILL.md

customer-research is a skill for Claude Code, Codex from kanazawazawa/copilot-agent-workspace. It costs 50 tokens per session (1,029 once invoked), scanned A, original, MIT.

A customer-research skill for collecting public information about companies, industries, technology use, and relevant case studies.

In plain words
What is it for?
It is for researching a target company, industry trends, cloud adoption, competitors, Microsoft or Azure examples, and possible solution directions.
Why use it?
It turns scattered research into a structured brief for proposal and pre-sales preparation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is kanazawazawa/copilot-agent-workspace's own configuration. It tells Claude Code and Codex how to work on copilot-agent-workspace itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything copilot-agent-workspace configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kanazawazawa/copilot-agent-workspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/kanazawazawa/copilot-agent-workspace/master/.github/skills/customer-research/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/kanazawazawa/copilot-agent-workspace

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for customer-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/kanazawazawa/copilot-agent-workspace/customer-research/github.svg)](https://agentmods.dev/skills/kanazawazawa/copilot-agent-workspace/customer-research)
Your own site
<a href="https://agentmods.dev/skills/kanazawazawa/copilot-agent-workspace/customer-research"><img src="https://agentmods.dev/badge/skills/kanazawazawa/copilot-agent-workspace/customer-research/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for customer-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/kanazawazawa/copilot-agent-workspace/customer-research"><img src="https://agentmods.dev/badge/skills/kanazawazawa/copilot-agent-workspace/customer-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,029 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.01029
Opus 5 $0.00025 $0.00515
Sonnet 5 $0.00010 $0.00206
Haiku 4.5 $0.00005 $0.00103

Measured 10d ago against content hash 094ba6170fcb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

customer-research scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/skills/customer-research/SKILL.md · 122 lines

What it actually says

顧客情報調査スキル

概要

顧客企業や業界に関する情報を効率的に調査し、 提案活動やプリセールス資料の作成に役立つインサイトを提供するスキルです。

トリガーワード

以下のキーワードが含まれる場合にこのスキルを使用する:

  • 「顧客情報」「顧客調査」「企業調査」
  • 「業界動向」「業界調査」「市場調査」
  • 「導入事例」「ケーススタディ」「事例」
  • 「競合分析」「提案準備」

使用しない場合

  • 技術仕様の確認のみ(→ ms-learn-research を使う)
  • 社内プロジェクトの情報整理

調査ワークフロー

Step 1: 調査目的の確認

  • 対象顧客: 企業名、業界
  • 調査の目的: 初回提案?深掘り?更新?
  • 必要な情報: 企業概要?IT戦略?競合?事例?

Step 2: 情報収集

  1. 企業の基本情報

    • Web 検索で企業概要、事業内容、最新ニュースを取得
    • IR 情報(上場企業の場合)
  2. 業界動向

    • 業界レポート、トレンド記事を検索
    • DX 動向、クラウド採用状況
  3. Microsoft / Azure 関連

    • microsoft_docs_search で導入事例を検索
    • クエリ例: "case study [業界名] Azure"
    • microsoft_docs_search で業界ソリューションを検索
  4. 技術的なコンテキスト

    • 競合クラウド(AWS, GCP)との比較ポイント
    • 導入済みの主要システム情報(公開情報ベース)

Step 3: 整理とアウトプット

出力テンプレート

企業概要テンプレート

## [企業名] 調査サマリー

### 基本情報
| 項目 | 内容 |
|------|------|
| 企業名 | |
| 業界 | |
| 従業員数 | |
| 売上規模 | |
| 主な事業 | |

### IT / DX の取り組み
- [公開情報ベースで記載]

### Microsoft との関係
- 既存導入製品(公開情報ベース)
- 類似業界の Azure 導入事例

### 提案の方向性(仮説)
- ビジネス課題 → 技術ソリューション候補

業界概要テンプレート

## [業界名] 概要

### 業界トレンド
- 直近のキートレンド 3-5 点

### DX / クラウド動向
- クラウド採用率、主要な利用領域

### よくある課題
- 業界共通のIT課題

### Azure ソリューション候補
| 課題 | Azure サービス | 概要 |
|------|---------------|------|

出力ルール

保存先

  • 企業調査: output/customers/企業名/profile.md(最新の企業概要)
  • テーマ別調査: output/customers/企業名/YYYY-MM-DD_HHmmss_調査テーマ.md
  • 業界調査: output/research/YYYY-MM-DD_HHmmss_業界名_調査/report.md

品質基準

  • 公開情報のみを使用する(機密情報は扱わない)
  • 情報源を明記する
  • 推測・仮説は「仮説:」「推定:」と明記する
  • 情報の鮮度(いつの情報か)を意識する
  • 数値データは元ソースを確認できるようにする

注意事項

  • 個人情報は扱わない
  • 非公開の顧客内部情報は記載しない
  • 競合の批判ではなく、差別化ポイントとして記載する
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 122 lines · 50 tokens per session scan A 094ba6170fcb

Subscribe to this mod's changes

customer-research is a skill published in the GitHub repository kanazawazawa/copilot-agent-workspace (5 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 1,029 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens