npm registry ops: login, whoami, names, publish; 1Password tmux.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
The skill manages npm package publishing and registry operations via `publish-package.sh` and `reserve-packages.sh`. This is an indirect financial operation (publishing packages / reserving names on a package registry that may involve paid features or public namespace claims, but does not move direct money or charge cards). Under the evaluation framework, indirect financial operations map to medium severity.
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 workflow publishes packages and reads registry metadata (such as package version/status via npm view and access get status), which can ingest outsider-authored package metadata and registry responses containing free text.
steipete/agent-scripts
2f82700
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.