Prepare and verify ruv-FANN Cargo/npm release candidates, pinned Rune builds, frozen source, real artifact provenance, clean consumers, dependency order, and immutable receipts. Use for Rune integration, build reproduction, CI/CD, release readiness, archive contents, version migrations, or candidate validation; it does not authorize publication.
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
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.
The required workflow reads third-party crate and npm package contents (archive files, license texts, manifests) that the agent fetches from public registries, which outsiders can publish to but cannot force into the workflow.
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.
The Rune reference's explicit setup step clones the `ruvnet/rune` GitHub repository and builds its code, which is then executed as the trusted `rune` binary; this repository is individual-owned, so it is unofficial, and the pinned commit with HEAD and lock checks is a configuration-dependent control rather than an independent signature, yielding medium.
ruvnet/ruv-FANN
2fce9b7
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.