Tech Article Reproducibility
Evaluate the reproducibility of technical articles. Dispatch a subagent to simulate a first-time reader reproducing the work locally and list missing information. Use as the final check on a draft before publication or to recheck a published article before responding to reader feedback.
Install
npx skills add mizchi/skills --skill tech-article-reproducibilitygit clone --depth 1 https://github.com/mizchi/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/tech-article-reproducibility ~/.claude/skills/tech-article-reproducibilityPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Tech Article Reproducibility Measure the quality of a technical article from the angle of "can a reader reproduce the same thing on their machine?" This is an independent axis from prose-style evaluation (mizchi-blog-style) or logical evaluation. The premise: **the most important thing about a technical article is whether a reader can reproduce it on their own machine.** ## When to use - Final pre-publication check on a technical article draft - Hands-on articles / tutorial articles - Tool introduction articles / setup articles - Verifying an article that claims "it worked" When not to use: - Conceptual explainer articles (nothing to reproduce) - Poems / opinion pieces - Self-contained small tidbits ## Reproducibility check axes (10 axes) Score each axis on a 0–2 scale, 20 points total → converted to a 10-point scale. | # | Axis | 0 (NG) | 1 (partial) | 2 (OK) | |---|---|---|---|---| | 1 | Environment prerequisites stated | No OS / version / required tools listed | Partially listed | Everything listed (OS, lang version, CLI tools) | | 2 | Code completeness | Fragments only, imports/setup omitted | Only the main part | Full, copy-pasteable form that runs | | 3 | Command accuracy | Placeholders left as-is (`<your-token>` etc. without explanation) | Some placeholders | Runnable as-is | | 4 | Version dependency stated | No mention | Partial | Explicit, e.g. "works on v3.x", "v2 or earlier behaves as X" |
Details
- Skill name
tech-article-reproducibility- Repository
- mizchi/skills
- Path
tech-article-reproducibility/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Tech Article Reproducibility skill do?
Evaluate the reproducibility of technical articles. Dispatch a subagent to simulate a first-time reader reproducing the work locally and list missing information. Use as the final check on a draft before publication or to recheck a published article before responding to reader feedback.
How do I install the Tech Article Reproducibility skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add mizchi/skills --skill tech-article-reproducibility. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Tech Article Reproducibility popular?
It lives in mizchi/skills, which has 423 GitHub stars and 6 forks.
Related skills
Actions CI Tuning
423mizchi/skills
Use when auditing or improving GitHub Actions workflows for a project. Covers cache setup (npm/pnpm/yarn), job parallelism, shard-based test splitting, artifact handling pitfalls, and Playwright-specific patterns. Trigger on: slow CI, cache miss, flaky shard jobs, merge-reports failures, or an explicit 'tune CI' request.
AI Index
423mizchi/skills
Method and tooling for measuring how AI-generated a piece of prose reads, in Japanese or English. Two layers — a deterministic lint for removable surface tells (scripts/slopscore.py, no API) and a judgment layer of typed probabilistic questions (Jev noul/score) for the tells that survive editing. Includes measured human/AI baselines, a gap-first calibration procedure, and labeled fixtures. Use when building or calibrating an AI-likeness score, or when a draft needs a defensible number rather than a vibe. For writing guidance use natural-writing-ja / natural-writing-en instead.
Apm Usage
423mizchi/skills
Reference for APM manifests, installation, targeted updates, deployment paths and lockfiles. Invoke when the user explicitly asks about APM or apm.yml, or an unfamiliar APM command/error needs exact CLI details. Do not automatically invoke for every project that happens to have installed skills.
Imprint
104ilang-ai/Imprint
Your habits, imprinted on AI. Learns how you work from conversation, builds a portable profile, and applies judgment that adapts to you: when to act, when to check with you, when to follow the project's rules over your own defaults. Use this skill whenever the user starts a new session, opens a project, writes or reviews code, debugs, plans, or writes commits. If .dna.md does not exist yet, start the onboarding conversation before doing anything else. Active in almost every working session.
Natural Writing Ja
423mizchi/skills
Japanese prose norm for writing explanatory text that does not read as machine-generated. Built on one diagnostic axis (does a sentence update the situation or the document?) plus register purity, sentence-beat and 体言止め/反問 rules calibrated against 937 sentences of human technical writing. Use when drafting or revising Japanese articles, docs, or long-form explanations, especially after an LLM produced the draft. For English use natural-writing-en; for scoring a draft use ai-index.
Mojo Syntax
213modular/skills
Help to write Mojo code using current syntax and conventions. Always use this skill when writing any Mojo code, including when other Mojo-specific skills (e.g., mojo-gpu-fundamentals) also apply. Use when writing or reviewing Mojo code, translating projects to Mojo, or otherwise generating Mojo. Use this skill to overcome misconceptions with how Mojo is written.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.