一键在 Manus 中运行任何 Skill

开始使用

writing-fragments

星标4

分支1

更新时间2026年6月28日 13:42

Writing, explore — mine raw fragments, no structure yet.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

Fernado03

Fernado03/zoo-flow

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Writing Fragments

Setup

This is pure explore: widen what could be written without committing to structure. Committing is exploit, a separate skill's job.
Run a grilling session that produces fragments. Interview relentlessly.
Capture fragments from initial prompt onward.
If output path missing, ask once.
First write: one H1 working title; no metadata/TOC/date.
Use Read to re-read file before every Write.
Use Write to append only unless user requests specific edit.

Fragment forms

Sharp sentence.
Claim + one-line reason.
Vignette/scenario/analogy/code snippet.
Half-thought.
Quote/dialogue.
Observation cluster.
Complaint/confession/punchline.
Leading word — compact metaphor/coinage the whole piece can hang on, like tracer bullets or fog of war.

Leading word is the highest-value fragment. It shapes structure, transitions, and title later. When conversation circles a recurring idea, push to coin a word for it.

File format

# Working title

Fragment one.

---

Fragment two.

Rules:

Separate fragments with ---.
No body headings/tags.
Order = capture order.
Append silently; mention briefly.
Preserve user edits.
Support cut last, rewrite, merge immediately.
DO NOT impose outline/structure.

同仓库更多 Skills

同仓库

ask-zoo

Fernado03/zoo-flow

Ask which skill or flow fits your situation. A router over the skills in this repo.

2026-07-114

implement

Fernado03/zoo-flow

Implement a piece of work based on a spec or set of tickets.

2026-07-114

setup-matt-pocock-skills

Fernado03/zoo-flow

Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

2026-07-114

to-spec

Fernado03/zoo-flow

Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

2026-07-114

to-tickets

Fernado03/zoo-flow

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

2026-07-114

wayfinder

Fernado03/zoo-flow

Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

2026-07-114

name	writing-fragments
description	Writing, explore — mine raw fragments, no structure yet.

Writing Fragments

Setup

This is pure explore: widen what could be written without committing to structure. Committing is exploit, a separate skill's job.
Run a grilling session that produces fragments. Interview relentlessly.
Capture fragments from initial prompt onward.
If output path missing, ask once.
First write: one H1 working title; no metadata/TOC/date.
Use Read to re-read file before every Write.
Use Write to append only unless user requests specific edit.

Fragment forms

Sharp sentence.
Claim + one-line reason.
Vignette/scenario/analogy/code snippet.
Half-thought.
Quote/dialogue.
Observation cluster.
Complaint/confession/punchline.
Leading word — compact metaphor/coinage the whole piece can hang on, like tracer bullets or fog of war.

Leading word is the highest-value fragment. It shapes structure, transitions, and title later. When conversation circles a recurring idea, push to coin a word for it.

File format

# Working title

Fragment one.

---

Fragment two.

Rules:

Separate fragments with ---.
No body headings/tags.
Order = capture order.
Append silently; mention briefly.
Preserve user edits.
Support cut last, rewrite, merge immediately.
DO NOT impose outline/structure.