CortexPilot Adoption Router
v1.1.1Teach the agent how to connect the published CortexPilot read-only MCP package, choose the right public lane, and use the stable read-only tools without over...
⭐ 0· 50·0 current·0 all-time
byYifeng[Terry] Yu@xiaojiou176
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, and included references consistently describe a read-only CortexPilot MCP onboarding helper. The files and SKILL.md focus on choosing read-only lanes and installing a published package (cortexpilot-orchestrator==0.1.0a4). No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Runtime instructions stay within the stated read-only inspection scope (list_runs, get_run, list_queue, proof/incident reads). The SKILL.md and reference docs explicitly warn not to claim write or hosted operator capabilities and instruct the agent to use provided install/config snippets. There are no instructions to read unrelated host files, secrets, or transmit data to external endpoints beyond installing the published package.
Install Mechanism
This is instruction-only (no install spec), but it explicitly advises installing a published PyPI package via the host 'uvx' command (uvx --from cortexpilot-orchestrator==0.1.0a4 cortexpilot-readonly-mcp). That is proportionate to the skill's purpose but carries the usual supply-chain risk of installing third-party packages — the skill itself does not include arbitrary download URLs or obscure installers.
Credentials
The skill does not request any environment variables, credentials, or config paths. The instructions and JSON snippets show only how to register the MCP server command/args; no secrets are asked for or implied.
Persistence & Privilege
The skill is not marked always:true and is user-invocable; it does not request to modify other skills or system-wide settings beyond adding a hosted MCP server entry under the host's normal configuration. Autonomous invocation is allowed by default but is not combined with other privilege concerns.
Assessment
This skill appears coherent and focused on read-only inspection. Before installing or running it, do these checks: (1) Confirm the PyPI package cortexpilot-orchestrator==0.1.0a4 is published by a trusted maintainer and review its release page/metadata; (2) Inspect the package contents (or review its source repo) in a sandbox before allowing it to run on production hosts — installing packages runs third-party code; (3) Ensure the host's uvx tool invocation matches your policy and that you understand what 'cortexpilot-readonly-mcp' will do; (4) Do not supply credentials to this skill; if you need write or hosted capabilities, require explicit confirmation and additional credentials only when justified; (5) If you want higher assurance, run the MCP attach and first reads in an isolated environment and verify the MCP only exposes the read-only tools listed in CAPABILITIES.md.Like a lobster shell, security has layers — review code before you run it.
cortexpilotvk973ntnz292m4e3m98sn9xkg8x84g9g2latestvk973ntnz292m4e3m98sn9xkg8x84g9g2local-firstvk97366emrzp2pvjxdf4raez7ps84fpcqmcpvk973ntnz292m4e3m98sn9xkg8x84g9g2proofvk973ntnz292m4e3m98sn9xkg8x84g9g2read-onlyvk973ntnz292m4e3m98sn9xkg8x84g9g2routervk97366emrzp2pvjxdf4raez7ps84fpcqworkflowvk973ntnz292m4e3m98sn9xkg8x84g9g2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.