prompt-exec

Execute stored .prompt-forge prompts verbatim after explicit user consent.

6|1|Updated Jan 5, 2026

Search Tags:#verification #safety #execution #artifact #prompt #consent #forging

Ready to run

npx skills add https://github.com/JordanGunn/skills --skill prompt-exec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prompt-exec
Source: https://github.com/JordanGunn/skills/tree/main/skills/prompt/exec
Command: npx skills add https://github.com/JordanGunn/skills --skill prompt-exec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Execute forged prompts with safety and explicit consent, preventing accidental harmful runs.

Core Features & Use Cases

Exact prompt execution: Run the provided prompt verbatim without reinterpretation.
Safety-first workflow: Checks for artifact presence and status, and requires explicit user confirmation before execution.
Auditability: Deletes the canonical artifact only after successful execution and produces an execution receipt.

Quick Start

Initiate a prompt execution by confirming you want to run the forged prompt exactly as stored.

Frequently Asked Questions about prompt-exec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I execute stored prompt artifacts verbatim without altering the content?▼

Executing prompt artifacts verbatim requires a deterministic workflow that runs the text exactly as written. This process enforces exact execution by preventing any reinterpretation of the stored prompt file.

What safety checks are required before running deterministic prompt execution workflows?▼

Deterministic prompt execution requires verifying artifact existence and status on disk, followed by explicit user consent. These safety checks prevent accidental harmful runs by ensuring you confirm the action before execution begins.

How does an audit trail work when executing prompts stored on disk?▼

An audit trail for prompt execution works by deleting the canonical artifact only after successful completion and producing an execution receipt. This records the run and ensures the prompt cannot be executed again accidentally.

Do I need to manually delete the prompt file after a successful execution?▼

You do not need to manually delete the prompt file after execution. The workflow automatically deletes the canonical artifact from disk after a successful run and generates an execution receipt for auditing.

Can I modify a forged prompt before triggering the execution process?▼

You cannot modify a forged prompt before execution. The workflow enforces a safety-first approach that runs the provided prompt verbatim without reinterpretation, requiring explicit consent to trigger the unaltered artifact.