writing-fragments
Capture raw writing fragments through a focused interview
Writers often know they have material for an article but cannot yet structure it. This skill runs a relentless interview, pulls heterogeneous fragments from both sides of the conversation, and appends them to a single markdown file you control — giving you a growing pile of raw material to mine later.
下载技能 ZIP
在 Claude 中上传
前往 设置 → 功能 → 技能 → 上传技能
开启并开始使用
测试它
正在使用“writing-fragments”。 Start a fragment session. Save to ~/notes/typing.md. I want to write about gradual typing.
预期结果:
- I created ~/notes/typing.md with a working title and captured your first fragment.
- As we go I will append each new fragment after a horizontal rule and never overwrite your edits.
正在使用“writing-fragments”。 Cut the last fragment. Merge the first two into one vignette.
预期结果:
- Removed the most recent fragment and merged the first two into a single fragment above the rule.
- The file now opens with the merged vignette and your other fragments are unchanged.
安全审计
安全All four static findings are false positives. The 'Ruby/shell backtick execution' hits at lines 40 and 63 are markdown code fences wrapping a fragment-format example, not executable code. The 'weak cryptographic algorithm' hit at line 3 is the YAML frontmatter description, which contains no crypto. The 'system reconnaissance' hit at line 12 is the skill asking the user where to save a markdown file — a benign UX prompt. The skill's intent is purely a writing ideation workflow: interview the user, capture fragments, append to a user-designated markdown file. No network access, no shell execution, no credential handling.
低风险问题 (1)
风险因素
📁 文件系统访问 (2)
质量评分
你能构建什么
Pre-outline ideation for a new article
Start a new writing project by collecting raw fragments before deciding on structure or argument.
Research journal from interviews and reading
Capture observations, claims, and quotes from research conversations into a single append-only notebook.
Notebook for in-progress thinking
Use fragments as a scratch pad for half-thoughts, complaints, punchlines, and vignettes that may later feed into a longer piece.
试试这些提示
Start a fragment session. Save everything to ~/notes/new-article.md. I want to write about why teams underuse type systems in everyday code.
Resume the fragment session at ~/notes/new-article.md. Re-read the file and keep appending as we talk.
Grill me specifically on the failure modes of gradual typing. I have a hunch that the worst costs show up at module boundaries.
Cut the last fragment. Rewrite the third one to be sharper. Merge the first two into a single vignette.
最佳实践
- Choose a dedicated file path at the start of the session and keep using the same file for one project.
- Let the interviewer drive: answer honestly, include half-thoughts, and let fragments be heterogeneous.
- Edit the file freely between turns; the skill re-reads before every write, so your manual edits are preserved.
避免
- Do not ask the skill to outline or restructure the fragments — that is explicitly out of scope.
- Do not start a new session against the same file with the expectation of a clean slate, since fragments are append-only by default.
- Do not interrupt every fragment with a confirmation prompt; the skill is designed to append silently.