research-sourcing

Sourcing discipline for research and analysis: validate each claim against a primary source, link it, and verify on-chain identifiers before citing them. TRIGGER when producing research, analysis, comparisons, or any write-up that asserts external facts about protocols, libraries, incidents, or on-chain state. DO NOT TRIGGER for reasoning about code in the current repo, which is settled by reading it.

Jump to install

Repository: liuchengxu/dotfiles
Last source activity: August 7, 2026 at 17:04
Detected SKILL.md language: English
Stars: 216
Forks: 88

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/liuchengxu/dotfiles --skill research-sourcing

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

adversarial-review

Use when asked to review code or a design at any granularity — a pull request, an architecture/design proposal, a module, a file, or a whole codebase/repo — "review this PR", "review this repo", "audit this module", "challenge this design", "is this architecture sound", "adversarial review"; especially anything touching trust boundaries, signing/key flows, consensus rules, upgrade/governance logic, protocol APIs, or crate/module boundaries being locked in. DO NOT use for quick working-diff hygiene (use code-review) or prose/document editing passes (use doc-review).

2026-08-08

doc-review

Review a written document (markdown, design doc, runbook, README, etc.) for redundancy, inconsistency, clarity, and density. Apply the general rules first, then the type-specific addendum for the doc's genre. TRIGGER when: user asks to "review", "audit", "clean up", "tighten", "compress", or "check" a markdown / documentation file (including a proposal, pitch, or decision memo); user pastes a doc and asks for an editorial pass; user asks if a specific reviewer comment is "addressed"; about to DRAFT a design doc, proposal, planning doc, or RFC (apply Part C's authoring defaults, then self-review). DO NOT TRIGGER when: user wants substantive technical correctness review of a design, algorithm, or protocol (use adversarial-review), or review of a code diff or implementation (use code-review); writing a GitHub issue or PR body (use writing-issues-and-prs). Design docs and proposals may still trigger for structure, readability, and claim/ask calibration.

2026-08-08

md2html

Render a markdown doc as a self-contained HTML view, written by hand for that document. TRIGGER when the user asks for an "html view", "make this readable", "render as html/page", "open as a page", or wants a shareable page of a markdown deliverable (review report, plan, ADR, research/design note). DO NOT TRIGGER to author new content (write the markdown first), for the todo board (use /todo), or to build interactive dashboards and tools (author those directly).

2026-08-08

View all from this repository

name

research-sourcing

description