varg-publish-skill@1.0.4
CAUTION· static onlyPublisher claims: "Turn your agent skill into a varg how to listing: reads a skill folder or repo, checks it against the varg media skill standard, fills the one card format every listing on varg how to (varg.ai/how-to) uses — name, one-line summary, use-when triggers, category, install command, a real example of the output — shows it to the person and publishes it for review through the varg MCP publish_skill tool (or the API with a varg key). Use when someone says "publish my skill", "list this skill on varg", "submit my skill to varg how to", "add my skill to the catalog", "how do I get my skill found by agents", or the same in any language. Not for finding a skill (use how-to-make-ai-video), not for writing the skill itself, and not for contributing to the vargHQ/skills repo (that is a pull request)." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-13 and scored it 57/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: HTML comment carrying imperative instructions to the agent; Pipe-to-shell pattern. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
Generated by .github/readme/build.ts from SKILL.md files and .github/readme/*.json. Edit those and run `bun .github/readme/build.ts`; CI fails when this file isFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.`curl | bash` or install hooks, scripts calling unknown hosts, bundled media without a license, no SKILL.md description.Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.`curl | bash` or install hooks, scripts calling unknown hosts, bundled media without a license, no SKILL.md description.Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.| `install` | The exact command from the repo's docs; else `npx skills add <owner>/<repo> --skill <name>` only when the folder sits where that CLI finds it; else leave out |Fix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
23 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim vargai: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
- Pipe-to-shell pattern≈ +4 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.