[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AC3DHE64VHDK2G9K3VZP0B":3,"skill-same:01M7AC3DHE64VHDK2G9K3VZP0B":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AC3DHE64VHDK2G9K3VZP0B","validate-skills",null,"Validates skills in this repo against agentskills.io spec and Claude Code best practices. Use via \u002Fvalidate-skills command.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"MIT","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvalidate-skills\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Validates skills in this repo against agentskills.io spec and Claude Code best practices. Use via \u002Fvalidate-skills command.\"\nlicense: \"MIT\"\nmetadata: {\"author\":\"Callstack\",\"tags\":\"validation, linting, skill-authoring\"}\n---\n# Validate Skills\n\nValidate all skills in `skills\u002F` against the agentskills.io spec and Claude Code best practices.\n\n## Validation Checklist\n\nFor each skill directory, verify:\n\n### Spec Compliance (agentskills.io)\n\n| Check | Rule |\n|-------|------|\n| `name` format | 1-64 chars, lowercase alphanumeric + hyphens, no leading\u002Ftrailing\u002Fconsecutive hyphens |\n| `name` matches directory | Directory name must equal `name` field |\n| `description` length | 1-1024 characters, non-empty |\n| Optional fields valid | `license`, `metadata`, `compatibility` if present |\n\n### Best Practices (Claude Code)\n\n| Check | Rule |\n|-------|------|\n| Description format | Third person, describes what + when to use |\n| Body length | Under 500 lines |\n| Loading is one-level deep | `SKILL.md` is the only progressive-disclosure entry point: every reference file must be reachable from `SKILL.md`. References may cross-link each other for navigation (see note below). |\n| Links are markdown | Use `[text](path)` not bare filenames |\n| No redundancy | Don't repeat description in body |\n| Concise | Only add context Claude doesn't already have |\n\n> **One-level-deep vs. cross-linking.** The one-level-deep rule targets *progressive-disclosure loading chains* — a reference that can only be discovered by loading another reference first (`SKILL.md` → `a.md` → `b.md`, where `b.md` is not linked from `SKILL.md`). That is a defect: it hides content from the loader.\n>\n> It does **not** forbid *navigational* cross-links. Per [AGENTS.md](..\u002F..\u002F..\u002FAGENTS.md), reference files end with a \"Related Skills\" footer linking sibling references, and this is required. A cross-link is fine as long as both endpoints are also reachable directly from `SKILL.md`. Only flag a reference that is reachable *exclusively* through another reference.\n\n## How to Run\n\n1. Find all skill directories:\n   ```bash\n   fd -t d -d 1 . skills\u002F\n   ```\n\n2. For each skill, read `SKILL.md` and check against the rules above\n\n3. Report issues in this format:\n   ```\n   ## Validation Results\n\n   ### skills\u002Fexample-skill\n   - [PASS] name format valid\n   - [FAIL] name \"example\" doesn't match directory \"example-skill\"\n   - [PASS] description length OK (156 chars)\n   ```\n\n## References\n\n- [agentskills.io spec](https:\u002F\u002Fagentskills.io\u002Fspecification)\n- [Claude Code best practices](https:\u002F\u002Fplatform.claude.com\u002Fdocs\u002Fen\u002Fagents-and-tools\u002Fagent-skills\u002Fbest-practices)\n","# Validate Skills\n\nValidate all skills in `skills\u002F` against the agentskills.io spec and Claude Code best practices.\n\n## Validation Checklist\n\nFor each skill directory, verify:\n\n### Spec Compliance (agentskills.io)\n\n| Check | Rule |\n|-------|------|\n| `name` format | 1-64 chars, lowercase alphanumeric + hyphens, no leading\u002Ftrailing\u002Fconsecutive hyphens |\n| `name` matches directory | Directory name must equal `name` field |\n| `description` length | 1-1024 characters, non-empty |\n| Optional fields valid | `license`, `metadata`, `compatibility` if present |\n\n### Best Practices (Claude Code)\n\n| Check | Rule |\n|-------|------|\n| Description format | Third person, describes what + when to use |\n| Body length | Under 500 lines |\n| Loading is one-level deep | `SKILL.md` is the only progressive-disclosure entry point: every reference file must be reachable from `SKILL.md`. References may cross-link each other for navigation (see note below). |\n| Links are markdown | Use `[text](path)` not bare filenames |\n| No redundancy | Don't repeat description in body |\n| Concise | Only add context Claude doesn't already have |\n\n> **One-level-deep vs. cross-linking.** The one-level-deep rule targets *progressive-disclosure loading chains* — a reference that can only be discovered by loading another reference first (`SKILL.md` → `a.md` → `b.md`, where `b.md` is not linked from `SKILL.md`). That is a defect: it hides content from the loader.\n>\n> It does **not** forbid *navigational* cross-links. Per [AGENTS.md](..\u002F..\u002F..\u002FAGENTS.md), reference files end with a \"Related Skills\" footer linking sibling references, and this is required. A cross-link is fine as long as both endpoints are also reachable directly from `SKILL.md`. Only flag a reference that is reachable *exclusively* through another reference.\n\n## How to Run\n\n1. Find all skill directories:\n   ```bash\n   fd -t d -d 1 . skills\u002F\n   ```\n\n2. For each skill, read `SKILL.md` and check against the rules above\n\n3. Report issues in this format:\n   ```\n   ## Validation Results\n\n   ### skills\u002Fexample-skill\n   - [PASS] name format valid\n   - [FAIL] name \"example\" doesn't match directory \"example-skill\"\n   - [PASS] description length OK (156 chars)\n   ```\n\n## References\n\n- [agentskills.io spec](https:\u002F\u002Fagentskills.io\u002Fspecification)\n- [Claude Code best practices](https:\u002F\u002Fplatform.claude.com\u002Fdocs\u002Fen\u002Fagents-and-tools\u002Fagent-skills\u002Fbest-practices)\n",{"license":15,"metadata":24,"description":7},{"tags":25,"author":26},"validation, linting, skill-authoring","Callstack","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fvalidate-skills","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add NeelakshSaxena\u002FVayu --skill validate-skills",{"tool":40,"command":41},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill validate-skills",{"tool":43,"command":44},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill validate-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvalidate-skills\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]