ワンクリックでManusで任意のスキルを実行

summarise-customer-call

スター0

フォーク0

更新日2026年5月26日 17:02

After a customer call (transcribed or hand-noted), file a structured summary to wiki/research/ and trigger extract-commitments. Use when founder finishes a call and says "@customer-success file this call" or similar.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

jezweb

jezweb/office-town-pack-startup

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Summarise customer call

Customer-call notes are gold: feature requests, churn signals, expansion opportunities, commitments. Every call should produce a structured entry in 2 minutes flat.

When this skill fires

Founder shares a transcript or hand-written notes from a customer call
A meeting note lands in the inbox with kind:customer-call-raw
Customer-success agent is asked to "debrief" a call

The shape

Read the source completely (transcript / notes / audio summary)
Identify the org — match to existing wiki/orgs/?entity_type=client entry; create if new
Capture structured fields:
- title, org_slug, primary_contact, attendees, duration_min, sentiment, next_call_due
Write the body in this shape:

## Summary

[2-3 sentence executive summary]

## What's working

- [specific positive signal — name the feature, name the impact]

## What's NOT working

- [specific friction — name the issue, name the workaround they tried]

## Asks

- [explicit feature request or commercial ask, with priority you'd assign]

## Commitments made

- [explicit "I/we will..." statements from our side, with deadlines]

## Next call: <date>

Save to wiki/research/<date>-<org-slug>-<topic>.md with kind:customer-call
Fire extract-commitments skill on the new entry
Update org sentiment in wiki/orgs/<slug>/entity.md if it shifted
Flag boss if anything urgent surfaced (churn signal, escalation, etc.)

Voice rules

Be specific about features (name them) and people (name them)
Quote the customer where their phrasing matters
Don't paper over negatives — "they're frustrated with X" beats "they had some questions about X"

Anti-patterns

Generic summary ("they liked the product overall") — useless
Stripping out customer-quote details to "save space"
Skipping the commitments section because "I'll remember"
Forgetting to update the org's sentiment when it noticeably shifted

このリポジトリの他の Skills

同じリポジトリ

draft-investor-update

jezweb/office-town-pack-startup

Drafts the monthly investor update — pulls metrics, surfaces wins + struggles, formats per the founder's voice. Use on the 1st of each month, or when boss asks for a draft, or when investor-relations fires a scheduled monthly routine.

2026-05-260

extract-commitments

jezweb/office-town-pack-startup

After filing a meeting, customer call, investor call, or any conversation entry, scan the body for explicit commitments (I'll ship X by Y, send Z by Friday) and create structured commitment entries in wiki/commitments/. Use whenever a new meeting note lands; also use to retroactively scan an existing entry for missed commitments.

2026-05-260

runway-check

jezweb/office-town-pack-startup

Compute current runway, burn trend, and forecast end-of-runway. Use when boss or bookkeeper is asked for runway, on a scheduled monthly check, or before any fundraising conversation.

2026-05-260

track-candidate

jezweb/office-town-pack-startup

Move a candidate through the hiring pipeline — sourced, contacted, first-call, case-study, offer, hired, passed. Captures notes per stage; never lets a candidate ghost-drift. Use when recruiter advances a candidate or the founder adds a new one.

2026-05-260

Summarise customer call

Customer-call notes are gold: feature requests, churn signals, expansion opportunities, commitments. Every call should produce a structured entry in 2 minutes flat.

When this skill fires

Founder shares a transcript or hand-written notes from a customer call

A meeting note lands in the inbox with kind:customer-call-raw

Customer-success agent is asked to "debrief" a call

The shape

Read the source completely (transcript / notes / audio summary)

Identify the org — match to existing wiki/orgs/?entity_type=client entry; create if new

Capture structured fields:

title, org_slug, primary_contact, attendees, duration_min, sentiment, next_call_due

Write the body in this shape:

## Summary [2-3 sentence executive summary] ## What's working - [specific positive signal — name the feature, name the impact] ## What's NOT working - [specific friction — name the issue, name the workaround they tried] ## Asks - [explicit feature request or commercial ask, with priority you'd assign] ## Commitments made - [explicit "I/we will..." statements from our side, with deadlines] ## Next call: <date>

Save to wiki/research/<date>-<org-slug>-<topic>.md with kind:customer-call

Fire extract-commitments skill on the new entry

Update org sentiment in wiki/orgs/<slug>/entity.md if it shifted

Flag boss if anything urgent surfaced (churn signal, escalation, etc.)

Voice rules

Be specific about features (name them) and people (name them)

Quote the customer where their phrasing matters

Don't paper over negatives — "they're frustrated with X" beats "they had some questions about X"

Anti-patterns

Generic summary ("they liked the product overall") — useless

Stripping out customer-quote details to "save space"

Skipping the commitments section because "I'll remember"

Forgetting to update the org's sentiment when it noticeably shifted

name	summarise-customer-call
description	After a customer call (transcribed or hand-noted), file a structured summary to wiki/research/ and trigger extract-commitments. Use when founder finishes a call and says "@customer-success file this call" or similar.