My Skills
Portable SKILL.md skills · Claude Code · Cursor · Codex可攜 SKILL.md 技能 · Claude Code · Cursor · Codex

Agent skills that write Traditional Chinese like a real person寫出像真人正體中文的 agent 技能

Straight from my ~/.skills — the portable SKILL.md skills, scripts, and tooling I actually use day to day on Claude Code, Cursor, and Codex. A personal toolbox with open scope; today it leans toward Traditional Chinese writing: de-AI editing, Taiwan localization, and business docs.直接來自我的 ~/.skills，是我日常在 Claude Code、Cursor、Codex 上真的在用的 SKILL.md 技能、腳本與工具。範圍開放的個人工具箱，目前偏向繁體中文寫作：去 AI 味、台灣在地化、商務公文。

Star on GitHub在 GitHub 上按星 Browse skills瀏覽技能
npx skills add https://github.com/leoluyi/skills -g -a '*' -y
11Skills個技能
4Categories分類
3Agents supported支援平台
MITOpen source開源授權

Why these exist為什麼有這些

Most AI-writing tooling assumes English. For a Taiwan audience it leaves gaps these skills close.市面上的 AI 寫作工具幾乎都預設英文。對台灣讀者來說，它們留下的缺口正是這些技能要補的。

English-only defaults只顧英文

De-AI editors and style tools are tuned for English and miss the tells in Chinese entirely.去 AI 味、風格工具都對著英文調校，完全抓不到中文裡的破綻。

Generic zh, not Taiwan zh通用中文，不是台灣中文

"Chinese" support usually means mainland usage. These write the way people actually write in Taiwan.所謂的「中文」支援通常是大陸用法。這些技能照台灣人實際的寫法寫。

Leaked mainland wording & Simplified混進來的陸用語與簡體

陸用語, 互聯網黑話, and stray 簡體字 get caught — without over-correcting real terms.陸用語、互聯網黑話、殘留簡體字都抓得出來，又不誤傷真正的術語。

AI tells & corporate jargonAI 味與職場黑話

The uniform rhythm, hedging, and filler that give machine text away — stripped, in both languages.那種一致的節奏、模稜兩可和填充語，中英文都一起清掉。

Skill catalog技能目錄

Most fire automatically when a task matches their trigger; ones badged invoke-only you call by name. Search or filter by category.多數會在任務命中 trigger 時自動載入；標了 invoke-only 的要指名叫用。可用搜尋或分類篩選。

Traditional Chinese Writing繁中寫作

Clean AI tells, mainland-China wording, and jargon, or draft a blog from scratch, so Traditional Chinese reads like a person wrote it.去掉 AI 味、陸用語和術語黑話，或從零寫出一篇部落格，讓繁體中文讀起來像真人寫的。

De-AI Writing (English + zh-TW)去除 AI 味（中英雙語） avoid-ai-writing-zh

EN繁中中英

Catches the tells that make English and Traditional Chinese read as machine-written, then rewrites them into human prose揪出讓中英文讀起來像機器寫的破綻，改回像人講話的樣子

What it does細節

When to use何時使用

Reach for it as a final de-AI pass before shipping a README, ADR, blog post, or any English/Chinese draft that reads machine-generated.在 README、ADR、部落格或任何中英文草稿出稿前，當作去 AI 味的最後一關。

When not to何時不要

Skip it when you need to compose a piece or give it a human voice from scratch, which is blog-writing-zh's job; this skill removes tells but does not create voice.若要從零寫文章或替它注入個人聲音，改用 blog-writing-zh；本 skill 只除味，不造聲音。

Highlights重點

  • Three modes: rewrite, detect-only audit, or edit a file in place with minimal fixes三種模式：改寫、只標記、直接改檔
  • Traditional Chinese layer flags 空話, 確保 filler, 破折號濫用, and over-translated proper nouns中文層抓空話、確保贅字、破折號濫用、生造譯名
  • Detect-only structure audit names what a soulless draft is missing, not just bad phrases偵測模式點出草稿缺什麼，不只挑錯句
  • Signals not proof: tuned against false positives on non-native and technical writing只當訊號不當判決，避免誤傷非母語與技術寫作
#de-ai#traditional-chinese#ai-isms#zh-tw#editing#readme
Read SKILL.md看 SKILL.md →

Cross-Strait Chinese Localizer台灣正體中文在地化 avoid-china-writing

繁中

