zynkr-skill-builder

In the author's own words, from each skill's SKILL.md — showing the first 30 of 96 files.

• planning-1on1-annual-digest

  Turn ONE teammate's shared 1:1 Doc (weekly WB entries), their LOB plan Doc and the tracker rows they own into a zh-TW 「年度計畫＿<name>」 Google Doc in the planning hub folder — six fixed sections (過去一年成果總覽 · 策略透鏡 C1–C4 · 復盤 放大／收割／停止或改造 · 年度計劃 3–5 主軸 · OKR · 接下來) with every claim tagged to its WB date, plus a 12-line slide summary block for that person's session one-pager. Trigger on /planning-1on1-ann…

  skills/0-strategy/planning-1on1-annual-digest/SKILL.md on GitHub (opens in a new tab)

• planning-evidence-pack

  The "looking back in numbers" scoreboard for a Zynkr planning cycle (H1 / H2 / YE). Seeds KPIs from the session workbook's Pre-work by LOB tab + the OKR tracker's KRs, routes each to ONE readable source (Main Tracker 完成 counts · planning-tracker-sync's `tracker-snapshots` tab · OKR status · Calendar event counts by title pattern · Gmail Fireflies recap counts · numbers the user pastes; zynkr-gm's…

  skills/0-strategy/planning-evidence-pack/SKILL.md on GitHub (opens in a new tab)

• planning-lob-gap-audit

  Audit ONE line of business (an L1 LOB such as 3.0 Operations) after a planning cycle: inventory its Drive folder, read its plan Doc + Refresh addendum and its rows in the planning Main Tracker, and cross-check five gap classes — P0/P1 items with no doctrine/SOP or owner-named plan, role docs / SOPs that contradict the plan (stale tools, stale owners), docs the plan cites that do not exist, supers…

  skills/0-strategy/planning-lob-gap-audit/SKILL.md on GitHub (opens in a new tab)

• planning-prework-pack

  Build the BEFORE-THE-ROOM pack for a Zynkr planning session (H1 / H2 / YE): copy the session-workbook template Sheet and re-fill its five tabs for the new cycle (Read Me · Agenda 8 blocks · Pre-work by LOB 8 rows · Laundry List + Eisenhower seeds · Eisenhower Matrix) from the Main Tracker, the OKR tracker, the per-LOB plan Docs and the 1:1 Docs; write per-owner one-pager text blocks into a 「Pre-w…

  skills/0-strategy/planning-prework-pack/SKILL.md on GitHub (opens in a new tab)

• planning-session-synth

  Same-day digestion of a Zynkr planning offsite (H1 / H2 / year-end): turn the session transcript + whiteboard photos into the Main Tracker's working tabs — verbatim 「② 白板原文」 (pen colour + 判讀信心 高/中/低), the MECE re-cut 「③ 去重與歸類決策」 + 「④ MECE 檢查」 with every merge/split/move ruling written down, the 「<cycle> 回顧總結」 retro table with 5 重點結論, the README tab, a normalized item list handed to planning-track…

  skills/0-strategy/planning-session-synth/SKILL.md on GitHub (opens in a new tab)

• planning-suite-reconciler

  Propagate a FINALIZED planning Main Tracker into Zynkr's satellite planning suite after an H1 / H2 / YE planning session: for the integrated plan Doc and every per-LOB plan Doc it composes and inserts a dated top-of-body Refresh addendum (thesis sharpened · what changed vs the previous plan · open decisions · the P0 list with owners · management fixes from the retro), and for the OKR & KPI Tracke…

  skills/0-strategy/planning-suite-reconciler/SKILL.md on GitHub (opens in a new tab)

• planning-tracker-builder

  Build or extend Zynkr's planning Main Tracker (the cycle's system of record) from a NORMALIZED item list — the planning-session-synth handoff or a pasted table. Fresh cycle: copy the template tracker (never edit it) → 「<year> <cycle> Planning Main Tracker」 → cycle-named tabs → fill the SOR tab with L1 header rows + N.NN numbering, 重要×緊急 → Priority formula, the 專案項目小記 pivot, 狀態 colours. Existing t…

  skills/0-strategy/planning-tracker-builder/SKILL.md on GitHub (opens in a new tab)

• planning-tracker-sync

  Team-side weekly heartbeat on the COMPANY Planning Main Tracker (SOR tab of the H1 / H2 / YE cycle) — zynkr-gm's record-side companion. Reads the `<cycle> 專案項目` tab, derives per-item state with zynkr-gm's rules VERBATIM (ENDS_SOON · OVERDUE · UNDATED · STALLED · PROPOSE_DONE · DIRECTION_UNLABELLED — its scripts when installed, else the copied rules) and prints the zh-TW Team Weekly agenda block i…

  skills/0-strategy/planning-tracker-sync/SKILL.md on GitHub (opens in a new tab)

