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 agentmods add skills/cymchad/book-skill-generator/pivotnpx skills add CymChad/book-skill-generator --skill pivotgit clone --depth 1 https://github.com/CymChad/book-skill-generatorWrote 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/cymchad/book-skill-generator/pivot)<a href="https://agentmods.dev/skills/cymchad/book-skill-generator/pivot"><img src="https://agentmods.dev/badge/skills/cymchad/book-skill-generator/pivot.svg" alt="Measured on agentmods" 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.00038 | $0.01573 |
| Opus 5 | $0.00019 | $0.00787 |
| Sonnet 5 | $0.00008 | $0.00315 |
| Haiku 4.5 | $0.00004 | $0.00157 |
Grade A, and why
pivot 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 6d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
转型 (Pivot)
当数据证明假设错误时,果断调整方向。知道错了马上改,再大的代价都是最小的代价。
核心理念
快速转型,降低损失。 精益创业鼓励创业者在面对市场反馈时,既要灵活适应,也要有坚持的勇气。转型不是失败,而是基于学习的战略调整。
适用场景
- 数据证明产品方向不对
- 用户增长停滞
- 核心假设不成立
- 需要调整商业模式
- 面临转型还是坚持的决策
执行步骤
步骤 1: 识别转型信号
什么时候需要转型:
-
数据信号
- 用户增长停滞
- 留存率持续下降
- 转化率远低于预期
- 无法推动增长引擎
-
市场信号
- 用户不关心你的产品
- 竞争对手表现更好
- 市场需求发生变化
-
团队信号
- 团队士气低落
- 无法找到产品市场匹配
- 创新核算指标持续恶化
关键问题:
- 如果继续当前方向,能否实现愿景?
- 是否还有优化空间?
- 还是根本假设有问题?
步骤 2: 选择转型类型
常见的转型类型:
-
客户细分转型 (Customer Segment Pivot)
- 改变目标用户群体
- 产品不变,用户改变
- 案例:YouTube 最初是视频交友网站,后转型为视频分享平台
-
价值主张转型 (Value Proposition Pivot)
- 改变产品提供的价值
- 用户不变,产品改变
- 案例:Groupon 最初是团购平台,后转型为优惠券服务
-
渠道转型 (Channel Pivot)
- 改变产品分发渠道
- 产品不变,渠道改变
- 案例:从线下销售转为线上销售
-
商业模式转型 (Business Model Pivot)
- 改变盈利模式
- 案例:从免费增值转为订阅制
-
平台转型 (Platform Pivot)
- 从应用转为平台,或反之
- 案例:从单一产品转为生态系统
-
技术转型 (Technology Pivot)
- 用新技术实现相同价值
- 案例:从传统技术栈转为云原生
步骤 3: 设计转型方案
制定转型计划:
-
明确新方向
- 新的核心假设是什么?
- 新的目标用户是谁?
- 新的价值主张是什么?
-
评估资源需求
- 需要多少时间?
- 需要多少资金?
- 需要哪些人员?
-
制定转型路线图
- 第一阶段:验证新假设
- 第二阶段:开发新 MVP
- 第三阶段:测量和学习
-
设定转型里程碑
- 什么算转型成功?
- 什么算转型失败?
- 何时评估转型效果?
步骤 4: 执行转型
快速行动:
-
沟通转型决策
- 向团队解释原因
- 获得团队支持
- 明确新方向
-
保留有价值的部分
- 哪些功能可以保留?
- 哪些资源可以复用?
- 哪些认知可以应用?
-
快速验证新假设
- 开发新 MVP
- 推向市场
- 收集数据
-
监控转型进展
- 跟踪关键指标
- 定期评估效果
- 及时调整
步骤 5: 评估转型效果
判断转型是否成功:
- 新假设是否成立?
- 用户增长是否恢复?
- 关键指标是否改善?
- 团队士气是否提升?
决策:
- 成功:继续新方向
- 失败:再次转型或放弃
输出格式
转型决策文档:
## 转型信号
### 数据信号
- [指标 1]: [当前值] vs [预期值]
- [指标 2]: [当前值] vs [预期值]
### 市场信号
- [信号描述]
### 团队信号
- [信号描述]
## 转型决策
- 是否转型: [是/否]
- 转型原因:
- 转型类型: [客户细分/价值主张/渠道/商业模式/平台/技术]
## 新方向
### 新核心假设
- 价值假设:
- 增长假设:
### 新目标用户
- 用户画像:
- 用户需求:
### 新价值主张
- 核心价值:
- 差异化优势:
## 转型计划
### 资源需求
- 时间:
- 资金:
- 人员:
### 转型路线图
- 阶段 1: [时间] - [目标]
- 阶段 2: [时间] - [目标]
- 阶段 3: [时间] - [目标]
### 成功标准
- [指标 1]:
- [指标 2]:
- [指标 3]:
## 保留内容
- 可复用功能:
- 可复用资源:
- 可应用认知:
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.
- 6d ago First seen · 225 lines · 38 tokens per session scan A 2e975d839f67
pivot is a skill published in the GitHub repository CymChad/book-skill-generator (66 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 1,573 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…