跳到正文
cccskills
免费在 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".

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md3.7 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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

FormatLengthWhere it goes
Short expert post300–600 wordssocial / a channel
Longform post800–1500 wordsblog / newsletter
Deep analytical breakdown1500–3000 wordsa standalone piece
Case study1000–2000 wordsportfolio / blog

Pipeline (4 phases)

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

  1. Clarify if unclear: format? audience? any data/insights that must be included?
  2. State the central thesis in one sentence — what the reader walks away with.
  3. 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]
    
  4. 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:

  1. "What if I'm wrong?" — is there a counterargument to the thesis? How do you handle it?
  2. "Where do I generalize without data?" — find "many", "as a rule", "obviously" — replace with specifics or cut.
  3. "What won't the reader get?" — any terms unexplained for a non-specialist?
  4. "What's stale?" — any data that may be outdated (>6 months)?
  5. "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.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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".

中文简介正在准备中。当前显示原文说明。

Sanexxxx777/curated-claude-code162026年9月7日 更新

konsilium

免费

Council — 5 independent AI perspectives + mutual critique + synthesis (adapted from karpathy/llm-council for Claude Code). For high-stakes decisions where the answer does NOT follow unambiguously from the data — go/no-go before real consequences, critiquing a methodology, choosing between competing approaches, pressure-testing a conclusion you're attached to, designing risk controls. NOT for log/data analysis (the council has no data access) and not for factual lookups. Triggers — "convene the council", "run it past the council", "go/no-go", "pressure-test this".

中文简介正在准备中。当前显示原文说明。

Sanexxxx777/curated-claude-code162026年9月7日 更新

pre-push

免费

A gate before git push / deploy — assembled from your own tools (secret-grep + slop-scan + code-review + build/compile + optional worktree isolation), so AI junk (slop / bugs / secrets / uncompiled code) never reaches a remote or a production server. Turns "I hope it's clean" into a verifiable criterion. Branches: web/OSS (git push/PR) vs deploy-to-server service. Triggers — "check before push", "clean push", "gate before push", "finalize before commit", "run before deploy".

中文简介正在准备中。当前显示原文说明。

Sanexxxx777/curated-claude-code162026年9月7日 更新

proof

免费

Prove — or honestly fail to prove — a specific technical claim: "the fix works", "it's deployed", "the service is running", "the site is done", "there are no vulnerabilities". Atomizes the claim, picks the shortest decisive signal on the evidence ladder, and returns a verdict from a fixed vocabulary (pass / partial / fail / skip) with an explicit coverage boundary. NOT code review, NOT a fix, NOT orchestration — only "what is proven, and what we merely hope". Triggers — "prove it works", "is it really done?", "are you sure?", "we deployed — is it live?", "verify that", "did we actually check?".

中文简介正在准备中。当前显示原文说明。

Sanexxxx777/curated-claude-code162026年9月7日 更新

Security launch audit for a public web app BEFORE you ship or hand it to a client — "vibe coders are getting sued", systematized. An executable pipeline: classify (static / full-stack / AI) → run sections (secrets+supply-chain, DB, auth, infra+headers, legal, LLM/injection) orchestrating deterministic tools + manual checks → GO/NO-GO report. Adapted from Prajwal Tomar's playbook, extended with prompt-injection / supply-chain / secret-history / dependency-CVE layers. NOT the same as pre-push (that = clean push; this = is the product itself safe to launch). Triggers — "security checklist for the site", "audit before launch", "is the site safe", "check before handing to client".

中文简介正在准备中。当前显示原文说明。

Sanexxxx777/curated-claude-code162026年9月7日 更新

Preventive hygiene audit of your own Claude Code configuration — memory files, project context (CLAUDE.md), rules, permissions, skills — a deterministic scan of sizes / broken links / stale entries / excessive permissions / junk + interpretation + targeted fixes by agreement. Keeps the setup from rotting before it breaks. Triggers — "check the system", "system health", "workflow hygiene", "what to clean up", "audit memory", "optimize the system".

中文简介正在准备中。当前显示原文说明。

Sanexxxx777/curated-claude-code162026年9月7日 更新

查看 Sanexxxx777 的全部技能

报告此技能的问题