Strips mainland-China wording, jargon, and leaked Simplified from Traditional Chinese and rewrites it into natural Taiwan usage without over-correcting real terms把混進來的陸用語、簡體字和互聯網黑話，改回台灣讀者習慣的正體中文，又不誤傷真正的術語

What it does細節

When to use何時使用

Reach for it when a Traditional Chinese draft carries mainland wording, corp-speak, or leaked Simplified characters and you need it to read naturally for a Taiwan audience.當一份繁體中文稿子夾雜陸用語、互聯網黑話或簡體字，要改成台灣讀者自然的正體中文時使用。

When not to何時不要

Not for stripping AI tells or polishing tone (use avoid-ai-writing-zh), formal business docs (formal-doc-structure), RFPs (rfp-writing), or plain-language rewrites (plain-speak).不要用於去 AI 味或潤飾語氣（用 avoid-ai-writing-zh）、簽呈報告（用 formal-doc-structure）、RFP（用 rfp-writing）或白話翻譯（用 plain-speak）。

Highlights重點

  • Catches 陸用語 across four axes: vocabulary, corp-speak jargon, leaked Simplified, transliterations四軸偵測：詞彙、職場黑話、簡體殘留、音譯專名
  • Three modes: detect-only audit, full rewrite, or in-place file edit三種模式：只標不改、整段改寫、直接改檔案
  • Ranks findings P0-P2 so you fix the loudest mainland-source giveaways firstP0–P2 分級，先改最明顯的陸源破綻
  • Protects brand names, quotes, code, and genuine terms-of-art from over-correction品牌名、引文、程式碼與術語自動保留不誤改
#traditional-chinese#taiwan-localization#cross-strait#zh-tw#simplified-chinese#de-jargon
Read SKILL.md看 SKILL.md →

Plain Speak: Jargon into Plain Language把技術術語翻成白話 plain-speak

繁中EN

Turn a technical term, snippet, or dense paragraph into one line your PM, exec, or customer can actually repeat back把術語、程式碼、工程長文翻成非技術主管聽得懂、還能複述的一句話

What it does細節

When to use何時使用

Reach for it when you need to explain a technical term, code snippet, error, or dense engineering text to a non-technical reader, or to check whether a plain-language draft actually lands.當你要把技術術語、程式碼、錯誤訊息或工程長文講給非技術讀者聽，或想檢查白話草稿夠不夠白時使用。

When not to何時不要

Not for de-AI voice cleanup (avoid-ai-writing-zh), structuring a whole formal doc like a 簽呈 or 報告 (formal-doc-structure), or an RFP (rfp-writing).不要用於潤飾語氣、去 AI 味（用 avoid-ai-writing-zh），編排整份簽呈或報告（用 formal-doc-structure），或 RFP（用 rfp-writing）。

Highlights重點

  • Pins the exact reader first: a CFO gets 財務影響, a salesperson gets 客戶好處先鎖定讀者：CFO 談財務、業務談客戶好處，同一術語講法不同
  • Delivers one repeat-test line: what it does and what it's for, no jargon產出一句能複述的話：做什麼、為什麼，不靠術語解術語
  • Reviews an existing draft against a 9-point checklist, marking each pass/fail可審既有白話草稿，九項檢查逐條標 pass/fail
  • Glosses terms inline (idempotent 冪等) and cuts empty modifiers like 大幅優化就地標註術語（冪等），砍掉「大幅優化」這類空話
#plain-language#traditional-chinese#jargon-translation#audience-translation#zh-tw#explain-to-pm
Read SKILL.md看 SKILL.md →

Traditional Chinese Blog Writer繁中部落格寫作 blog-writing-zh

繁中

Turn notes, a talk, or a bare topic into a Taiwan-Chinese blog post that reads like a real person wrote it把筆記、演講或一個題目，寫成有立場、有親身經歷、讀起來像真人的繁中部落格文

What it does細節

When to use何時使用

When you need to write or rewrite a Taiwan-Chinese blog post or newsletter, or turn Obsidian notes, talks, or foreign articles into a long-form zh-TW piece.要寫或改寫繁中部落格文、電子報，或把 Obsidian 筆記、演講、外文文章變成中文長文時。

When not to何時不要

Not for formal memos (formal-doc-structure), RFPs (rfp-writing), explaining a single term in plain language (plain-speak), or pure de-AI cleanup with no restructuring (avoid-ai-writing-zh).正式簽呈用 formal-doc-structure、RFP 用 rfp-writing、單一術語白話解釋用 plain-speak、純去 AI 味不動結構用 avoid-ai-writing-zh。

