pi-native-e2e-dev
Spin up a live local Omnigent server + runner and exercise the native Pi TUI harness (pi-native) end-to-end — launch the real pi CLI via…
Examining code for the line that is wrong
What it does
Pi native harness: end-to-end dev & testing (local server/runner)
What it can touch
No script files in its folder
Its folder holds text, not programs — but the instructions do tell your AI to run commands (see below).
How we know
Listed the one file in the skill’s folder on GitHub; none is a script or program.
Asks for an API key or token
You will need an account with the service it talks to, and your own key. Keep keys in your settings or environment, never in a chat.
How we know
The SKILL.md mentions an API key or access token.
Installs other software
Following it will install packages (npm, pip, brew or similar). Those come from their own publishers, not from this skill.
How we know
The SKILL.md contains package-install commands.
Its code sends data over the internet
A script in it uploads or posts data. That is normal for a skill that talks to a service — check that the address is the service you expect.
How we know
SKILL.md line 126: “curl -s -X POST "$SERVER/v1/sessions/$CONV/events" -H 'content-type: application/json' -d '{"type":"message","data":{"role":"user","conte…”. Read 2026-10-05, commit 4edb75c.
SKILL.md, line 126 ↗No known risk pattern found
Launch7’s automated check read all 1 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-05, commit 4edb75c by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to omnigent-ai/omnigent: 2026-10-05 (0 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from omnigent-ai
All from this publisher →- api-docs
Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself.
- cross-review
Verify an implementer's diff with an INDEPENDENT, different-vendor sub-agent (diff plus contract only); turn blocking issues into fix-tasks…
- debate
Have the Claude and GPT partners critique each other's answers across a configurable number of rounds (default 1) before converging on a synthesis.
- deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any…
- detect-framework
Detect Python agent frameworks from code imports and map them to Omnigent executor types.
