From writing-skills
Scans Obsidian vaults for publishable notes, recommends blog topics from candidates, and converts selected notes to blog post drafts via Python script.
npx claudepluginhub niracler/skill --plugin writing-skillsThis skill uses the workspace's default tool permissions.
从 Obsidian Note 仓库中筛选适合发布的笔记，评估适配性，批量选题，双通道处理（快速转换 / 深度研究），并行 Agent 派发。
Drafts authentic blog posts and articles in a direct, conversational writer's voice from research, iterates drafts, and publishes to Notion for AI, productivity, sales, marketing, tech topics.
Turns rough notes, bullet points, voice transcripts, or tweet dumps into a polished, publication-ready blog post. Optionally enriches with Tavily research to add supporting data and credibility to claims. Use when asked to write a blog post from notes, turn rough ideas into an article, expand bullet points into a full post, clean up a voice transcript into a blog, or repurpose a tweet thread as an article. Trigger when a user says "write a blog post from this", "turn these notes into a post", "expand this into an article", "make this publishable", "I have rough notes write a blog", or "clean up this transcript".
Writes or edits structured blog posts (800-1200 words) with sections, referencing published posts and guidelines to avoid repetition and match voice.
Share bugs, ideas, or general feedback.
从 Obsidian Note 仓库中筛选适合发布的笔记，评估适配性，批量选题，双通道处理（快速转换 / 深度研究），并行 Agent 派发。
| Tool | Type | Required | Install |
|---|---|---|---|
| Python 3 | cli | Yes | Pre-installed on macOS |
| PyYAML | cli | Yes | pip install pyyaml |
| writing-proofreading | skill | No | Included in npx skills add niracler/skill |
Do NOT proactively verify these tools on skill load. If a command fails due to a missing tool, directly guide the user through installation and configuration step by step.
<skill-dir>/scripts/note-to-blog.py convert "<path>"All deterministic operations are handled by the Python script:
<skill-dir>/scripts/note-to-blog.py (collect / convert / state subcommands)
Path configuration is in user-config.md. All bash examples below use <PLACEHOLDER> — replace with values from user-config.md.
Step 1 Step 2 Step 3 Step 4 Step 5
Collect ──▶ Level Select ──▶ By Level ──▶ Execute ──▶ Summary
(script) (user) ├─ L1 浏览 (Agent Teams) (report)
├─ L2 推荐
└─ L3 深探
│
Interact ──▶ track assign ──▶ confirm
Run the collect script with paths from user-config.md:
python3 <skill-dir>/scripts/note-to-blog.py collect \
--note-repo "<NOTE_REPO>" \
--blog-content "<BLOG_CONTENT>" \
--project-paths <PROJECT_PATHS> \
--history-file "<HISTORY_FILE>"
The script outputs a single JSON object to stdout containing:
candidates: all eligible notes with title, summary, char_count, outgoing_linksclusters: wikilink hub nodes (3+ inbound links) with related notespublished_posts: existing blog posts with title, tags, collectionsession_keywords: recent Claude Code session activity signalsstats: total_scanned, filtered_out, candidates_countRead the JSON output and proceed to Step 2.
Display data volume and offer Level choice:
collect 完成：
候选笔记: {candidates_count} 篇 (总扫描 {total_scanned}, 过滤 {filtered_out})
主题簇: {clusters_count} 个 (3+ 引用 hub)
可选深度:
Level 1 浏览 直接展示候选列表，手动选择 0 额外 token
Level 2 推荐 LLM 评估 + 主题簇分析 ~2k token ← 推荐
Level 3 深探 Level 2 + 读取 hub 笔记全文 ~5k+ token
选择 Level (1-3)?
| Level | 名称 | 评估方式 | 后续流程 |
|---|---|---|---|
| 1 | 浏览 | 无 LLM，候选按字数降序 | 用户直选 → 全部 fast track |
| 2 | 推荐 | LLM 评估摘要 + 主题簇 → 5-8 推荐 | fast/deep track 分配 |
| 3 | 深探 | Level 2 + 读取 hub 笔记全文 | fast/deep track，cluster 推荐更准确 |
| 候选数 | clusters | 推荐 |
|---|---|---|
| ≤ 10 | any | Level 1 |
| > 10 | 0 | Level 2 |
| > 10 | 1+ | Level 2 |
用户明确说「想发现主题」「有什么可以整合的」时 → 推荐 Level 3。
Skip LLM evaluation. Display candidates sorted by char_count descending:
# 标题 字数 链接数
1 关于后LLM时代的代码Review 3200 5
2 SSH私钥加密 1200 2
3 Feed内容阅读姿势 1800 3
...
User selects items by number. All selections go to fast track only (Level 1 does not offer deep track).
After selection, skip to Confirm & Execute below.
Make a single LLM evaluation using the prompt template from scoring-criteria.md.
Input: Construct the evaluation prompt with collect JSON data (candidates, clusters, published_posts, session_keywords).
Output: The LLM SHALL return a JSON array of 5-8 recommendations. See scoring-criteria.md for the full specification.
If the LLM response is not valid JSON, retry once with explicit format instructions.
After evaluation, proceed to Interact below.
Same as Level 2, but before calling the LLM, Read the full text of each cluster hub note and append it to the evaluation prompt.
For each cluster in the collect JSON where hub_path is not null:
## Hub 笔记全文 section (see scoring-criteria.md for the Level 3 input format)This gives the LLM actual content context for cluster recommendations instead of just metadata.
After evaluation, proceed to Interact below.
Display the recommendation list as a mixed table:
# 类型 标题 适配分 目标 工作量 活跃 重复风险
1 单篇 后LLM时代代码Review 92 blog 小 ★★★ 无
2 主题簇 优雅的哲学 (9篇关联) 88 blog 大 ★ 无
3 单篇 SSH私钥加密 85 til 小 ─ 无
...
| Action | Example | Effect |
|---|---|---|
| Select + assign track | "1 和 3 快速转换，2 走深度" | Queue items with track assignment |
| Override collection | "1 放 til" | Change target collection |
| Batch skip | "4~6 跳过，reason: private" | Mark as skipped via state skip |
| See more | "还有别的吗" | Request additional recommendations |
| Check status | "状态" | Run state status |
On skip: run immediately:
python3 <skill-dir>/scripts/note-to-blog.py state skip "<path>" --reason "<reason>" \
--note-repo "<NOTE_REPO>"
| Track | When to use | What happens |
|---|---|---|
| Fast (快速) | Independent, mostly complete notes | Script converts → Agent reviews → draft |
| Deep (深度) | Topic clusters or rough notes needing research | Agent reads all related notes → research report |
Default: effort: "小" → fast; type: "cluster" or effort: "大" → deep. User decides.
Display a confirmation summary (all Levels):
确认选择：
Fast track:
1. 后LLM时代代码Review → blog/
3. SSH私钥加密 → til/
Deep track:
2. 优雅的哲学 (9篇关联) → blog/
开始处理？
Wait for user confirmation, then dispatch.
Dispatch N parallel Agents using the Task tool, one per selected item.
其他 Agent 环境：以下 Fast/Deep track 任务相互独立，可按顺序依次执行。
总编 (Main Agent)
├── Task Agent 1: 文章 A (fast track)
├── Task Agent 2: 文章 B (fast track)
└── Task Agent 3: 主题簇 C (deep track)
Use the Task tool to launch all Agents in a single message. Each Agent should be a general-purpose subagent with a detailed prompt containing all the information it needs.
See agent-instructions.md for the complete Fast Track and Deep Track agent prompt templates.
Individual Agents do NOT update .note-to-blog.json directly. After all Agents complete, the main agent runs state updates sequentially:
python3 <skill-dir>/scripts/note-to-blog.py state draft "<note_path>" \
--target "<collection>/<slug>.md" \
--note-repo "<NOTE_REPO>"
Deep track items are NOT marked as drafted (they need further user decision).
After all Agents complete, present a unified summary:
Fast Track 完成：
✓ 后LLM时代代码Review → repos/bokushi/src/content/blog/llm-code-review.md
- 转换正常，无问题
✓ SSH私钥加密 → repos/bokushi/src/content/til/ssh-key-encryption.md
- 发现 1 个 TODO 标记需要手动处理
Deep Track 完成：
📋 优雅的哲学 (9篇关联)
- 研究报告已生成
- 下一步？ a) 按大纲写作 b) 修改大纲 c) 暂不处理
状态更新：
drafted: N 篇
草稿均为 hidden: true，需要手动 review 后改为 false 发布。
建议使用 /writing-proofreading 进行审校。
发布后运行:
python3 <skill-dir>/scripts/note-to-blog.py state publish "<note_path>" --note-repo "<NOTE_REPO>"