梳理自媒体文章大纲与写作语料的管理流程
npx skills add https://github.com/cafe3310/public-agent-skills --skill kol-writer
> ⚠️ 内置子技能 (Sub-skills) 加载路径
> 本技能包含三个依赖子技能,存放在本地 sub-skills/ 目录:
> - deep-research ──→ 位于 sub-skills/deep-research/
> - markdown-new ──→ 位于 sub-skills/markdown-new/
> - agent-browser ──→ 位于 sub-skills/agent-browser/
>
> 必须且只能从相对路径 sub-skills/ 下读取其 SKILL.md,严禁访问全局技能根目录以防冲突。
本技能用于协助创作者,将零散想法、原始素材与检索信息整理为结构化大纲,并归档个人写作资产。
graph TD
AI_Ask["1. 询问基本信息<br>(主题/平台/风格/目标)"] --> U_Answer["2. 用户提供信息"]
U_Answer --> AI_Init["3. 初始化工作区<br>(创建目录并保存原始输入)"]
AI_Init --> AI_Note["4. 对话式观点速记<br>(仅记录事实,不做推理)"]
AI_Note --> AI_Eval["5. 结构化大纲梳理<br>(输出初版大纲并标注调查项)"]
AI_Eval --> AI_Research["6. 补充检索与回填<br>(针对大纲缺失信息执行检索)"]
AI_Research --> Loop_Iter{"7. 对话修改与调优<br>(反馈微调)"}
Loop_Iter -->|未完善| Loop_Iter
Loop_Iter -->|用户确认| AI_Write["8. 终稿归档<br>(写入 03-大纲终稿.md)"]
01-用户原始输入.md。详见:01_initialize_project.md02-用户想法记录.md 中,作为大纲整理和文风模仿的素材。详见:02_quick_notes.mdrules/platforms.md 中对应的平台规范,结合已有想法提炼论点,输出初版大纲。大纲中需使用引用块(>)标注待调查或补充的事项。详见:03_understanding_prompt.md03-大纲草稿.md,直到用户确认满意。详见:05_iteration_optimization.md03-大纲终稿.md,输出简短的总结和下一步行动建议。详见:06_archive_final.md当执行环境支持 ask_question 或 ask_user 时,Agent 在关键决策点必须优先调用对应工具,避免使用纯文本交互。
应用场景:
markdown-new 或 agent-browser)。用于写作参考的博文、长图文及外部优秀案例,其收集、转写、清洗与归档需遵循统一的流程规范。详见:07_corpus_collection.md
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take cafe3310/kol-writer from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.