All categories
Tools & Automation
CLI tools, utilities, converters, workflow automation, and productivity helpers
- 45,575
- 1,899
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse tools & automation skills
Showing 481–504 of 45,575 skills
- Weft UpdatingRead when the user asks to update or upgrade weft, or when something broke right after one: locating the checkout, the git pull plus setup.sh walk, what setup.sh rebuilds and what it preserves, and fixing a failed update.Votes: 0GitHub stars: 1,992
- DeployerThe only agent that acts on a cloud install. Dispatched by Tangle with what to do on a named target (deploy, roll back, set up CI, read a failed cloud build); names the target with --on on every command, reads the weft-deploying skill, and reports the deployed version and route addresses, or the exact failure.Votes: 0GitHub stars: 1,992
- Weft UpdatingRead when the user asks to update or upgrade weft, or when something broke right after one: locating the checkout, the git pull plus setup.sh walk, what setup.sh rebuilds and what it preserves, and fixing a failed update.Votes: 0GitHub stars: 1,992
- Weft UpdatingRead when the user asks to update or upgrade weft, or when something broke right after one: locating the checkout, the git pull plus setup.sh walk, what setup.sh rebuilds and what it preserves, and fixing a failed update.Votes: 0GitHub stars: 1,992
- Weft Live TestCOMMAND, not reference: Walk the user through setting up and running a node's live test. Run this when the user asks for this step by name, optionally naming the node type or package name. The seventeen `weft-` reference skills beside it are things you read; this is a procedure you carry out.Votes: 0GitHub stars: 1,992
- Weft CheckCOMMAND, not reference: Validate and build the weft program, fix diagnostics until clean. Run this when the user asks for this step by name. The seventeen `weft-` reference skills beside it are things you read; this is a procedure you carry out.Votes: 0GitHub stars: 1,992
- DeployerThe only agent that acts on a cloud install. Dispatched by Tangle with what to do on a named target (deploy, roll back, set up CI, read a failed cloud build); names the target with --on on every command, reads the weft-deploying skill, and reports the deployed version and route addresses, or the exact failure.Votes: 0GitHub stars: 1,992
- Weft UpdatingRead when the user asks to update or upgrade weft, or when something broke right after one: locating the checkout, the git pull plus setup.sh walk, what setup.sh rebuilds and what it preserves, and fixing a failed update.Votes: 0GitHub stars: 1,992
- Weft CatalogRead before picking nodes for a job: the three reads that find a node and tell you how it wires, the metadata vocabulary you will meet there, the wiring shapes that recur (a connection, a provider, infrastructure, ports that come from a list), where a project's own nodes live, and what to do when nothing in the catalog fits.Votes: 0GitHub stars: 1,992
- Nano Add Event HandlerAdd an event handler to a Nano application - a class deriving BaseEventHandler<TEvent> that subscribes to messages published via IEventing.PublishAsync. Use when the user asks to add an event handler, subscriber, or consumer for Nano's Publish/Subscribe eventing to a Nano API, Web, or Console application. Not for Entity Events (automatic per-entity-save publishing, which needs no handler at all) - see AGENTS.md's Entity Events section for that.Votes: 0GitHub stars: 5
- Openspec Verify ChangeVerify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving. Also use when the user says "openspec verify" or "opsx verify".Votes: 0GitHub stars: 2
- Openspec Sync SpecsSync delta specs from an OpenSpec change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change. Also use when the user says "openspec sync" or "opsx sync".Votes: 0GitHub stars: 2
- Openspec ProposePropose a new OpenSpec change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation. Also use when the user says "openspec propose" or "opsx propose".Votes: 0GitHub stars: 2
- Openspec Ff ChangeFast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually. Also use when the user says "openspec ff" or "opsx ff".Votes: 0GitHub stars: 2
- Openspec Continue ChangeContinue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow. Also use when the user says "openspec continue" or "opsx continue".Votes: 0GitHub stars: 2
- Openspec Verify ChangeVerify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving. Also use when the user says "openspec verify" or "opsx verify".Votes: 0GitHub stars: 2
- Openspec Sync SpecsSync delta specs from an OpenSpec change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change. Also use when the user says "openspec sync" or "opsx sync".Votes: 0GitHub stars: 2
- Openspec ProposePropose a new OpenSpec change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation. Also use when the user says "openspec propose" or "opsx propose".Votes: 0GitHub stars: 2
- Openspec Ff ChangeFast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually. Also use when the user says "openspec ff" or "opsx ff".Votes: 0GitHub stars: 2
- Openspec Continue ChangeContinue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow. Also use when the user says "openspec continue" or "opsx continue".Votes: 0GitHub stars: 2
- Self ReviewUse when finishing spec.md before writing test-definitions.md, orVotes: 0GitHub stars: 19
- LintRun linters and formatters to fix code style issues. Use whenVotes: 0GitHub stars: 19
- DdThis skill should be used when the user runs /dd or /ㅇㅇ to act on the current OS clipboard (text or image) without pasting it into chat. It captures the live clipboard into a local cache and uses only the manifest plus a short preview as context, so error logs and reference images do not bloat the conversation. Korean triggers: "/dd", "/ㅇㅇ", "클립보드 보내줘", "이거 분석해줘", "방금 캡처한 거", "이 레퍼런스로", "스크린샷 드롭". English triggers: "/dd", "drop clipboard", "use what I copied", "this screenshot", "this referen...Votes: 0GitHub stars: 66
- Bash ToolsProper usage of Bash and file operation tools. Use this skill when executing shell commands, writing files, or when tempted to use echo/cat/heredoc to pipe content to files. Prevents permission circumvention patterns like piping multiline content through echo instead of using Write tool. Covers Bash tool, Write tool, Edit tool, and Read tool best practices.Votes: 0GitHub stars: 15