無料GitHub で公開

longread

Write an analytical longform piece — a 4-phase pipeline from raw idea to finished text, with research-backed facts and a devil's-advocate pass before publishing. Invoke /longread <topic>. Triggers — "write a longread about X", "write an analytical breakdown of Y", "write an expert post", "turn this into an article".

Sanexxxx777/curated-claude-code

インストール方法を見る

含まれるファイル（1）

SKILL.md3.7 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Longread Writer

A pipeline for analytical writing. Structure first, facts second, voice third, self-critique last. Works for any subject — adapt the sources to the domain.

Output formats

Format	Length	Where it goes
Short expert post	300–600 words	social / a channel
Longform post	800–1500 words	blog / newsletter
Deep analytical breakdown	1500–3000 words	a standalone piece
Case study	1000–2000 words	portfolio / blog

Pipeline (4 phases)

Phase 1 — Cheap: angle & structure (don't write yet)

Clarify if unclear: format? audience? any data/insights that must be included?
State the central thesis in one sentence — what the reader walks away with.

Propose a structure (3–5 blocks):

Hook: [a provocative fact / question / contradiction]
Block 1: [name]
Block 2: [name]
…
Conclusion / CTA: [what the reader should do]

Show the structure and confirm before Phase 2.

Phase 2 — Research: gather facts

Without specifics, the text is empty. For each block:

Find 1–2 key facts/figures.
Find 1 concrete example or case.
Note the source (URL / dataset / first-hand).

Verification rule: every concrete number needs a source. Can't find one → write [need figure] and move on. Never invent a number.

Phase 3 — Write: section by section

Write in a plain, conversational voice, not an academic one.

2–4 sentences per thought, no more.
Concrete: numbers, names, dates — not "many", "often", "significantly".
No filler openers ("It should be noted that…", "Thus…").
No AI-aesthetic ("In conclusion, it is worth noting…").

Each block's shape:

Claim (1 sentence — the block's point)
Evidence (fact / figure / example)
Why it matters
[transition to the next block]

Write the hook last (once you know what actually grabs after the body is done). Write section by section; show intermediate drafts if approval is useful.

Phase 4 — Devil's advocate: pre-publish check

Ask yourself 5 questions:

"What if I'm wrong?" — is there a counterargument to the thesis? How do you handle it?
"Where do I generalize without data?" — find "many", "as a rule", "obviously" — replace with specifics or cut.
"What won't the reader get?" — any terms unexplained for a non-specialist?
"What's stale?" — any data that may be outdated (>6 months)?
"Why read to the end?" — is there an interest dip in the middle?

Make targeted edits, don't rewrite everything.

Final

Title (for a post — first line as a bold headline).
The text in the chosen format.
If relevant: a note on what illustration/image type fits.

Anti-patterns

❌ Writing without a structure — always Phase 1 first.
❌ Facts without a source — better [need figure] than an invented number.
❌ Academic style ("this work is dedicated to…").
❌ A longread of generalities — if there's no concrete data, say so before writing.
❌ Skipping the devil's-advocate pass — that's where the weak spots are.

Examples of a strong hook

"A prediction market paid traders $2.3M in one day. Half of it went to 12 wallets."
"Everyone knows BTC correlates with macro. Nobody says how much — by timeframe it runs from 0.1 to 0.9."
A specific number + a specific stake beats any abstract claim.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

goal

無料

Autonomous goal loop — give it ONE goal plus how to verify it, the agent runs check→fix→check itself and comes back only with the finished result (code with audit, research with fact-check, content with critique, audit/backtest). Self-verification instead of constant supervision, with hard safety guards. Vary the loop with a verification rubric designed before it runs. Triggers — "work autonomously to the result", "don't come back until it's done", "run the loop yourself", "drive it to done".

日本語の概要は準備中です。原文の説明を表示しています。