Skip to content
TrustedSkillsbeta
Back to all skills

Dev Checkpoint

Listed
andreaserradev-gbj·vlatest·other·MIT

Dev Checkpoint analyzes code for potential issues like bugs & vulnerabilities, boosting development efficiency & code quality.

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 andreaserradev-gbj/dev-workflow --skill dev-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

andreaserradev-gbj

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: feross.org.

    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.

    Hosts contacted

    feross.orgundeclared

    What it found

    • plugins/dev-workflow/skills/dev-checkpoint/scripts/dev-workflow.cjs:213contacts feross.org
      (*! queue-microtask. MIT License. Feross Aboukhadijeh <https://feross.org/opensource> *)
    • plugins/dev-workflow/skills/dev-checkpoint/scripts/dev-workflow.cjs:216contacts feross.org
      (*! run-parallel. MIT License. Feross Aboukhadijeh <https://feross.org/opensource> *)

  • 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 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 andreaserradev-gbj/dev-workflow at 0462dcba16.

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

Commit
0462dcba16
Manifest
plugins/dev-workflow/skills/dev-checkpoint/SKILL.md
Scanned
8 files, 952 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 dev-checkpoint skill allows AI agents to pause execution, record state, and resume later. This is particularly useful for long or complex development tasks that might be interrupted. It enables saving progress at specific points in a workflow, facilitating debugging and iterative development.

When to use it

  • Long build processes: Pause a lengthy compilation process to free up resources or handle other tasks.
  • Complex debugging scenarios: Save the state of an application during a difficult-to-reproduce bug for later analysis.
  • Iterative development cycles: Capture intermediate states in a project to easily revert or compare different versions.
  • Workflow interruptions: Resume a halted workflow from exactly where it left off, preserving all context and data.

Key capabilities

  • State recording: Captures the current state of variables and environment.
  • Execution pausing: Temporarily halts the execution flow.
  • Resumption: Restarts execution from the checkpointed state.

Example prompts

  • "Checkpoint my development progress now."
  • "Save the current application state to a checkpoint file."
  • "Resume the last saved checkpoint."

Tips & gotchas

The skill requires sufficient disk space to store checkpoint files. Ensure you have adequate permissions to write to the designated storage location for checkpoints.