Business & Operations

Turn a qualified CRM deal plus whatever the client actually sent — a requirement sheet, discovery notes, a meeting transcript, a prior proposal — into a priced client proposal published as a 交付文件 at platform.zynkr.ai/d/<token>, and keep it alive through the revision rounds. It does four things in one pass: ranks the client's asks by an openly-stated criterion and presents them as 第一順位／額外項目 (never colour codes, never our internal IDs); splits them into a recurring lane and a one-off build lane...

Turn ONE person's interest signal into a tracked CRM lead AND a ready-to-send reply. The signal can be a copied DM / chat thread (Threads, IG, LINE, FB Messenger, WhatsApp, email), a single row from an event feedback or registration form, a website enquiry, or the text off a business card — anything where one named person showed interest and left an email address. Optionally hand it their profile link too. It does two things in one pass: (1) collects who they are — parsing the signal and enri...

The conductor of the Zynkr sales family — it decides which sales skill a given input needs, chains them when a job takes more than one, and reads the CRM across deals to say which ones need attention now. It owns the deal lifecycle; the five skills under it each own one step. Three modes: ROUTE (one input → the right child skill), SEQUENCE (a job that needs two or more, e.g. triage a whole event survey with sales-client-sourcing then run sales-outbound on each Hot Lead row), and REVIEW (deal-...

Turn a finished sales DEMO / discovery call into a converting follow-up — the post-meeting counterpart to sales-outbound. Give it the demo transcript (a Fireflies meeting, a Google Doc URL, or pasted notes) and it does two things in one pass: (1) drafts a pre-sales follow-up reply as a threaded Gmail DRAFT in Peter's inbox (never sends), in the prospect's language and Peter's voice — opening by mirroring the exact pain points they raised, mapping each to the matching Zynkr AI 平台 capability (z...

Turn a consulting engagement session — a discovery call or an on-site shadowing session, either already captured in Fireflies or supplied as a recording — into a clean zh-TW transcript filed straight into the client's numbered [N] Drive project folder and linked on the CRM deal. A thin delegation wrapper: it invokes the installed training-srt-transcriber (local Whisper → timestamped .srt; transcribe or retime mode) and training-srt-optimizer (minimal-edit zh-TW cleanup) for ALL transcription/...

Generate the weekly CLIENT-FACING status email for ONE consulting engagement. Reads the CRM deal's tasks / activities / notes plus the newest [Notes] / [Plan] / [BRD] / [UAT] docs in the client's numbered [N] Drive folder, derives health / progress / blockers / next milestone, renders the 專案狀態看板-style HTML dashboard, and creates a Gmail DRAFT addressed to the deal's client contact — NEVER auto-sends. Trigger on /consult-status-report or when Peter says "客戶週報", "顧問案週報", "寫給客戶的進度報告", "客戶進度信", "...

Turn an engagement's discovery outputs — consult-discovery summaries, consult-session-notes 痛點 ledgers, the client's stated goals — into a structured solution plan: persona, operator journey, pains ranked by 影響範圍 size × 強度 intensity × 頻率 frequency, selected opportunities, MVP scope, and success metrics — filed as a "[Plan]" Google Doc in the client's numbered [N] Drive folder and ending in an explicit handoff block for /consult-brd-writer. Operationalizes MrPM-Stanley's 產品企劃力 product-planning...

Close the shadowing-scheduling admin loop for a consulting deal in one pass: read the CRM deal, resolve the client's existing [N] Drive project folder from the deal notes, check Peter's calendar free/busy, propose 3–5 candidate slots, and on Peter's confirm lay down the whole kit — a calendar hold, a "Shadowing — YYYY-MM-DD" subfolder inside the project folder, a client logistics Gmail DRAFT (never sent), a CRM follow-up task, and a deal-notes backlink. Trigger EAGERLY on /consult-shadowing-s...

Turn a consulting-session transcript or messy notes — a discovery call or a shadowing observation — into the four-section session summary (Summary Update · Progress · Blockers · What's Next) PLUS a 痛點 ledger (one row per pain actually voiced or observed), filed as a [Notes] Google Doc into the engagement's EXISTING numbered [N] Drive folder with a note on the CRM deal; the ledger is the raw material /consult-brd-writer consumes. Trigger on /consult-session-notes or when Peter says "整理這次客戶訪談筆記...

Turn a single sales / consulting meeting into tracked work. Give it a meeting transcript or notes — pasted text, a Google Doc, or a Gemini Notes link — and it produces a structured Weekly Project Update, then lays down the three things the engagement needs: a numbered Google Drive project folder, a kickoff/context Doc inside it, and a CRM deal in Supabase with a meeting + links-note + one task per "What's Next" item. Trigger on /consult-project-specialist or when Peter says "turn this meeting...

Turn this week's inbound "AI 顧問服務" consulting inquiries (the website discovery-call emails from website@zynkr.ai) into tracked work: for each real lead it creates a CRM deal in Supabase, a numbered Google Drive project folder, and a kickoff doc inside that folder. Use this skill whenever Peter runs /consult-intake or says things like "process this week's consult inbounds", "處理本週顧問諮詢", "有沒有新的顧問諮詢", "check for new consulting leads", "turn the discovery-call inquiries into deals", "intake the co...

Run a client info session (說明會) for a consulting engagement end to end on the D-14 → D+3 checklist — schedule and invite, prep, run and record, then produce the client-facing five-section recap — with every artifact filed in the client's numbered [N] Drive folder and noted on the CRM deal. Re-entrant: each run shows the checklist with today's position and advances the due stage. Trigger on /consult-info-session or when Peter says "幫客戶辦說明會", "導入說明會", "說明會回顧", "安排 kickoff 說明會", "run the client ...

The weekly hygiene sweep across the WHOLE consulting portfolio — inventory every numbered [N] engagement folder under the consult Drive parent AND every open consult deal in the CRM, diff the two against six invariants (deal↔folder backlink, kickoff-doc presence, session-note recency, [N] numbering continuity, activity pulse, artifact chain), and emit a zh-TW ready-to-apply changelist in the chat. Strictly READ-ONLY — it proposes fixes named to the owning skill but never applies one: no Doc c...

Visualize a consulting engagement's operations on Lucid as a paired AS-IS / TO-BE process chart set — drawn from the engagement's own documents (session notes, 痛點 ledgers, [Plan] docs, BRD) and recorded back on the CRM deal. ALL drawing, editing, and lint mechanics are delegated to the installed product-flow-design skill; this wrapper adds engagement resolution, the as-is/to-be pairing discipline, chart naming, and CRM linkage. Trigger on /consult-flow-design or when Peter says "畫客戶的 as-is/to...

Two-stage consulting discovery — pain-point intake then company vision exploration — to produce a needs definition and strategic discovery summary before any solution work.

Turn a client bug report — a Gmail thread, a forwarded mail, or pasted text — into tracked work in one pass: a well-formed GitHub issue in the right repo (routed via a local bug-routing-config.md), a CRM follow-up task on the client's deal, and a threaded acknowledgment reply left as a Gmail DRAFT (never sent). Trigger on /consult-bug-ticket or when Peter says "開 bug 單", "把這封信開成 issue", "回報這個 bug", "客戶回報問題", "file this bug", "turn this bug mail into a ticket", "log this defect and reply", or ...

Turn a consulting engagement's raw discovery material — consult-discovery summaries, shadowing transcripts / recording notes, process findings — into a client-grade requirements document as a Google Doc in the client's numbered [N] Drive project folder, backlinked to the CRM deal. Two modes: BRD (default — business-facing, zh-TW) and PRD (an SDD-conformant buildable spec with a per-client spec ID, EARS-lite ACs and Verify lines). Trigger on /consult-brd-writer or when Peter says "幫我寫 BRD", "把...

Pull a consulting client's AI-assistant usage out of platform telemetry (crm_ai_usage, READ-ONLY), compute adoption metrics — WAU, actions per user per week, week-over-week trend, top features, at-risk users — and render a zh-TW "[Adoption] {{COMPANY}} — YYYY-MM" report Doc into the client's [N] Drive folder, backlinked to the CRM deal, plus an optional ask-only Gmail draft. Trigger on /consult-adoption-reporter or when Peter says "客戶用量報告", "採用率追蹤", "這個客戶有沒有在用", "使用狀況分析", "adoption report for...

The conductor of the slide relay (sitting above the three-stage relay): fires when the user says '做一份簡報／做個 deck／幫我把這些做成投影片／做季報簡報／all-hands 簡報／deep dive 簡報／pitch deck'. I do a one-shot intelligent intake — detecting which kind of deck this is (deep-dive / business-review / data-presentation / all-hands / planning / pitch / update / teach / fundraise), taking stock of the material and storyline the user has already given, proposing a page count for the user to confirm, and gathering the must-in...

The third leg of the slide-assistant three-leg relay (picks up after slide-page-splitter, then hands off to the slide-pptx skill for rendering): once it has the SLIDE_PACKET ▸ Pages, it decides page by page \"what is the most effective visual treatment for this page?\" (chart / bullets / diagram / image / comparison / big statement…), and converges each page into a render-ready per-page visual spec SLIDE_PACKET ▸ Visuals, handing it off to the installed slide-pptx skill to render into a .pptx...

Leg 1 of the three-leg slide relay: take the raw slide material / topic + the message you want to land, and shape it into a logically smooth storyline — confirm the presentation's goal and audience, fix the core claim that runs through the whole talk, lay out an ordered narrative arc (beats), and check each transition one by one for leaps or gaps, producing the SLIDE_PACKET ▸ Storyline narrative skeleton that gets handed to slide-page-splitter for paging. Trigger me proactively when the user ...

The second leg of the slide-assistant three-leg relay: take the storyline approved by the previous leg (SLIDE_PACKET ▸ Storyline) and, following paging principles, slice it into a page-by-page slide list — deciding which beat each page maps to, what title it carries, how many bullet points it holds, and how dense its information should be. Trigger me immediately when the user hands over a ▸ Storyline handoff packet, or says 「幫我分頁」, 「把故事線切成投影片」, 「每頁放什麼」, 「規劃投影片頁數」, 「slide 分頁設定」. I only handle ...

Turn an ideated business workflow into a slide-ready FE/BE/DB architecture diagram: three horizontal lanes (前端 Front End · 後端 Back End · 資料庫 Database) with the workflow's IPO units stitched LEFT→RIGHT across them — human inputs drop ↓ from the FE lane into dark octagon process nodes chained → across the BE lane, stored knowledge feeds ↑ from the DB lane, and the output document rises ↑ back to FE at the far right, closed by exactly ONE orange 'law line' verdict bottom-right. Trigger when the ...

Second leg of the SEO pipeline: based on the persona, brainstorm the questions your target readers actually ask before buying, then work backward from those questions to seed keywords. Maps to the v2 flowchart step 'brainstorm common questions + interview-answer common questions and list keywords'. Triggers when the user hands over the persona handoff packet or says '發想常見問題' or '挖種子關鍵字'. Only brainstorms questions and seed keywords; it does not do difficulty analysis and does not write articles.