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-crm-strategygit 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-crm-strategy)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/biz-crm-strategy"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/biz-crm-strategy/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-crm-strategy"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/biz-crm-strategy.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.00214 | $0.05437 |
| Opus 5 | $0.00107 | $0.02719 |
| Sonnet 5 | $0.00043 | $0.01087 |
| Haiku 4.5 | $0.00021 | $0.00544 |
Grade A, and why
"biz-crm-strategy" 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 10d 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.
This is a copy
92% identical to biz-crm-strategy — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
顧客關係管理戰略（CRM Strategy）
定位
為什麼 EMBA 需要 CRM 戰略 skill
多數學員（或其公司）已有某種 CRM 工具（Salesforce、HubSpot、自建系統），但常見問題是：
- 有工具沒戰略（系統閒置、資料未用）
- 有活動沒體系（每月行銷檔期但不整合）
- 有 VIP 制度但回報不明
- 投資 CDP 但無法回答「究竟解決什麼戰略問題」
本 skill 把 CRM 拉回戰略層：不只用哪個工具、不只做哪個 Journey，而是整個客戶經營體系的設計與治理。
與相近 Asgard skill 的邊界
biz-cac-ltv— 工具層：CAC 與 LTV 的計算與決策閾值biz-customer-journey— 工具層：單一客戶旅程繪製biz-stp— 早期定位，本 skill 接在 STP 之後的「經營設計」biz-pricing-strategy— 定價，本 skill 可整合但不重複mkt-content-calendar— 內容排程戰術- 本 skill — CRM 戰略整合，將上述工具整合為可治理的客戶經營體系
何時使用
觸發條件
- 會員／VIP 體系設計或改造
- CDP、CRM 系統選型與導入決策
- 客戶分層策略（大眾市場 + VIP 雙軌）
- B2B 大客戶經營體系（KAM）建置
- 跨通路（線上 + 線下）整合經營
- 客戶流失、NPS 下滑的戰略回應
- 師大、政大、中山 EMBA CRM 課程作業
不適用
- 單純獲客成本計算 → Asgard
biz-cac-ltv - 單一旅程繪製 → Asgard
biz-customer-journey - 廣告投放優化 → Asgard
algo-ad-* - 顧客訪談方法 → Asgard
ux-*系列
IRON LAW — CRM 戰略三條鐵律
IRON LAW 1：CRM 不是工具，是經營體系
買 Salesforce 不會解決客戶經營。
完整 CRM 戰略 = 資料架構 + 分群邏輯 + 旅程設計 + 組織治理。
四者缺一，系統都會淪為昂貴的通訊錄。
IRON LAW 2：VIP 不等於高消費，等於「策略重要性」
依單次消費金額排 VIP 是最粗糙的分層。
好的 VIP 定義 = 高 LTV + 高策略貢獻（推薦、品牌、口碑）。
錯把「金額」當「價值」，會養出最不賺錢的「VIP」。
IRON LAW 3：自動化之前先做「手工化」
還沒人工經營過的客群，貿然上 MA 自動化等於放大錯誤。
先用人工試跑 journey 三個月，量測反應，再自動化。
顛倒順序是九成 CRM 導入失敗的根源。
Rationalization Table — 當 Claude 想「本案例外」時，先自問
| 可能想 | 但 Iron Law 仍適用，因為 |
|---|---|
| 「公司剛買 Salesforce，CRM 戰略就算到位」 | 買工具 ≠ 有戰略；必須檢視資料架構、分群邏輯、旅程設計、組織治理四要件 |
| 「VIP 就用年消費 > X 萬定義」 | 金額定義會養出「高消費低忠誠」VIP；建議改用 LTV + 策略貢獻（推薦、品牌、口碑） |
| 「直接導 MA 上線自動化 Journey」 | 未經人工試跑的 Journey 自動化 = 放大錯誤；必須先手工試跑 3 個月再自動化 |
六大戰略模組
┌─────────────────────────────────────────┐
│ 模組 6：組織與治理 │
│ 誰擁有客戶？CRM 跨部門責任分工 │
├─────────────────────────────────────────┤
│ 模組 5：技術堆疊（CDP/MA/CRM/DMP） │
│ 資料層、決策層、執行層 │
├─────────────────────────────────────────┤
│ 模組 4：Journey 編排 │
│ 跨通路、跨階段、跨時間的客戶互動 │
├─────────────────────────────────────────┤
│ 模組 3：會員與忠誠體系 │
│ VIP 定義、等級、權益、經濟模型 │
├─────────────────────────────────────────┤
│ 模組 2：客戶分層與分群 │
│ RFM、CLV、行為、生命週期 │
├─────────────────────────────────────────┤
│ 模組 1：戰略定位 │
│ 誰是核心客戶？賺哪群人的錢？ │
└─────────────────────────────────────────┘
What ships with it
6 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.
- 10d ago First seen · 418 lines · 214 tokens per session scan A ed6b8f9760db
"biz-crm-strategy" is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (26 stars, last pushed 1mo ago), licensed MIT. It adds 214 tokens to every session and 5,437 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to biz-crm-strategy, differing in 9 lines, and is treated as a copy.
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).
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.
rfi-management
Complete RFI (Request for Information) management system. Create, track, route, and analyze RFIs with automatic notifications and response deadline tracking.
data-evolution-analysis
Analyze data evolution patterns in construction organizations. Assess digital maturity and data strategy for construction companies.