Highlights重點

  • Two modes: compose from a topic, or rewrite Obsidian notes, talks, and foreign sources兩種模式：從題目開寫，或改寫筆記、演講、外文來源
  • Voice recipes modeled on 7 studied Taiwan and English blogs, tuned by reader and goal風味配方取樣自七個台灣與英文部落格，依讀者與目的調整
  • Length tiers, dual-draft merge for high-stakes pieces, and auto series-split suggestions長度分檔、雙稿熔接、自動評估要不要拆成系列
  • Ships the article plus 3-5 title/subtitle options, then runs a de-AI finishing pass成品一定附 3-5 組標題副標，並跑一輪去 AI 味收尾
#traditional-chinese#blog-writing#zh-tw#de-ai#newsletter#voice
Read SKILL.md看 SKILL.md →

Taiwan Business Documents台灣商務公文

Draft and review 簽呈, meeting records, assessment reports, RFPs, and briefing outlines in Taiwan corporate Traditional Chinese.用台灣職場慣用的正體中文撰寫與審查簽呈、會議紀錄、評估報告、RFP 與說明提綱。

Briefing Outline說明提綱 briefing-outline

繁中

Distill one long report or many docs into a high-altitude 說明提綱 a manager can grasp, then drill into把厚重的來源文件收斂成一份高空俯瞰的說明提綱，讓主管一眼掌握全貌、需要時再往下鑽

What it does細節

When to use何時使用

Reach for it when you need to condense one or more source documents into a navigable briefing a manager or committee can grasp at a glance and drill into.當你要把一份或多份來源文件收斂成主管或委員會能一眼掌握、又能往下鑽的說明提綱時使用。

When not to何時不要

Not for authoring a single formal doc from scratch (use formal-doc-structure), an RFP (rfp-writing), lowering one term to a lay reader (plain-speak), or pure de-AI cleanup (avoid-ai-writing-zh).不要用於從零撰寫單一正式文件（用 formal-doc-structure）、RFP（用 rfp-writing）、白話化單一術語（用 plain-speak）或純去 AI 味（用 avoid-ai-writing-zh）。

Highlights重點

  • Handles one long report or many docs: each part gets its essence, then points down for detail跨多份文件或一份長報告，每段給足精華再往下指路
  • Cuts detail that belongs in the source (SOP, 逐條標準, 配分) so the outline stays stable when sources churn把逐條標準、SOP、逐項配分等細節下沉回來源，提綱穩定不亂
  • MECE spine: every source maps to exactly one section, no overlap, full coverageMECE 骨架：每份來源只落在一個章節，不重不漏
  • Re-sync mode re-runs only the sections whose source docs changed來源改版時，只重跑受影響的章節
#briefing-outline#traditional-chinese#executive-summary#document-distillation#taiwan-business#mece
Read SKILL.md看 SKILL.md →

Formal Internal Doc Structure正式公文結構 formal-doc-structure

繁中

Turns a rough ask into a ready-to-circulate 簽呈, 會議紀錄, or 評估報告 with the structure its reader actually needs把粗略需求變成可直接送簽的簽呈、會議紀錄或評估報告，結構跟著讀者的決策需求走

What it does細節

When to use何時使用

Reach for it to write or fix an internal business document in Taiwan corporate Traditional Chinese: approval memo, meeting record, assessment report, project plan, or vendor communication.要撰寫或修整公司內部的簽呈、會議紀錄、評估報告、專案規劃或廠商溝通文件時用它。

When not to何時不要

Not for RFPs or bidding specs (use rfp-writing), pure language cleanup with no restructuring (use avoid-ai-writing-zh), or blog posts and marketing copy.不要用在 RFP 或招標規格（改用 rfp-writing）、只做語言去 AI 味不動結構（改用 avoid-ai-writing-zh），或部落格與行銷文案。

Highlights重點

  • Maps five reader needs (approve, assess, record, execute, coordinate) to a matching document template依五種讀者需求（核准、評估、紀錄、執行、協調）套對應的文件範本
  • Outputs a paste-ready draft with real sections, not a critique or an outline直接產出可貼進文件的完整段落，不是給建議或列大綱
  • Forces concrete owners, timelines, deliverables, and acceptance criteria into every activity每項工作都要寫清楚負責單位、時程、交付物與驗收方式
  • Runs a 10-point revision checklist plus an optional de-AI finishing pass before final output收尾跑十點修訂檢查，並可選配去 AI 味的最後一道潤稿
#traditional-chinese#taiwan#meeting-minutes#approval-memo#assessment-report#business-docs
Read SKILL.md看 SKILL.md →

