Write
Stop Claude from winging it — 7 workflow skills that route every task through two thinking modes (Philosopher = absorb / Engineer = ship). Works in Claude Code + Codex.
npx -y skills add Lemonaderrrrr/flow-kit --skill writeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Turn ideas into deliverable writing, split into two tracks — 📚 Academic (adds a mandatory evidence-gathering step; every claim gets a traceable source) and ✍️ Regular (emails, posts, docs, narrative). Each track runs in 🧠 Philosopher (default) or ⚙️ Engineer mode. Saves drafts to outputs/drafts/. Use when the user says "help me write/draft X", "write a paper", "write an email", or invokes the skill.
SKILL.md
2.9 KB, as published. Nobody here has run it
Write Workflow
Turn ideas into deliverable writing.
Start
- Route-confirm (see
CONVENTIONS.md): one line stating this is the write workflow and the suggested mode; wait for the go-ahead. - Confirm mode: default 🧠 Philosopher; the user may switch to ⚙️ Engineer.
- Confirm track: 📚 Academic or ✍️ Regular (decides which branch below).
✍️ Regular writing
Emails, posts, docs, narrative parts of applications — writing not centered on citations.
🧠 Philosopher mode (default): ① Dig for the one core idea → ② Interrogate the angle (why this, does it match the real story) → ③ Write only once the core is set → ④ Capture.
⚙️ Engineer mode: ① Define the goal (who reads it, what action) → ② Outline (get the skeleton confirmed) → ③ Draft (match tone) → ④ Trim + proof (names, emails, dates, numbers) → ⑤ Capture.
📚 Academic writing
Course papers, research reports, literature-backed essays — anything where claims need evidence. This track adds a mandatory evidence-gathering step, and every fact/claim must have a traceable source.
- Thesis — What is the claim/question? What does it answer? Bound the scope.
- 🔍 Gather evidence (mandatory — the core of this track) — Search the literature/data online; attach a traceable source to every claim (paper title, authoritative source, link). For broad needs, call the
researchordeep-researchskill. Separate fact / inference, flag what's uncertain, never fabricate. - Compose — Follow an academic structure (intro → claims → evidence → conclusion); attach citations as you write, evidence next to each claim.
- Verify citations — Check each one: it really exists, it actually supports the claim, format is consistent.
- Capture — Save to
outputs/drafts/draft_<english-slug>.md(body + reference list).
Mode still applies: 🧠 Philosopher = think the argument/position through before gathering and writing; ⚙️ Engineer = produce to the structure, time-boxed.
Wrap-up conventions
- Never send on the user's behalf — produce the draft, let them review.
- Live-search / verify facts — verify external facts online; academic citations must be traceable, never fabricated.
- Promote: if it's directional/reusable, offer to save it to long-term memory; one-off outputs stay put.
- Filenames use English slugs.