Recording
codewhale-hq/Codewhale
Capture screenshots on registered computers, record on macOS or HarmonyOS, and manage saved captures.
Review and record one pending human checkpoint in a research Workspace; use when a HUMAN Unit is blocked on an Approve C decision, and never treat silence or artifact existence as approval.
No licenceAuto-check passed
Install Human Checkpoint
$ npx skills add WILLOSCAR/research-units-pipeline-skills --skill human-checkpoint -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills human-checkpoint --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/human-checkpoint .claude/skills/human-checkpoint && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "human-checkpoint" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/human-checkpoint into .claude/skills/human-checkpoint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "human-checkpoint", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/human-checkpointType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add WILLOSCAR/research-units-pipeline-skills --skill human-checkpoint -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills human-checkpoint --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/human-checkpoint .agents/skills/human-checkpoint && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "human-checkpoint" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/human-checkpoint into .agents/skills/human-checkpoint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "human-checkpoint", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WILLOSCAR/research-units-pipeline-skills --skill human-checkpoint -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills human-checkpoint --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/human-checkpoint .cursor/skills/human-checkpoint && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "human-checkpoint" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/human-checkpoint into .cursor/skills/human-checkpoint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "human-checkpoint", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/WILLOSCAR/research-units-pipeline-skills.git --path .codex/skills/human-checkpoint--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add WILLOSCAR/research-units-pipeline-skills --skill human-checkpoint -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills human-checkpoint --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/human-checkpoint .gemini/skills/human-checkpoint && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "human-checkpoint" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/human-checkpoint into .gemini/skills/human-checkpoint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "human-checkpoint", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install WILLOSCAR/research-units-pipeline-skills human-checkpointInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add WILLOSCAR/research-units-pipeline-skills --skill human-checkpoint -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/human-checkpoint .github/skills/human-checkpoint && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "human-checkpoint" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/human-checkpoint into .github/skills/human-checkpoint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "human-checkpoint", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WILLOSCAR/research-units-pipeline-skills --skill human-checkpoint -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills human-checkpoint --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/human-checkpoint .opencode/skills/human-checkpoint && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "human-checkpoint" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/human-checkpoint into .opencode/skills/human-checkpoint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "human-checkpoint", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
human-checkpoint- GitHub stars
- 513
- Token cost
- ~791 tokens
- SKILL.md length
- 378 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- None found
At a glance
Review and record one pending human checkpoint in a research Workspace; use when a HUMAN Unit is blocked on an Approve C decision, and never treat silence or artifact existence as approval.
- Works in 4 steps: Identify the pending checkpoint → Review the declared Artifacts → Record approval through the adapter → …
- A HUMAN Unit is blocked on an Approve C decision
- SKILL.md covers Inputs, Outputs, Steps and Context Pointers, plus 1 more section
- Runs Python scripts from its folder; calls uv
What it does
Human Checkpoint is an agent skill from WILLOSCAR/research-units-pipeline-skills. Review and record one pending human checkpoint in a research Workspace; use when a HUMAN Unit is blocked on an Approve C decision, and never treat silence or artifact existence as approval.
Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/run.py`).
The repository describes itself as: Research pipelines as semantic execution units: each skill declares inputs/outputs, acceptance criteria, and guardrails. Evidence-first methodology prevents hollow writing…
When your agent uses it
- A HUMAN Unit is blocked on an Approve C decision
- Never treat silence
- Artifact existence as approval
Example prompts
- “/human-checkpoint”
Requirements
- Python 3
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Identify the pending checkpoint
- Review the declared Artifacts
- Record approval through the adapter
- Hand execution back to the Runner
What it can do on your machine
Read from SKILL.md and the folder at commit c92912a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Human Checkpoint loads about 791 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 378 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 378 words (~791 tokens).
“A checkpoint is consent, not a formatting step. It binds a named human Decision to the exact Artifacts and constraints reviewed before execution may continue.”
- name
- human-checkpoint
Files
SKILL.md and 1 other file (scripts) in .codex/skills/human-checkpoint of WILLOSCAR/research-units-pipeline-skills.
- SKILL.md
- scripts/run.py
Open the folder on GitHubat commit c92912a
Compare with similar skills
Human Checkpoint next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Human Checkpoint this skillWILLOSCAR/research-units-pipeline-skills | 513 | — | ~791 | Automated safety check: Pass | None | |
| Recordingcodewhale-hq/Codewhale | 41k | — | ~540 | Automated safety check: Pass | MIT | |
| Architecture Decision Recordsaffaan-m/ECC | 275k | 4 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Architecture Decision Recordsaffaan-m/ECC | 275k | 1 repos | ~863 | Automated safety check: Pass | MIT | |
| Architecture Decision Recordsaffaan-m/ECC | 275k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Browser Recordruvnet/ruflo | 74k | — | ~735 | Automated safety check: Notes | MIT |
Similar skills
Architecture Decision Records
affaan-m/ECC
Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README.
Architecture Decision Records
affaan-m/ECC
在Claude Code会话期间，将做出的架构决策捕获为结构化的架构决策记录（ADR）。自动检测决策时刻，记录上下文、考虑的替代方案和理由。维护一个ADR日志，以便未来的开发人员理解代码库为何以当前方式构建。
Architecture Decision Records
affaan-m/ECC
コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。
Browser Record
ruvnet/ruflo
Open a named, traced browser session into an RVF cognitive container with a ruvector trajectory recording every action
Grill And Record
asgeirtj/system_prompts_leaks
Run an explicitly requested decision interview and record each settled decision in durable project documentation.
More from WILLOSCAR/research-units-pipeline-skills
All 107 skills in this repoAppendix Table Writer
WILLOSCAR/research-units-pipeline-skills
Curate reader-facing survey tables for the Appendix (clean layout + high information density), using only in-scope evidence and existing citation keys.
Artifact Contract Auditor
WILLOSCAR/research-units-pipeline-skills
Audit one research Workspace for declared Unit outputs and Pipeline target Artifacts, writing output/CONTRACTREPORT.md; use for mid-Run coverage snapshots or final delivery completeness, not deep…
Arxiv Search
WILLOSCAR/research-units-pipeline-skills
Retrieve arXiv paper metadata with keyword queries or import an offline arXiv export, and save results as JSONL (papers/papersraw.jsonl).
Chapter Lead Writer
WILLOSCAR/research-units-pipeline-skills
Write H2 chapter lead blocks (sections/S<secidlead.md) that preview the chapter's comparison lens and connect its H3 subsections, without adding new facts.
Chapter Skeleton
WILLOSCAR/research-units-pipeline-skills
Build a retrieval-informed chapter skeleton (outline/chapterskeleton.yml) from taxonomy/core scope before stable H3 decomposition.
Dedupe Rank
WILLOSCAR/research-units-pipeline-skills
A skill your agent uses when a broad paper candidate pool needs deterministic deduplication and a stable core set.
Questions about Human Checkpoint
What does Human Checkpoint do?
Review and record one pending human checkpoint in a research Workspace; use when a HUMAN Unit is blocked on an Approve C decision, and never treat silence or artifact existence as approval. Human Checkpoint is an agent skill from WILLOSCAR/research-units-pipeline-skills. Review and record one pending human checkpoint in a research Workspace; use when a HUMAN Unit is blocked on an Approve C decision, and never treat silence or artifact existence as approval.
When should I use Human Checkpoint?
Human Checkpoint fits situations like: A HUMAN Unit is blocked on an Approve C decision; never treat silence; artifact existence as approval.
How do I install Human Checkpoint in Claude Code?
Run `npx skills add WILLOSCAR/research-units-pipeline-skills --skill human-checkpoint -a claude-code`. Or copy the skill folder (.codex/skills/human-checkpoint in WILLOSCAR/research-units-pipeline-skills) into .claude/skills/human-checkpoint in your project. Claude Code loads it when a task matches its description.
How do I install Human Checkpoint in Codex?
Run `npx skills add WILLOSCAR/research-units-pipeline-skills --skill human-checkpoint -a codex`. Or copy the skill folder (.codex/skills/human-checkpoint in WILLOSCAR/research-units-pipeline-skills) into .agents/skills/human-checkpoint in your project. Codex loads it when a task matches its description.
Can I use Human Checkpoint in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add WILLOSCAR/research-units-pipeline-skills --skill human-checkpoint -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/human-checkpoint, .gemini/skills/human-checkpoint, .github/skills/human-checkpoint and .opencode/skills/human-checkpoint in your project.
What does Human Checkpoint need to run?
Going by SKILL.md and its folder, Human Checkpoint needs Python for the scripts in its folder and the command-line tools its instructions call (uv). Our summary lists: Python 3.
Does Human Checkpoint access the network?
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Human Checkpoint safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Human Checkpoint use?
No licence was found for Human Checkpoint or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Human Checkpoint use?
About 791 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Human Checkpoint?
Skills that share tags, products or a category with Human Checkpoint: Recording (codewhale-hq/Codewhale, 41k stars), Architecture Decision Records (affaan-m/ECC, 275k stars), Architecture Decision Records (affaan-m/ECC, 275k stars) and Architecture Decision Records (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Human Checkpoint?
WILLOSCAR (a GitHub user) maintains it in WILLOSCAR/research-units-pipeline-skills, which has 513 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on October 5, 2026.
Source: WILLOSCAR/research-units-pipeline-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.