Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add charlieviettq/awesome-agent-skill --skill biz-sme-managementgit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/biz-sme-management)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/biz-sme-management"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/biz-sme-management/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/biz-sme-management"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/biz-sme-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00204 | $0.04523 |
| Opus 5 | $0.00102 | $0.02261 |
| Sonnet 5 | $0.00041 | $0.00905 |
| Haiku 4.5 | $0.00020 | $0.00452 |
Grade A, and why
"biz-sme-management" scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
中小企業與家族企業管理（SME & Family Business Management）
定位
為什麼台灣 EMBA 特別需要這個 skill
- 台灣 98% 企業為中小企業、超過 70% 上市櫃為家族控制
- 多數 EMBA 學員本身是 SME 老闆、家族企業二代或配偶
- 主流商管理論以跨國大企業為樣本（Porter、Kotler 皆如是），直接套用會失真
- 台灣特有：一代創辦人仍健在、二代歸國、專業經理人介入 — 三方動態
與相近 Asgard skill 的邊界
biz-porters-five-forces、biz-swot等策略工具 — 通用、需搭配本 skill 調整grad-strat-agency— 代理理論，可支援家族治理分析grad-strat-stakeholder— 利害關係人，家族企業中「家族」即關鍵利害人algo-hr-*— 通用人資工具，SME 版需降維- 本 skill — 補齊「資源限制 + 家族動態」兩個主流理論不處理的現實條件
何時使用
觸發條件
- 公司員工數 10–200 人、營收 1–50 億、創辦人仍在位
- 家族內（父子、兄弟、姑嫂）股權／經營權爭議
- 二代留學歸國準備接班
- 專業經理人與家族成員衝突
- 外部投資人（PE/VC）介入家族企業引發治理改革
- IPO 前夕的家族企業專業化
- 成大、政大、逢甲 EMBA 相關個案與期末報告
不適用
- 跨國集團治理 → Asgard
grad-governance+ 本 repobiz-corporate-governance - 純新創（尚未進入家族化）→ Asgard
ux-lean-startup - 薪酬技術設計 → Asgard
algo-hr-compensation - 併購估值 → 本 repo
fin-m-and-a（待開發）
IRON LAW — SME 與家族企業三條鐵律
IRON LAW 1：SME 不是「小型大企業」
中小企業面臨的限制（資金、人才、資訊、品牌）是結構性的，
不能直接套用大企業的最佳實務。
錯誤處方：給 30 人公司導 SAP、設 COO／CFO／CMO 三層 C-level。
正確處方：優先序排程、一人多角設計、外包替代內建。
IRON LAW 2：家族企業的「系統」有三個圓
家族系統（情感）× 所有權系統（財產）× 事業系統（績效）
三圓相交處是家族企業獨有張力。忽略其中任一圓的分析都是殘缺的。
典型陷阱：純用績效邏輯評估「兒子接班」。
IRON LAW 3：傳承不是「選人」是「設計制度」
把接班視為挑兒子或找專業經理人 = 錯把人當制度。
完整傳承 = 所有權傳承 + 治理結構傳承 + 經營權傳承 + 文化傳承
四者可分離，且節奏不同（通常所有權最快、文化最慢）。
Rationalization Table — 當 Claude 想「本案例外」時，先自問
| 可能想 | 但 Iron Law 仍適用，因為 |
|---|---|
| 「30 人公司也要導入完整 COSO + SAP 才專業」 | SME 限制是結構性；必須給精簡版框架並標註「未精簡 = 組織癱瘓」 |
| 「接班分析只談『長子 vs. 專業 CEO』」 | 必須同時分析家族、所有權、事業三圓；忽略任一圓的建議殘缺 |
| 「結論寫『王董長子是最佳接班人』就完成傳承規劃」 | 傳承含所有權 / 治理 / 經營 / 文化四層；選人只是經營層一步，其餘三層必須設計制度 |
框架一：資源受限下的策略選擇
SME 常見資源缺口
| 資源維度 | 大企業 | SME | 因應策略 |
|---|---|---|---|
| 資金 | 多元融資 | 銀行 + 自有 | 預現金流先於追成長 |
| 人才 | 分工專業 | 一人多角 | 關鍵職位以外外包 |
| 品牌 | 強 | 弱 | 策略聚焦（niche）、B2B 優於 B2C |
| 資訊 | 情報系統 | 老闆的行業網絡 | 善用產業公會、同儕社群 |
| 通路 | 自建或主導 | 依附大通路 | 平台議價 + 建替代通路 |
| 法遵 | 法務團隊 | 老闆兼任 | 外部顧問 + 分段遵循 |
資源受限的策略原則
- 先活著，再談成長：現金流 > 損益表
- 聚焦取勝：利基市場、單點做深
- 槓桿外部：通路、品牌、技術借用他人
- 快速試錯：決策成本低是 SME 唯一優勢
- 拒絕模仿大企業：組織結構、KPI、會議頻率都要減配
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 292 lines · 204 tokens per session scan A fa1848c829ca
"biz-sme-management" is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (25 stars, last pushed 1mo ago), licensed MIT. It adds 204 tokens to every session and 4,523 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
rfi-management
Complete RFI (Request for Information) management system. Create, track, route, and analyze RFIs with automatic notifications and response deadline tracking.
punch-list-manager
Digital punch list management for construction project closeout. Track deficiencies, assign corrections, photo documentation, and completion verification.
safety-inspection
Digital safety inspection system for construction sites. Checklists, hazard tracking, incident reporting, and compliance documentation.
data-evolution-analysis
Analyze data evolution patterns in construction organizations. Assess digital maturity and data strategy for construction companies.