Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
nft-standards
nft-standards is an open-source integrations skill for Claude Code and compatible agents, published by wshobson. Its author describes it as: “Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset sys…”. The project has 39k stars on GitHub and is available under the MIT license. Add it to your setup with `/plugin marketplace add wshobson/agents`.
What nft-standards does
Master ERC-721 and ERC-1155 NFT standards, metadata best practices, and advanced NFT features.
Installation
Add nft-standards to your agent with:
/plugin marketplace add wshobson/agents Always review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for nft-standards is organised into these sections:
- When to Use This Skill
- ERC-721 (Non-Fungible Token Standard)
- ERC-1155 (Multi-Token Standard)
- Metadata Standards
- Off-Chain Metadata (IPFS)
- On-Chain Metadata
- Royalties (EIP-2981)
- Additional patterns and templates
When to use it
Reach for nft-standards when you want integrations help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear MIT license — safe to read and adapt
- Ships in wshobson/agents, an established project with 38,890 GitHub stars
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does nft-standards do?
- Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
- How do I install nft-standards?
- Run /plugin marketplace add wshobson/agents in your agent, then reload your skills. Review the source at https://github.com/wshobson/agents before installing.
- Is nft-standards free to use?
- Yes. nft-standards is free and open source under the MIT license, so you can read, run, and adapt it within that license's terms.
- Where does nft-standards come from?
- nft-standards ships inside wshobson/agents, a repository that contains 54 catalogued skills in total. The repository's 38,890 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Integrations →Loop engineering for AI coding agents — turn ad-hoc sessions into a repeatable research → plan → wave-execute → close loop with verification gates. Runs on Claude Code, Codex CLI, Cursor, and Pi. MIT community plugin.
A curated marketplace of plugins for Claude Code, built from first principles.
Manage context-mode GitHub issues, PRs, releases, and marketing with parallel subagent army. Orchestrates 10-20 dynamic agents per task. Use when triaging issues, reviewing PRs, releasing versions, writing LinkedIn posts, announcing releases, fixing bugs, merging contributions, validating ENV vars, testing adapters, or syncing branches.
Use context-mode tools (ctx_execute, ctx_execute_file) instead of Bash/cat when processing large outputs. Triggers: "analyze logs", "summarize output", "process data", "parse JSON", "filter results", "extract errors", "check build output", "analyze dependencies", "process API response", "large file analysis", "page snapshot", "browser snapshot", "DOM structure", "inspect page", "accessibility tree", "Playwright snapshot", "run tests", "test output", "coverage report", "git log", "recent commits", "diff between branches", "list containers", "pod status", "disk usage", "fetch docs", "API reference", "index documentation", "call API", "check response", "query results", "find TODOs", "count lines", "codebase statistics", "security audit", "outdated packages", "dependency tree", "cloud resources", "CI/CD output". Also triggers on ANY MCP tool output that may exceed 20 lines. Subagent routing is handled automatically via PreToolUse hook.