メニュー
Deterministic feedback processor. Fetches client feedback emails from Gmail, downloads attachments (screenshots), and prepares a structured report for triaging into GitHub issues.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/genericService/claude-skills --skill client-feedbackコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | client-feedback |
| description | Deterministic feedback processor. Fetches client feedback emails from Gmail, downloads attachments (screenshots), and prepares a structured report for triaging into GitHub issues. |
| version | 2.0.0 |
Transform client feedback emails into tracked, investigated, and resolved GitHub issues with professional response emails.
This workflow uses a Script-First approach: a deterministic Python script handles the "labor" of fetching and parsing emails, leaving the agent to handle the "judgment" of triaging and fixing issues.
When the user asks to "process feedback", "check emails from [domain]", or "turn feedback into issues":
Run the processor script:
python3 ~/.agents/skills/client-feedback/scripts/process_feedback.py \
--domain "<client-domain>" \
--days 7 \
--out "./feedback-batch-$(date +%F)"
Read the report:
Load the generated report.json and the full body text files to understand the feedback.
Triage to GitHub: For each distinct piece of feedback in the report, create a GitHub issue or update an existing one.
The process_feedback.py script performs these tasks in seconds:
report.json summarizing threads, participants, and snippets.GitHub issues are the primary work board. One issue per item, not one per email.
## Reported by
[Person name] — [date] "[email subject]" (thread [threadId])
## Issue
[Verbatim quote if short, paraphrase if long]
## Status
[Open / awaiting client / in progress]
Apply labels based on category: feedback (always), bug, content, design, provider-data, question.
Verify the feedback against the actual codebase. Grep globally for subjects of claims to ensure full removal or update.
Draft professional responses organized by email thread.
Key Rule: ALWAYS show the draft body text in chat before sending.
Keep signatures simple and professional. Avoid disclosing AI co-authorship unless the client relationship explicitly welcomes it.
If you need to draft a reply with inline images (e.g. before/after proofs), use the gws multipart upload flow documented in the script comments or process_feedback.py logic.