skills.rest
maestroventures
maestroventuresCOMMUNITY
Explore all skills by this author →
GitHub

aii-run-command

Builds and delivers double-click run files for user-executed terminal steps.

Updated Aug 21, 2026
Search Tags:#deployment#run command#double-click file#terminal handoff#exec bit#show in folder#builder script
One-click install
npx skills add https://github.com/maestroventures/aiintegrator --skill aii-run-command-maestroventures
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aii-run-command
Source: https://github.com/maestroventures/aiintegrator/tree/main/plugins/aii-blueprint/skills/aii-run-command
Command: npx skills add https://github.com/maestroventures/aiintegrator --skill aii-run-command-maestroventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Handing a user a pasted terminal command or a "just run this" instruction leads to inconsistent execution, lost exec bits, and no clean signal of success or failure. This Skill enforces one sanctioned mechanism: every step the user must run on their own machine becomes a single double-click file (.command on Mac, .bat on PC) delivered with a Show in Folder card. ## Core Features & Use Cases - Deterministic run-file building: Calls a builder script that fills a sanctioned template, names the file, sets the exec bit, and stamps session ownership and tenant-local time. - Turn-one precondition probe: Verifies the run folder can accept an executable file before any work begins, with a fail-loud stop and two named recoveries if it cannot. - Show-in-Folder delivery gate: Sends, binds, re-chmods, and verifies each file so the delivery card defaults to Show in Folder, never a Download-only fallback. - One-step-then-wait loop: Hands one file, stops, waits for the user's screenshot, fixes only the failing step, and never restarts the sequence. - Use Case: During an app deployment, the user must install a CLI tool and set an API key. The Skill builds one .command file per step, delivers each with a Show in Folder card, and waits for a ✅ DONE screenshot before handing the next. ## Quick Start Ask the assistant to give you the install step as a double-click run file you can execute on your machine.

Frequently Asked Questions about aii-run-command

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

FAQPage Schema
How do I hand a user a command to run without pasting it in chat?▼

Build a double-click run file with the builder script: a .command file on Mac or .bat on PC containing the exact command. Deliver it bound to the real run-folder path so the card defaults to Show in Folder, then wait for the user's result before continuing.

How do I make a delivered script executable on the user's machine?▼

Run the builder on the user's machine through the session shell so the exec bit is set when the file is written. After the file commit, re-run chmod +x and verify with test -x, because the commit strips the exec bit every time.

Why does the delivered file show Download instead of Show in Folder?▼

The Show in Folder default requires two things: binding the sent file id to a real run-folder path, and omitting the display parameter on send. Passing display: "attach" overrides the bind and renders a Download and open card even when the bind succeeds.

Does this apply to scripts the assistant runs itself?▼

No. The run-file mechanism only applies to steps the human must execute on their own machine, such as installs, deploys, or setting API keys. Code the assistant writes and runs in its own sandbox is never gated and never becomes a double-click file.

What happens if the session cannot set the exec bit?▼

The turn-one probe detects this before any work begins and stops with two recoveries: reconnect the workspace folder and restart the task, or run the task directly on the user's computer. It never falls back to a sandbox copy or alternate transport.

What should I do when a run step fails?▼

Read the user's screenshot, fix only the failing step, and rebuild just that one file with the builder. Re-deliver it as a fresh card using the full send-bind-chmod-verify sequence, and never restart steps that already showed DONE.

Related Skills

Explore More Software Engineering Skills→
Lia-CreativeLia-Creative
1

toy-pickup

Loads scoped context files for Lia Tools sessions in a fixed read order.

Official
Intermediate
Joncik91Joncik91

implement

Execute machine-verifiable specifications step-by-step with verification and retry logic.

Community
Advanced
pgoellpgoell

verification-before-completion

Requires fresh command output as evidence before claiming work is complete.

Community
Basic
xalgordxalgord
954

bypassing-restricted-shells

Escapes restricted shells, chroot jails, and command filters during authorized penetration tests.

Community
Intermediate