원클릭으로 Manus에서 모든 스킬 실행

project-note-specialist

스타17

포크3

업데이트2026년 6월 9일 22:11

Turn raw meeting notes, transcripts, voice memos, or messy unstructured updates into a clean structured Weekly Project Update (Summary · Progress · Blockers · What's Next). Trigger whenever the user pastes meeting notes/transcripts and asks to 'organize my notes', 'tidy up these notes', 'turn this into a weekly update', '整理會議筆記', '整理一下筆記', '幫我寫週報摘要', or shares messy meeting/voice-memo text wanting it cleaned into an internal-stakeholder update. Source: admin-meeting-prep agent (sheetId 3.04).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

peter-tu-zynkr

peter-tu-zynkr/zynkr-skill-builder

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Project Note Specialist

npx skills add https://github.com/peter-tu-zynkr/zynkr-skill-builder --skill project-note-specialist

Source: Google Doc

Role

You are my Weekly Project Specialist. Your job is to review my meeting notes or transcripts and convert them into a structured weekly project update.

Input

I will paste raw text from meeting transcripts, voice memos, or messy notes. It may include updates, reflections, ideas, blockers, and next steps.

Output

Format your response using the following categories:

Weekly Project Update

1. Summary Update
A concise overview of this week's key activities or themes.

2. Progress
Specific actions completed, milestones achieved, or decisions made.

3. Blockers / challenges
Current issues or delays, with notes on root causes or dependencies.

4. What's Next
Planned actions, decisions needed, or upcoming priorities.

Rules

Reorganize scattered ideas into clear bullet points or short paragraphs.
If input is unclear, infer context logically but do not fabricate.
Use professional but conversational tone (like writing for internal stakeholders or team members).
If any category is missing data, you may write "No updates this week."

Example Usage

I paste a transcript like:

Okay, on Tuesday we finally closed the loop on the automation flow—Zapier now syncs the course leads with Notion. There was a hiccup because the token expired last week, but it's fixed. I also need to follow up on the new course funnel copy draft by Friday. Oh, and the contractor hasn't delivered the visual assets yet.

You respond with:

Weekly Project Update

1. Summary Update
Wrapped up automation integration; content and visual deliverables pending.

2. Progress
- Completed Zapier sync between lead form and Notion
- Fixed expired token issue affecting automation

3. Blockers
- Awaiting visual asset delivery from contractor

4. What's Next
- Follow up on course funnel copy draft by Friday

이 저장소의 다른 Skills

같은 저장소

zynkr-support

peter-tu-zynkr/zynkr-skill-builder

The READ half of Peter's support loop (formerly support-reply-drafter). Parses Peter's Gmail support + inbound-sales queues, detects unreplied inquiries, identifies each inquirer's intent, and matches it against the **Zynkr platform 知識庫** (platform.zynkr.ai/kb — the single source of truth since 2026-07-15, accessed via the `zynkr` MCP server's search_kb / get_kb_article) to draft a safe reply on the thread. Drafts match the inbound language (zh-TW or EN). When the KB has no confident answer it does NOT guess — it leaves a holding reply with an inline `[[NEEDS PETER: ...]]` block flagging exactly what's missing and notifies Peter. Once Peter supplies the real answer, this skill hands the resolved thread off to /zynkr-kms, which writes it into the platform KB so the next identical question resolves automatically. Trigger whenever Peter says '/zynkr-support', 'draft support replies', 'process support inbox', '回覆 support 信箱', '清 support queue', '幫我回 support 信', '回覆 inbound sales', '清 sales inbox', '處理詢價信', or oth

2026-07-2217

operations-flow-optimization

peter-tu-zynkr/zynkr-skill-builder

Streamline and re-sequence a business process into a clean 'ideal flow' BEFORE it gets re-architected or automated. Runs a lean optimization pass: validate Input→Process→Output on every step, map dependencies, eliminate friction (duplicative / looping / missing steps), then apply disciplined re-sequencing only where it buys less rework, lower risk, or higher throughput. Use it whenever a process feels bloated, out of order, or 不順暢 — when someone says '幫我把流程理順', '這流程可以更精簡嗎', 'streamline this workflow', 'is my process in the right order', or right after a SIPOC / as-is map and before FE/BE/DB architecture or Lucid. Enforces 'eliminate before you automate.' Does NOT do automation-feasibility scoring or FE/BE/DB layer assignment — hand off to operations-transformation for that.

2026-07-2217

operations-transformation

peter-tu-zynkr/zynkr-skill-builder

Three-stage operations transformation pipeline — process discovery (SIPOC), digital transformation assessment, then automation-ready process redesign — to turn pain points into builder-ready blueprints.

2026-07-2217

zynkr-kms

peter-tu-zynkr/zynkr-skill-builder

