Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Runtime Prerequisite Proof — Safe Setup Checks

    1

    Find the declared prerequisite blocking setup: a runtime version, required file or environment name. Get the next repair to hand to its owner.

    Free

    1 useSecurity scanned
    Runtime Prerequisite Proof — Safe Setup Checks

    Runtime Prerequisite Proof — Safe Setup Checks

    Example session with this skill installed

    Use the selected synthetic project. Its checklist requires Python>=3.10, project.toml and the environment name RPP_DEMO_TOKEN. The name is present; never report its value. Check the prerequisites without repairing them. After the owner supplies the missing file, repeat the same checklist and show what changed.

    • Read your context and instructions
    • Compiled the runtime prerequisite proof
    • Generated the document

    Setup check: one file was missing

    Actual synthetic local demonstration. The same checklist was checked before and after an explicit owner repair.

    This readable report summarizes captured JSON output. The helper emits JSON or Markdown to stdout. Any Agensi-generated PDF/file card is a marketplace preview, not a file produced by the helper.

    PrerequisiteFirst observationAfter owner repair
    Python>=3.103.14.3 — PASS3.14.3 — PASS
    project.tomlMissing — REVISEPresent — PASS
    RPP_DEMO_TOKENName present — PASSName present — PASS

    First next action: ask the project owner to supply the documented project.toml. The helper did not install, create or repair it. The synthetic harness supplied that file between observations.

    Repeated result: PASS for these declared checks. No project content was read for the file-presence check; the environment value was absent from all captured output. The missing-file run created no project files; the repaired run preserved fixture bytes, modification times and modes.

    This is a point-in-time prerequisite report. A present name does not establish a valid credential; an empty value also counts as present. Application behaviour, dependencies, connectivity and release readiness were not tested. The original observation's full temporary path is retained in raw proof; it is omitted from this human report.

    runtime-prerequisite-proof-safe-setup-ch.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Setup fails, and the next suggestion is another install, reset or shell command. First, find out which documented prerequisite is actually missing.

    Runtime Prerequisite Proof checks a small checklist you supply: supported Python, Node.js or Git minimum versions, required project files and environment variable names. The report gives each check an observed result and a next action, so you can hand one precise repair to the environment or project owner.

    Check, repair, repeat

    A missing project.toml, for example, returns REVISE while the other checks retain their own results. The owner supplies the intended file; you repeat the same manifest and compare both reports. The helper does no automatic repair.

    It uses fixed, bounded version probes and file-presence checks. Environment checks report name membership without exposing values. Unknown version output, unsafe paths or missing trust produce HOLD rather than a guessed result.

    Python 3.10+ and approved local file/terminal access are required. Node.js/Git probes also need explicitly trusted absolute installed executable paths outside the project; the helper does not discover or sandbox them. It creates short-lived probe directories and may terminate only its own timed-out or overflowing probe child.

    A PASS covers the declared versions and presence checks at that moment. It does not prove that dependencies work together, credentials are valid or the application is ready to deploy. Local macOS Python 3.12 and 3.14 execution is checked; other hosts and on-demand helper delivery remain unverified.

    Try the included synthetic quickstart, then supply the prerequisites your project actually documents.

    Checks declared supported minimum versions and presence only. PASS does not establish dependency compatibility, application behaviour, connectivity, credential validity, authorization or release readiness.
    An empty environment value counts as present. The report never fetches values for serialization; version probes receive a minimal non-secret environment and raw probe output is not serialized.
    Caller must trust the interpreter and selected absolute runtime executables; fixed arguments are not an executable sandbox. No PATH discovery or project wrapper execution.
    Each version probe has a 2-second timeout and 8192-byte combined capture ceiling. Only the exact probe child launched by the helper may be terminated/reaped.
    No install, remediation, package manager, project setup script, network/database request or connection check. File paths reject symlink components and traversal; concurrent changes remain outside a point-in-time guarantee.
    Python 3.10+ is required. Exact local execution was checked on macOS Python 3.12/3.14; Python 3.10, Windows/Linux and marketplace/MCP helper materialization are unverified. A text-only host needs an approved route to the exact bundled files or must report delivery unavailable.
    The helper emits JSON or Markdown to stdout. Any Agensi-generated PDF/file card is a marketplace preview; it does not prove that the helper created a file in your workspace.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 25 days ago

    • Free with an Agensi account

    Requires

    Python 3.10+
    Terminal access
    Python
    Node.js

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Environment Variables

    Read the explicitly supplied prerequisite JSON manifest Stat only declared project-relative file path components; no contents read Inspect presence of declared environment variable names; values not fetched for reports Execute only explicitly trusted runtime executables with fixed --version argument Create and remove short-lived probe working directories outside the selected project Terminate/reap only the exact owned probe child on timeout or output overflow

    Listed27 days ago
    Updated25 days ago

    What's inside

    Frequently Asked Questions

    It gives each missing or below-minimum prerequisite to its owner. The helper performs no repair or installation. After the owner repairs it, repeat the same manifest and retain both reports.

    No. Manifests contain only supported tool names and minimum versions, relative file paths and environment variable names. Unknown fields and commands produce HOLD.

    Only the declared version and presence checks at observation time. Dependencies, application behavior, connectivity, credential validity and release readiness remain unverified.

    Environment checks inspect name membership and never fetch values for reporting. The version probes receive only fixed PATH/LANG/LC_ALL entries; raw probe output and the full process environment are not serialized. Do not put secret values in the manifest.

    Yes, with the documented supported stable output and an explicitly trusted absolute installed executable path outside the project. The helper does not search PATH, run project wrappers or sandbox an executable.

    That delivery route is unverified. The host needs approved local execution and the exact bundled helper. Text-only hosts must obtain/materialize it through an approved resource route; report HOLD if that route is unavailable.

    New in Testing & Debugging