Technical RFP Writing & Review技術 RFP 撰寫與審查 rfp-writing

繁中

Draft and review technical RFPs from the issuer's side, cutting redundant sections, appendix bloat, and AI filler站在招標方立場撰寫與審查技術 RFP，砍掉重複章節、附錄灌水與 AI 填充語

What it does細節

When to use何時使用

Reach for it when you draft or review a technical RFP (需求規格書 / 招標規格) as the issuing organization, not the bidder.當你要以招標方身分撰寫或審查技術 RFP（需求規格書／招標規格）時使用。

When not to何時不要

Skip it for vendor bid responses (投標提案), migration/test plans, ADRs, meeting minutes, or pure de-AI cleanup (use avoid-ai-writing-zh).投標提案、遷移／測試計畫、ADR、會議紀錄或純去 AI 味潤稿不要用（改用 avoid-ai-writing-zh）。

Highlights重點

  • Structural audit that fixes misplaced sections, merges thin ones, and kills appendix bloat結構審查：修正錯置章節、合併過薄段落、刪除附錄灌水
  • Pain-point filter deletes requirements already met by general infrastructure痛點過濾：一般基礎設施已涵蓋的需求就刪掉，只留領域專屬項目
  • Language rules force every bullet into a full what/why sentence with section context語言規則：每條需求都寫成說明 what/why 的完整句，段落先給脈絡
  • Strips AI filler (確保, 從而, 賦能) while keeping legitimate RFP notation禁用清單清掉『確保、從而、賦能』等 AI 填充，但保留正規 RFP 寫法
#rfp#procurement#requirement-spec#traditional-chinese#zh-tw#de-ai
Read SKILL.md看 SKILL.md →

Docs & Design文件與設計

Language-agnostic professional tools: save-worthy explanatory graphics in SVG or HTML, and engineering-grade Diátaxis knowledge docs.跨語言的專業工具：讓人想收藏的說明圖表（SVG 或 HTML），以及工程等級的 Diátaxis 知識文件。

Infographic Design資訊圖表設計 infographic-design

繁中EN

Design-system-grade explanatory graphics — timelines, comparisons, process diagrams — as clean, self-contained SVG or a single HTML file. Language-agnostic; built to be saved and reshared設計系統級的說明圖表（時間軸、比較、流程圖），輸出成乾淨、可獨立開啟的 SVG 或單一 HTML 檔案。跨語言通用，為收藏轉發而生

What it does細節

When to use何時使用

Reach for it when you need an infographic, one-pager, timeline, comparison, or how-it-works diagram, or a visual recap of something just taught.需要資訊圖表、懶人包、one-pager、時間軸、比較圖或流程圖解，或把剛教完的內容總結成一張圖時使用。

When not to何時不要

Skip it for standalone data charts, dashboards, BI tooling, slide decks, or plain-language term explanations; route those to a dataviz, pptx, or plain-speak flow instead.純資料圖表、儀表板、BI 工具、投影片，或只想用白話解釋一個名詞時不要用它，改用 dataviz、pptx 或 plain-speak。

Highlights重點

  • Plans the graphic and critiques that plan before building, so it isn't a templated default先擬計畫再自我批判，才動手畫，避開樣板感的預設圖
  • Draws palette, layout, and visual metaphor from the subject's own world for a distinctive look配色、版面、視覺隱喻都取材自主題本身，做出獨特風格
  • Three-level text hierarchy plus a deterministic gate that catches clipped text and weak contrast三層文字階層加自動檢查，抓出爆版、文字被切、對比不足
  • Handles ByteByteGo-style technical explainers and animated HTML learning recaps支援 ByteByteGo 式技術圖解與動畫版學習總結 HTML
#infographic#svg#diagram#visual-communication#bytebytego#traditional-chinese
Read SKILL.md看 SKILL.md →

Knowledge Doc Writing (Diátaxis)Diátaxis 知識文件寫作 knowledge-doc-writing

繁中

Engineering-grade knowledge docs on the Diátaxis model — tutorial, how-to, reference, explanation — writing only what the material supports and flagging the gaps honestly. A discipline that travels across domains以 Diátaxis 模型寫工程等級的知識文件（tutorial、how-to、reference、explanation），素材撐得起才寫，缺口據實標出。這套紀律跨領域通用

What it does細節

When to use何時使用

When you want to distill a technical topic you studied or researched into one lasting reference doc split into tutorial, how-to, reference, and explanation.當你想把自學或研究過的技術主題，整理成可長期參考、tutorial／how-to／reference／explanation 四型分離的知識文件時。

