Skip to content
TrustedSkillsbeta
Back to all skills

Human Checkpoint

Checked
willoscar·vlatest·other

This skill simulates a human review process by pausing execution and prompting for confirmation, ensuring critical decisions are validated.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add willoscar/research-units-pipeline-skills --skill human-checkpoint -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

willoscar

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned willoscar/research-units-pipeline-skills at f53f82f8d7.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
f53f82f8d7
Manifest
.codex/skills/human-checkpoint/SKILL.md
Scanned
2 files, 126 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The human-checkpoint skill allows an AI agent to pause its current task and request a human review of the progress made so far. This is particularly useful for complex or high-stakes tasks where periodic validation from a human expert is required. The agent can then resume execution based on feedback received.

When to use it

  • Complex Reasoning: During multi-step reasoning processes, especially when dealing with ambiguous information.
  • Creative Tasks: To solicit feedback on creative outputs like writing or design concepts before proceeding further.
  • High-Stakes Decisions: Before making critical decisions that could have significant consequences.
  • Long Running Processes: When a task is expected to take a long time, checkpoints can ensure the agent remains aligned with user intent.

Key capabilities

  • Pauses current execution flow.
  • Requests human review of intermediate results.
  • Resumes execution based on feedback.

Example prompts

  • "Please pause and ask for a human checkpoint before generating the next draft."
  • "Before proceeding with this decision, request a human review to ensure accuracy."
  • "Implement a human checkpoint after each iteration of this process."

Tips & gotchas

The effectiveness of this skill depends on clear instructions provided to the AI agent regarding when and how to trigger checkpoints. Ensure that the agent understands the context in which human intervention is most valuable.