All skills
aktsmm avatar

/customer-workspace

@9d977df
by yamapanaktsmm/agent-skills26 stars
4

Set up and operate customer workspaces: route customer updates, record meetings, track questions and actions, manage workstreams, and prepare handoffs. Use when creating or maintaining a customer workspace, processing meeting notes or updates, reviewing next actions, or preparing a handoff. Triggers: customer workspace, 顧客ワークスペース, inbox 追加, 議事録管理, 案件更新, 宿題管理, 引き継ぎ.

Use this Skill: https://skilld.dev/gh/aktsmm/agent-skills/customer-workspace

This session only. Nothing lands on disk.

referencesworkspace-summary-rules.md

≈631 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Workspace Summary Rules

This file describes reusable rules for customer workspace summaries and handoff notes. Overview is in SKILL.md.

When to Use

  • Creating a new customer workspace and leaving a starting summary
  • Preparing a handoff note for another person
  • Writing a workspace summary that should work as a navigation entry point

Required Sections

Related File Paths

  • Include a 関連ファイルパス or equivalent section.
  • Use workspace-relative paths.
  • Add one short line for each file's role.

Source of Truth

  • Mark the latest authoritative file as 正本 or 確認先 when applicable.
  • Don't force readers to infer which file is current.

Workstream Portfolio

  • When a workspace has multiple confirmed workstreams, link workstreams/README.md from the summary.
  • Keep each workstream's current status, owner, actions, and timeline in its own README; the summary is an index and priority view, not a second status ledger.
  • Keep unconfirmed workstream ideas in workstreams/_candidates.md until the user confirms the name and scope.

Bring-Along vs Reference-Only

  • Separate files to carry into the new workspace from files kept only for reference.
  • Use this split when preparing a portable customer workspace package.

Material-Heavy Workspaces

  • If customer-shared files such as diagrams, decks, schedules, or comparison tables are part of the ongoing work, split folders by lifecycle first: _received/, _working/, _provided/.
  • Within those folders, use overall-architecture/ for cross-meeting baseline material and mtg-YYYY-MM-DD-name/ only for truly meeting-scoped material.
  • In summaries, link the ledger README or index file rather than only a deep file path when the material set is still growing.

Writing Rules

  • Don't write only generic labels such as 日報, 準備メモ, or タスク.
  • Point to the actual file path that contains the information.
  • Keep the summary short and use linked source files as the drill-down path.
  • If a summary mentions a task, meeting, or report, include the file that backs it up.

Minimal Template

## 関連ファイルパス

- Customers/contoso/workspace-summary.md
  - 起点メモ。最初に読むファイル
- Customers/contoso/profile.md
  - 顧客の基本情報。正本
- Customers/contoso/\_meetings/2026-05-20.md
  - 直近会議の要点と宿題
- Tasks/active.md
  - 全体タスクの確認先。必要なら顧客該当箇所を抜粋

Source: SKILL.md on GitHub

2 warnings5mo4 checks · Risk SAFE
  • Gen Agent Trust Hub5mo

    This skill provides a structured environment for managing customer workspaces, including automated meeting minutes conversion and chat information accumulation. It operates locally using templates and a PowerShell setup script. No malicious behavior was detected.

  • Socket5mo

    No alerts

  • Snyk5mo

    Risk: MEDIUM · 1 issue

  • Runlayer7mo

    11/11 files flagged

Signed by skilld at 9d977df. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 18 hours ago.

Activeupdated last week
user-invocable
true
metadata
{
  "author": "yamapan (https://github.com/aktsmm)"
}
Other metadata
argument-hint
Customer workspace name or an existing-workspace task (meeting, update, follow-up, handoff)

README badge

README badge for aktsmm/agent-skills/customer-workspace