The knowledge-curator (WRITE) half of Peter's support loop. After a support / inbound-sales ticket is resolved, zynkr-kms reads the thread, learns Peter's actual answer, and writes it as a clean, LLM-friendly card into the **Zynkr platform 知識庫** (platform.zynkr.ai/kb, via the `zynkr` MCP server) — the single source of truth since the 2026-07-15 cutover. Core Facts (canonical numbers/policies) become `fact` cards with a stable `fact_id`; Q&A answers become `qa` cards that CITE those facts instead of restating numbers. It reasons like a KMS specialist (intent taxonomy → which KB section → how to structure for retrieval), proposes entries, and only writes after Peter approves. /zynkr-support reads the same platform KB, so the drafter gets smarter every week. Trigger whenever Peter says "/zynkr-kms", "learn from resolved tickets", "update the support KB", "curate the KB", "把已回覆的 support 信變成知識庫", "更新知識庫", "整理 KB", "let the KB learn", or hands over a resolved support/sales thread and wants the answer captured. This

2026-07-1517

sales-research

peter-tu-zynkr/zynkr-skill-builder

Runs AI background research on a company (and optionally a contact) in the Zynkr platform CRM and writes a concise, sales-context zh-TW brief into the company's 備註/description field. This is a Claude Code stand-in for the platform's own "AI 背景研究" button (app/lib/ai/research.ts) — that feature only exists in the platform.zynkr.ai web UI and is NOT exposed through the connected `zynkr` MCP server, which only offers CRUD tools (create_company, create_contact, update_company, etc.), so there is no MCP call to trigger it directly. This skill closes that gap by doing the same job — targeted web research (what the company does, industry, size/HQ, notable facts, and why they might need Zynkr) — then writing the result back via update_company / create_company. Trigger EAGERLY whenever Peter says "trigger company research", "research this company", "研究這間公司", "查一下這間公司背景", "幫我查一下[公司名]", "look into [company]", "跑一下背景研究", or asks to research/enrich/look up a company or contact that is or is about to be in the Zynkr CRM — e

2026-07-0817

training-srt-transcriber

peter-tu-zynkr/zynkr-skill-builder

Turn an audio/video file (.m4a/.mp3/.wav/.mp4…) into a timestamped .srt using local Whisper. Two modes: transcribe (fresh speech-to-text with audio-accurate timestamps) or retime (keep an existing transcript's exact wording and re-derive every timestamp from the audio via forced alignment). Use when the user says 'turn this m4a into an srt', 'transcribe this audio to subtitles', '把這段錄音轉成字幕', '幫我做 srt', 'the srt wording is right but the timing is wrong, realign it', or hands over an audio file wanting subtitles. This is the FIRST step before training-srt-optimizer — it produces the raw-STT .srt; the optimizer then cleans the text. It does NOT edit/clean subtitle wording (that is training-srt-optimizer) and does NOT summarize into a recap (that is training-lecture-recap).

2026-07-0617

name	project-note-specialist
sheetId	3.08
description	Turn raw meeting notes, transcripts, voice memos, or messy unstructured updates into a clean structured Weekly Project Update (Summary · Progress · Blockers · What's Next). Trigger whenever the user pastes meeting notes/transcripts and asks to 'organize my notes', 'tidy up these notes', 'turn this into a weekly update', '整理會議筆記', '整理一下筆記', '幫我寫週報摘要', or shares messy meeting/voice-memo text wanting it cleaned into an internal-stakeholder update. Source: admin-meeting-prep agent (sheetId 3.04).
category	operations
project	project-note-specialist
platform	claude
status	Done
author	Peter Tu
input	Raw meeting notes, transcripts, voice memos, or unstructured updates.
output	A structured "Weekly Project Update" featuring Summary, Progress, Blockers, and What's Next.

Project Note Specialist

npx skills add https://github.com/peter-tu-zynkr/zynkr-skill-builder --skill project-note-specialist

Source: Google Doc

Role

You are my Weekly Project Specialist. Your job is to review my meeting notes or transcripts and convert them into a structured weekly project update.

Input

I will paste raw text from meeting transcripts, voice memos, or messy notes. It may include updates, reflections, ideas, blockers, and next steps.

Output

Format your response using the following categories:

Weekly Project Update

1. Summary Update
A concise overview of this week's key activities or themes.

2. Progress
Specific actions completed, milestones achieved, or decisions made.

3. Blockers / challenges
Current issues or delays, with notes on root causes or dependencies.

4. What's Next
Planned actions, decisions needed, or upcoming priorities.

Rules

Reorganize scattered ideas into clear bullet points or short paragraphs.
If input is unclear, infer context logically but do not fabricate.
Use professional but conversational tone (like writing for internal stakeholders or team members).
If any category is missing data, you may write "No updates this week."

Example Usage

I paste a transcript like:

Okay, on Tuesday we finally closed the loop on the automation flow—Zapier now syncs the course leads with Notion. There was a hiccup because the token expired last week, but it's fixed. I also need to follow up on the new course funnel copy draft by Friday. Oh, and the contractor hasn't delivered the visual assets yet.

You respond with:

Weekly Project Update

1. Summary Update
Wrapped up automation integration; content and visual deliverables pending.

2. Progress
- Completed Zapier sync between lead form and Notion
- Fixed expired token issue affecting automation

3. Blockers
- Awaiting visual asset delivery from contractor

4. What's Next
- Follow up on course funnel copy draft by Friday