• zynkr-gm

  The GM operating-rhythm skill for a small company run from Google Docs/Sheets. Reads the source-of-record chain in precedence order (strategy alignment section → H2 project tracker (status SOR) → the ops team's weekly log → OKR & KPI tracker → per-function progress sheets), derives per-item state (ends-soon · overdue · undated · propose-done · direction-unlabelled), and produces a fixed-shape WEE…

  skills/0-strategy/zynkr-gm/SKILL.md on GitHub (opens in a new tab)

• content-fission

  Article fission — extract outline + summary from any popular article, then run 3 rounds of reflective dialogue to surface the writer's own refined take, ending with a new actionable outline ready for style + writing handoff.

  skills/1-brand-marketing/content-fission/SKILL.md on GitHub (opens in a new tab)

• content-governance

  Put a newsletter in its proper place — reconcile it between Google Docs and the Notion Content DB in EITHER direction (Doc-first OR Notion-first), and file the Doc into the newsletter Drive folder. The goal is that the content ends up correctly placed and cross-linked regardless of which was created first. Use whenever the user shares a Google Doc and/or a Notion Content-DB page and wants them sy…

  skills/1-brand-marketing/content-governance/SKILL.md on GitHub (opens in a new tab)

• content-newsletter-draft

  Drafts Peter's weekly Chinese newsletter from the user's article outline or topic idea, shaping it into a structured handoff for the /zynkr-content-writer pipeline. Use this skill whenever Peter says "幫我寫電子報", "來寫電子報", "寫newsletter", "電子報大綱", or shares a topic/outline and wants it shaped into a newsletter. Trigger even if Peter only gives a rough idea — the skill will structure it into a full out…

  skills/1-brand-marketing/content-newsletter-draft/SKILL.md on GitHub (opens in a new tab)

• content-translator

  Translate English (or any source language) into natural, conversational Traditional Chinese using Taiwanese expressions and tone. Removes the 'translation smell' that comes from word-for-word renderings. Also supports a reverse zh-TW → English mode for producing English 'flagship' versions of SEO articles (used by seo-article-pipeline for AEO reach in English-dominant AI engines).

  skills/1-brand-marketing/content-translator/SKILL.md on GitHub (opens in a new tab)

• seo-angle-finder

  Third leg of the SEO pipeline: working from an SEO expert's perspective plus competitor URLs, surface the content angles and differentiation opportunities for 'where we can do better.' Maps to the v2 flow diagram step 'think about strengthening from the SEO angle + reference competitor URLs to think about strengthening.' Triggers when the user hands over a Questions handoff packet, provides compe…

  skills/1-brand-marketing/seo-angle-finder/SKILL.md on GitHub (opens in a new tab)

• seo-article-finalizer

  The final leg of the SEO pipeline: add internal/backlinks, a meta description, and structured data (schema) to an already-proofed article, then assemble it into a publish-ready Google Doc (article body + a 「SEO 交付物」block carrying slug/seo_title/meta_description/keywords/category + links/schema) for seo-publish-article. Corresponds to node (11) of the v2 flow diagram — 'list which paragraphs can t…

  skills/1-brand-marketing/seo-article-finalizer/SKILL.md on GitHub (opens in a new tab)

• seo-article-pipeline

  The orchestrator for Zynkr SEO content production: it chains the stages of the v2 flowchart into one pipeline running from brand material all the way to a published article on the live website. The first half (persona → seed questions → angles → keyword map → intent classification → demand validation → Brief → outline/FAQ) calls each SEO skill; the second half (drafting → titling → proofreading)…

  skills/1-brand-marketing/seo-article-pipeline/SKILL.md on GitHub (opens in a new tab)

• seo-brief-writer

  Seventh stage of the SEO pipeline: for one selected topic, find the value proposition and winning angle, and produce a complete SEO writing Brief. Corresponds to the v2 flowchart step 「選擇主題：設計 Brief」. Triggers when the user hands over a Topics handoff packet, provides reference articles/forums/expert opinions, or says 「寫 Brief」. Only writes the Brief — does not design the outline and does not wri…

  skills/1-brand-marketing/seo-brief-writer/SKILL.md on GitHub (opens in a new tab)

• seo-demand-validator

  Sixth stage of the SEO pipeline: validate the real demand and competitive difficulty of keywords, compare the common patterns across the current SERP, prune unnecessary terms, and consolidate a list of target keywords and topics. Corresponds to node (6) in the v2 flow diagram. Triggers when the user hands over a Classified handoff packet or says 「驗證需求」 (validate demand) or 「整理主題清單」 (organize the…

  skills/1-brand-marketing/seo-demand-validator/SKILL.md on GitHub (opens in a new tab)

• seo-keyword-classifier

  Fifth leg of the SEO pipeline: classify the keyword map "by search intent" (not by product category), and offer several grouping versions to choose from. Maps to the v2 flowchart step "classify by different classification methods, provide different versions". Triggers when the user hands over a KeywordMap handoff packet, or says '關鍵字分類' or '按意圖分群'. Only classifies — does not validate demand or di…

  skills/1-brand-marketing/seo-keyword-classifier/SKILL.md on GitHub (opens in a new tab)

• seo-keyword-mapper

  Fourth leg of the SEO pipeline: use keyword tools (Ubersuggest / AnswerThePublic) to expand angles and seed terms into a complete keyword map. Maps to the v2 flow diagram's 'filter keywords to build the keyword map + compile the complete keyword map'. Triggers when the user hands over an Angles handoff packet, pastes a keyword-tool export, or says '做關鍵字地圖'. Builds the map only — it does not class…

  skills/1-brand-marketing/seo-keyword-mapper/SKILL.md on GitHub (opens in a new tab)

• seo-outline-designer

  Stage 8 of the SEO pipeline: turn the SEO Brief into an article outline and FAQ section, outputting a handoff summary compatible with content-draft. Corresponds to the v2 flow diagram's 'Structure article: outline design' and 'Build FAQ'. Triggers when the user hands over a Brief handoff packet and says '設計大綱' or '做 FAQ'. Only handles the outline and FAQ; the actual writing is handed off to conte…

  skills/1-brand-marketing/seo-outline-designer/SKILL.md on GitHub (opens in a new tab)

• seo-persona-builder

  First leg of the SEO content pipeline: reads brand material (from the SEO knowledge-base folder or a brand-material pack) and builds personas / consumer profiles of the target readers and prospects, to serve as the basis for downstream keyword and topic work. Triggers when the user says '幫我建立 SEO 人物誌', '先做受眾輪廓', '開始 SEO 流程', or hands over a brand-material pack. Does personas only — no keyword wor…

  skills/1-brand-marketing/seo-persona-builder/SKILL.md on GitHub (opens in a new tab)

• seo-program-planner

  The Stage-0 program-scale SEO strategy planner for any Zynkr product or website — it sits UPSTREAM of seo-article-pipeline and turns 'plan the whole product/site's SEO' into a repeatable, callable orchestration. It reuses the existing single-topic seo-* strategy skills at program scale (seo-persona-builder → seo-question-miner → seo-angle-finder → seo-keyword-mapper → seo-keyword-classifier → seo…

  skills/1-brand-marketing/seo-program-planner/SKILL.md on GitHub (opens in a new tab)

• seo-publish-article

  Publishes a FINISHED SEO blog article to the live website (e.g. zynkr.ai/blog) by writing it straight into the CMS's Supabase `articles` table — the fast path, because the CMS admin page (e.g. cms.zynkr.ai/content) is an auth-gated dashboard, not a write API. Reads the article from a Google Doc (body + the embedded 「SEO 交付物」block for slug/seo_title/meta_description/keywords/category), converts it…

  skills/1-brand-marketing/seo-publish-article/SKILL.md on GitHub (opens in a new tab)

• seo-question-miner

  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 bra…

  skills/1-brand-marketing/seo-question-miner/SKILL.md on GitHub (opens in a new tab)

• slide-arch-diagram

  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…

  skills/1-brand-marketing/slide-arch-diagram/SKILL.md on GitHub (opens in a new tab)

• slide-page-splitter

  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 ▸ Story…

  skills/1-brand-marketing/slide-page-splitter/SKILL.md on GitHub (opens in a new tab)

• slide-pptx

  The 'rendering engine' that comes after the three-stage slide relay (the fourth stage, maintained by Anthropic): it takes the SLIDE_PACKET ▸ Visuals handed off by slide-visual-selector and renders it page by page into a real .pptx file, and can also read, parse, and edit existing decks in reverse. This is Anthropic's official slide-pptx skill; Zynkr does not redistribute its code — this card is o…

  skills/1-brand-marketing/slide-pptx/SKILL.md on GitHub (opens in a new tab)

• slide-storyline-designer

  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…

  skills/1-brand-marketing/slide-storyline-designer/SKILL.md on GitHub (opens in a new tab)

• slide-visual-selector

  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…

  skills/1-brand-marketing/slide-visual-selector/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• ECCby affaan-m The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Cod… 280k stars · 30 skills
• reaby morluto Reverse engineer anything with agents, from app behavior down to native binaries. 270k stars · 1 skill
• andrej-karpathy-skillsby multica-ai A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls. 220k stars · 1 skill
• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 164k stars · 6 skills
• ui-ux-pro-max-skillby nextlevelbuilder An AI skill that provides design intelligence for building professional UI/UX across multiple platforms. 136k stars · 7 skills
• graphifyby Graphify-Labs Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Curs… 127k stars · 1 skill