customer-workspace
Customer workspace initialization skill. Provides inbox (information accumulation), meeting minutes management, and auto-classification rules. Use for "setup customer workspace" or "add inbox feature" requests.
Best use case
customer-workspace is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Customer workspace initialization skill. Provides inbox (information accumulation), meeting minutes management, and auto-classification rules. Use for "setup customer workspace" or "add inbox feature" requests.
Teams using customer-workspace should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/customer-workspace/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How customer-workspace Compares
| Feature / Agent | customer-workspace | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Customer workspace initialization skill. Provides inbox (information accumulation), meeting minutes management, and auto-classification rules. Use for "setup customer workspace" or "add inbox feature" requests.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Customer Workspace Skill
Initialize customer-specific workspaces with information accumulation, meeting notes management, and handoff-ready summaries.
## When to Use
- **Customer workspace**, **inbox**, **meeting notes**, **workspace summary**, **handoff**
- Setting up per-customer workspaces
- Adding inbox or meeting minutes management
- Creating handoff-ready workspace summaries with source file paths
- Implementing auto-classification rules for customer information
## Features
| Feature | Description |
| --------------------- | ---------------------------------------------------- |
| **Inbox** | Paste chat/email for auto-classification |
| **Meeting Notes** | Convert Teams AI notes to template format |
| **Questions** | Extract questions/actions from meeting log |
| **Auto-Routing** | Route input based on pattern detection |
| **Customer Profile** | Centralized customer information |
| **Workspace Summary** | Handoff summary with related file paths |
| **Next Actions** | Per-MTG homework workspace with bidirectional links |
| **Material Split** | Optional split for customer originals, working copies, and customer-facing files |
---
## Quick Start
```powershell
# Basic
.\scripts\Initialize-CustomerWorkspace.ps1 -CustomerName "Contoso Inc"
# Full options
.\scripts\Initialize-CustomerWorkspace.ps1 `
-CustomerName "Contoso Inc" `
-ContractType "MACC" `
-ContractPeriod "2025/04 - 2028/03" `
-KeyContacts "John Doe (Infra Lead)"
```
If PowerShell is unavailable, manually create the same folders, copy the prompt/template files from `assets/`, and create `README.md` plus `workspace-summary.md` from the workspace root templates.
## Generated Structure
```
{workspace}/
├── README.md ← Start here / workspace overview
├── workspace-summary.md ← Handoff-ready summary
├── .github/
│ ├── copilot-instructions.md ← Auto-routing rules
│ └── prompts/ ← Inbox, meeting notes, questions
├── _inbox/{YYYY-MM}.md ← Inbox files
├── _questions/{YYYY-MM}.md ← Accumulated questions (optional)
├── _customer/profile.md ← Customer profile
├── _templates/ ← Templates
├── meeting-notes/ ← Meeting minutes (one file per MTG)
└── next-actions/ ← Per-MTG homework workspace
├── to-YYYY-MM-DD/ ← Tasks for the next MTG
│ ├── README.md ← Progress board
│ ├── homework/ ← Customer-agreed homework
│ ├── proposals/ ← Self-initiated proposal prep
│ └── research/ ← Supplementary research/validation
└── ongoing/ ← Continuing items without a deadline
```
## Optional Material Folders
When customer-shared diagrams, decks, tables, or schedules start to accumulate, split by lifecycle first and scope second.
```text
_received/ ← customer originals only
overall-architecture/ ← cross-meeting baseline material
mtg-YYYY-MM-DD-name/ ← meeting-specific material
_working/ ← internal edited / annotated / draft copies
overall-architecture/
mtg-YYYY-MM-DD-name/
_provided/ ← customer-facing copies, send-out decks, projection versions
overall-architecture/
mtg-YYYY-MM-DD-name/
```
- Use `_received/` for customer originals and avoid editing files in place.
- Use `_working/` for annotated copies, extracted pages, redlines, and draft comparisons.
- Use `_provided/` only for versions safe to show or send to the customer.
- Use `overall-architecture/` when the material stays relevant across multiple meetings.
- Use `mtg-YYYY-MM-DD-name/` only when the material is truly scoped to one meeting.
---
## Auto-Routing Patterns
| Pattern | Action |
| ---------------------------- | ----------------- |
| "Generated by AI" | → Meeting notes |
| Meeting memo with agenda / tasks / next meeting | → Meeting notes + Questions |
| Name + datetime + short text | → Inbox |
| Contains `From:` `Date:` | → Inbox |
| Bullet points / short memo | → Inbox |
| Question format | → Normal response |
## Default Tags
`#network` `#cost` `#contract` `#proposal` `#ai` `#container` `#meeting` `#support` `#organization` `#deadline` `#internal`
## Next Actions (per-MTG homework workspace)
Carve homework, proposal prep, and supplementary research out of meeting notes into a date-scoped `next-actions/to-YYYY-MM-DD/` folder.
- **Folders**: `homework/` (customer-agreed), `proposals/` (self-initiated), `research/` (supplementary)
- **Bidirectional links**:
- In meeting notes, every decision/homework row links to the corresponding `next-actions/to-YYYY-MM-DD/.../xxx.md`.
- In each task file, the header records `出どころ:` pointing back to the meeting note (or `自主提案` / `自主検証`).
- **Progress states**: `not-started` / `in-progress` / `blocked` / `done` / `dropped`. Only the state table lives in `to-YYYY-MM-DD/README.md`; details stay in each task file.
- **Why split by type**: mixing `proposals` into homework breaks the link to meeting notes and turns self-initiated ideas into apparent customer commitments.
- Full rules and templates: see `Next Actions Workspace` section in [assets/copilot-instructions.md](assets/copilot-instructions.md).
---
## Done Criteria
- [ ] Workspace folder created
- [ ] `README.md` exists at workspace root
- [ ] `workspace-summary.md` exists at workspace root
- [ ] `_inbox/{YYYY-MM}.md` exists
- [ ] `_questions/{YYYY-MM}.md` exists
- [ ] `_customer/profile.md` configured
- [ ] Auto-routing rules working
## Key References
- [Inbox Rules](references/inbox-rules.md)
- [Meeting Minutes Rules](references/meeting-minutes-rules.md)
- [Workspace Summary Rules](references/workspace-summary-rules.md)
## Assets
- `assets/_templates/` - Template files
- `assets/_templates/next-actions-readme.md` - Per-MTG progress board template
- `assets/_templates/next-actions-task.md` - Single task file template (homework / proposal / research)
- `assets/inbox.prompt.md` - Inbox prompt
- `assets/convert-meeting-minutes.prompt.md` - Meeting notes prompt
- `assets/extract-questions.prompt.md` - Question extraction prompt
- `assets/copilot-instructions.md` - Auto-routing rules