When not to何時不要

Not for internal memos or reports (use formal-doc-structure), RFPs (use rfp-writing), blog posts (use blog-writing-zh), or language-only de-AI cleanup (use avoid-ai-writing-zh).不要用於簽呈／評估報告（用 formal-doc-structure）、RFP（用 rfp-writing）、部落格（用 blog-writing-zh）、或只做語言層去 AI 味（用 avoid-ai-writing-zh）。

Highlights重點

  • Compass router assigns each material chunk to exactly one of four Diátaxis blockscompass 兩問把每段素材路由到唯一一型區塊
  • Writes only blocks the material supports and lists the rest as gaps, no fabricated filler素材撐得起才寫，撐不起的型明列為缺口，不捏造空殼
  • Four input modes: chat logs, raw sources, from-scratch research, existing-doc rewrites支援四種輸入：對話紀錄、原始資料、從零研究、既有文件改寫
  • Primary-source checks with as-of dating, plus a de-AI pass before shipping強制查一手來源並標 as-of 時效，出稿前做去 AI 味
#diataxis#traditional-chinese#technical-docs#knowledge-base#self-learning#zh-tw
Read SKILL.md看 SKILL.md →

Knowledge Management知識管理

Learn a concept by being taught and quizzed, then file your own note into an Obsidian vault on PARA structure.先教後考學懂一個概念，再把親手寫的筆記歸檔進 PARA 結構的 Obsidian 筆記庫。

Learn Loop結構化學習迴圈 learn-loop

繁中Invoke-only手動叫用

Get taught and quizzed on a concept, then write the note yourself while it verifies sources and files it into your Obsidian vault先教後考，筆記你親手寫，它負責查證來源、挑洞、歸檔進 Obsidian

What it does細節

When to use何時使用

Reach for it when you want to genuinely learn a new technical concept and crystallize it into a permanent Obsidian note, not just skim an explanation.當你想真正學懂一個新技術概念，並把它結晶成 Obsidian vault 裡的長期筆記時使用。

When not to何時不要

Skip it for reorganizing an already-distilled doc into Diátaxis blocks (use knowledge-doc-writing) or for a quick one-off explanation with no note to keep.不要用於把已 distill 完的文件重整成 Diátaxis 區塊（改用 knowledge-doc-writing），或只想要一次性的口頭解釋。

Highlights重點

  • Teaches from verified primary sources, then quizzes you with retrieval questions從查證過的一手來源開講，再用回想題考你
  • Never ghostwrites your note: you write it from memory while it pokes holes as a skeptic不代寫筆記：你憑記憶寫，它只當懷疑論者挑洞
  • Sorts each note into evergreen vs reference, wiring up wikilinks, MOCs, and frontmatter自動分流 evergreen／reference，接好 wikilink 與 MOC
  • Temp-vault fallback on machines without your vault, packaged to merge back later沒有 vault 的機器改走 temp-vault，打包好之後併回
#obsidian#learning-loop#retrieval-practice#knowledge-management#note-taking#source-verification
Read SKILL.md看 SKILL.md →

Obsidian Vault NotesObsidian 筆記庫 obsidian-vault

中英

Search, create, and link notes in an Obsidian vault that stays on PARA / Johnny-Decimal structure and wikilinks在 Obsidian 筆記庫搜尋、新增與串連筆記，維持 PARA 結構

What it does細節

When to use何時使用

Reach for it when you want to find, create, or organize notes in your Obsidian vault.要在 Obsidian 筆記庫裡搜尋、新增或整理筆記時用它。

When not to何時不要

Not for turning notes into a blog post (use blog-writing-zh) or a structured technical doc (use knowledge-doc-writing).不是把筆記寫成部落格（用 blog-writing-zh）或技術文件（用 knowledge-doc-writing）的工具。

Highlights重點

  • Search the whole vault by filename or content, skipping .obsidian internals依檔名或內容搜尋整個筆記庫，略過 .obsidian
  • Create notes in the right PARA / Johnny-Decimal folder with YAML frontmatter在對的資料夾新增筆記，帶好 frontmatter
  • Link notes with [[wikilinks]] and a ## Related section; dangling links are fine用 [[wikilinks]] 串接筆記，空連結也 OK
  • Find every backlink to a note with a single grep一行 grep 找出任何筆記的反向連結
#obsidian#wikilinks#para#johnny-decimal#note-taking#knowledge-management
Read SKILL.md看 SKILL.md →