printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a broken/lost internal copy. Trigger phrases: "import the CLI", "bring it into my library", "fetch from public library", "I don't have it locally yet".
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
Source text is outsider-authored only via user-supplied CLI selection (e.g., “notion”, “cal.com”) and then fetches trusted vendor-authored repo contents from GitHub (`registry.json` and the selected CLI subtree) rather than injecting arbitrary free text into an LLM at runtime.
W012: Unverifiable external dependency detected (runtime URL that controls agent).
What this means
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Why it was flagged
The import-fetch.sh script performs a runtime "git clone" from https://github.com/mvanhorn/printing-press-library.git (references/import-fetch.sh lines 57-59), and the fetched repository is later built (go build) in SKILL.md (lines 239-240), meaning remote code is fetched at runtime and executed locally.
- Repository
- mvanhorn/cli-printing-press
- Commit
6dc0cee
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.