[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M787WAFXM4R6683F3Y0NF4P4":3,"skill-same:01M787WAFXM4R6683F3Y0NF4P4":88},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":14,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M787WAFXM4R6683F3Y0NF4P4","jetson-package",null,"Pick Jetson-compatible containers, vLLM runtime images, and Jetson AI Lab PyPI indexes; maps Orin SM 8.7 vs Thor SM 11.0 and JetPack-specific package choices.","Solizardking\u002Ftrain2earn","Solizardking","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F108096810?v=4","01M786KDB10AYV042N0F9BD5B5","Clawd","01M786KDC5C3NPE4W44C5641EZ",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-package\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: jetson-package\ndescription: Pick Jetson-compatible containers, vLLM runtime images, and Jetson AI Lab PyPI indexes; maps Orin SM 8.7 vs Thor SM 11.0 and JetPack-specific package choices.\nversion: 0.0.1\nlicense: \"Apache-2.0\"\nmetadata:\n  author: \"Jetson Team\"\n  tags: [jetson, package, containers]\n  languages: [bash]\n  data-classification: public\n---\n\n# Jetson Package & Environment\n\nAgents often suggest `docker pull` images or `pip install` wheels that claim **aarch64** support but were never built for Jetson’s GPU **streaming multiprocessor (SM)** targets. On Jetson, **default to NVIDIA-curated artifacts** unless the user explicitly opts out.\n\n## Purpose\n\nChoose Jetson-compatible containers and Python package indexes before installing GPU-native ML stacks. This skill prevents agents from recommending generic ARM wheels or stale container tags that do not include the right CUDA, JetPack, or SM target for the device.\n\n## When to use\n\n- \"Which Docker image \u002F container should I use on this Jetson?\"\n- \"Where do I get PyTorch \u002F vLLM \u002F CUDA wheels for Jetson?\"\n- \"`pip install` failed\" or \"wrong CUDA \u002F SM\" after installing a generic ARM wheel.\n- Before `docker run` or `pip install` for ML stacks on Orin or Thor.\n- User or agent looks for `l4t-cuda` containers on NGC — redirect to `nvcr.io\u002Fnvidia\u002Fcuda` (multi-arch).\n- \"Which PyTorch container should I use on Jetson?\" — answer depends on Thor vs Orin and JetPack version.\n\n## Canonical sources (use these first)\n\n1. **Prebuilt containers (GHCR)** — [NVIDIA-AI-IOT packages](https:\u002F\u002Fgithub.com\u002Forgs\u002FNVIDIA-AI-IOT\u002Fpackages): `llama_cpp`, `ollama`, `live-vlm-webui`, older-Orin `vllm`, and related images built for Jetson JetPack stacks. Prefer these over random `arm64` images on Docker Hub. For vLLM, use upstream `vllm\u002Fvllm-openai` on Thor and Orin JetPack 7.2 \u002F L4T r39+.\n2. **NGC CUDA \u002F PyTorch containers** — Tag selection depends on Jetson generation. Do not treat example PyTorch tag shapes as pinned recommendations; look up the current tag in the [NGC PyTorch catalog](https:\u002F\u002Fcatalog.ngc.nvidia.com\u002Forgs\u002Fnvidia\u002Fcontainers\u002Fpytorch) before giving a command.\n\n   | Jetson | CUDA base | PyTorch |\n   |--------|-----------|---------|\n   | **Thor** | `nvcr.io\u002Fnvidia\u002Fcuda:\u003Cver>-devel-ubuntu\u003Cver>` (multi-arch, arm64 included) | `nvcr.io\u002Fnvidia\u002Fpytorch:\u003Ccurrent-tag>-py3` (main multi-arch tag; verify current NGC tag) |\n   | **Orin + r36 \u002F JetPack 6** | same multi-arch CUDA base | `nvcr.io\u002Fnvidia\u002Fpytorch:\u003Ccurrent-tag>-py3-igpu` — verify the current NGC tag and use the `-igpu` suffix for Orin iGPU (SM 8.7) when NGC publishes it |\n   | **Orin + r39+ (future)** | same | likely main multi-arch tag once Orin becomes SBSA; verify when r39 ships |\n\n**`l4t-cuda` is the legacy Orin-era CUDA container line.** If a user cannot find `l4t-cuda` on NGC, redirect them to the current multi-arch `nvcr.io\u002Fnvidia\u002Fcuda` image instead of third-party images.\n3. **Python package indexes (devpi)** — [Jetson AI Lab PyPI](https:\u002F\u002Fpypi.jetson-ai-lab.io\u002F): browse the tree (for example `jp6\u002Fcu126`, `jp6\u002Fcu128`) and pick the index that matches your **JetPack \u002F CUDA userland**. Prefer these over PyPI-only wheels for GPU-native stacks.\n\n## GPU architecture reminder (why generic ARM fails)\n\n| Jetson family | CUDA compute capability | Build target | Note |\n|---------------|-------------------------|--------------|------|\n| Orin (AGX \u002F NX \u002F Nano) | **8.7** | `sm_87` | Many desktop `aarch64` wheels omit Jetson Orin kernels. |\n| Thor (T5000 \u002F T4000) | **11.0** | `sm_110` | Requires CUDA \u002F wheels \u002F containers that include Blackwell Jetson support. |\n\nA wheel or container may install on **ARM64 Linux** and still be **unusable or slow** if CUDA kernels were not compiled for your Jetson’s SM.\n\nUse CUDA build target names when discussing wheel compatibility: `sm_87` for Jetson Orin and `sm_110` for Jetson Thor. Do not infer the generation from a prompt or a hostname — run `scripts\u002Fartifact_hints.sh` and use its detected `generation`, `variant`, `l4t`, and `cuda_sm_hint` fields before recommending wheels or container tags.\n\n## GPU Python wheels on Jetson\n\nDefault PyPI wheels for GPU-native packages are usually not the right answer on Jetson, even when they claim `aarch64` support. For `onnxruntime-gpu`, PyTorch, vLLM, and similar packages, use the Jetson AI Lab package index as the canonical source and choose the subtree that matches the device's JetPack \u002F CUDA userland.\n\nFor `onnxruntime-gpu`, lead with Jetson AI Lab rather than plain PyPI:\n\n```bash\npip install --extra-index-url https:\u002F\u002Fpypi.jetson-ai-lab.io\u002Fjp6\u002Fcu126\u002F+simple\u002F onnxruntime-gpu\n```\n\nAdjust the `jp6\u002Fcu126` portion to match the detected JetPack \u002F CUDA line. Do not present `pip install onnxruntime-gpu` from default PyPI as an equivalent Jetson GPU option.\n\n## Do not fabricate device facts\n\nDo not invent SKU names, RAM sizes, JetPack versions, CUDA versions, or GPU SM targets. Quote only what `scripts\u002Fartifact_hints.sh` or the user's supplied environment reports. If a field is unavailable, omit it or say it is unknown.\n\n## Prerequisites\n\n- Run package-detection scripts on a Jetson target, not on the host workstation.\n- Network access is needed to inspect GHCR, NGC, or Jetson AI Lab package indexes.\n- Source device facts from `scripts\u002Fartifact_hints.sh`, `jetson-diagnostic`, or user-provided environment output before recommending tags or wheels.\n\n## Available Scripts\n\n| Script | Purpose | Arguments |\n|--------|---------|-----------|\n| `scripts\u002Fartifact_hints.sh` | Emits detected Jetson SKU\u002Fgeneration, CUDA SM hint, canonical package URLs, and a preferred vLLM image hint. | `--human` for a readable summary; no argument for JSON. |\n\nIf your agent runtime supports `run_script`, use it to run `scripts\u002Fartifact_hints.sh` and read the JSON output. Otherwise run the script with `bash` from the repository root.\n\n## Instructions\n\n1. Run `scripts\u002Fartifact_hints.sh` (JSON on stdout). It sources `skills\u002Fjetson-diagnostic\u002Fscripts\u002Fdetect_jetson.sh` and returns `sku`, `generation`, `product_line`, `variant`, `l4t`, a preferred **vLLM** image, `cuda_sm_hint`, and canonical URLs.\n2. For **pip**, open the devpi root in a browser, pick the **jp6** subtree that matches your CUDA line, and set `--extra-index-url` \u002F `PIP_EXTRA_INDEX_URL` — see `references\u002Fpypi-jetson-ai-lab.md`.\n3. For **containers**, see `references\u002Fghcr-images.md` and `jetson-llm-serve` for vLLM.\n\n## Limitations\n\n- This skill points to package catalogs and emits compatibility hints; it does not verify that a specific model checkpoint fits in memory.\n- NGC and GHCR tags change. Treat placeholder tag shapes such as `\u003Ccurrent-tag>-py3` as lookup instructions, not literal tags.\n- If `generation` or `cuda_sm_hint` is unknown, do not guess a container tag.\n\n## Hand off to\n\n- `jetson-llm-serve` — run upstream\u002Fnative vLLM 0.20+ on Thor and Orin JetPack 7.2 \u002F L4T r39+, or `vllm:latest-jetson-orin` on older Orin.\n- `jetson-llm-benchmark` — measure after the stack is installed.\n- `jetson-diagnostic` — if installs succeed but runtime fails, snapshot first.\n\n## Safety\n\nRead-only: points to catalogs and emits hints; does not install or pull.\n\n## Sources\n\n[NVIDIA-AI-IOT GitHub Packages](https:\u002F\u002Fgithub.com\u002Forgs\u002FNVIDIA-AI-IOT\u002Fpackages), [pypi.jetson-ai-lab.io](https:\u002F\u002Fpypi.jetson-ai-lab.io\u002F).\n","# Jetson Package & Environment\n\nAgents often suggest `docker pull` images or `pip install` wheels that claim **aarch64** support but were never built for Jetson’s GPU **streaming multiprocessor (SM)** targets. On Jetson, **default to NVIDIA-curated artifacts** unless the user explicitly opts out.\n\n## Purpose\n\nChoose Jetson-compatible containers and Python package indexes before installing GPU-native ML stacks. This skill prevents agents from recommending generic ARM wheels or stale container tags that do not include the right CUDA, JetPack, or SM target for the device.\n\n## When to use\n\n- \"Which Docker image \u002F container should I use on this Jetson?\"\n- \"Where do I get PyTorch \u002F vLLM \u002F CUDA wheels for Jetson?\"\n- \"`pip install` failed\" or \"wrong CUDA \u002F SM\" after installing a generic ARM wheel.\n- Before `docker run` or `pip install` for ML stacks on Orin or Thor.\n- User or agent looks for `l4t-cuda` containers on NGC — redirect to `nvcr.io\u002Fnvidia\u002Fcuda` (multi-arch).\n- \"Which PyTorch container should I use on Jetson?\" — answer depends on Thor vs Orin and JetPack version.\n\n## Canonical sources (use these first)\n\n1. **Prebuilt containers (GHCR)** — [NVIDIA-AI-IOT packages](https:\u002F\u002Fgithub.com\u002Forgs\u002FNVIDIA-AI-IOT\u002Fpackages): `llama_cpp`, `ollama`, `live-vlm-webui`, older-Orin `vllm`, and related images built for Jetson JetPack stacks. Prefer these over random `arm64` images on Docker Hub. For vLLM, use upstream `vllm\u002Fvllm-openai` on Thor and Orin JetPack 7.2 \u002F L4T r39+.\n2. **NGC CUDA \u002F PyTorch containers** — Tag selection depends on Jetson generation. Do not treat example PyTorch tag shapes as pinned recommendations; look up the current tag in the [NGC PyTorch catalog](https:\u002F\u002Fcatalog.ngc.nvidia.com\u002Forgs\u002Fnvidia\u002Fcontainers\u002Fpytorch) before giving a command.\n\n   | Jetson | CUDA base | PyTorch |\n   |--------|-----------|---------|\n   | **Thor** | `nvcr.io\u002Fnvidia\u002Fcuda:\u003Cver>-devel-ubuntu\u003Cver>` (multi-arch, arm64 included) | `nvcr.io\u002Fnvidia\u002Fpytorch:\u003Ccurrent-tag>-py3` (main multi-arch tag; verify current NGC tag) |\n   | **Orin + r36 \u002F JetPack 6** | same multi-arch CUDA base | `nvcr.io\u002Fnvidia\u002Fpytorch:\u003Ccurrent-tag>-py3-igpu` — verify the current NGC tag and use the `-igpu` suffix for Orin iGPU (SM 8.7) when NGC publishes it |\n   | **Orin + r39+ (future)** | same | likely main multi-arch tag once Orin becomes SBSA; verify when r39 ships |\n\n**`l4t-cuda` is the legacy Orin-era CUDA container line.** If a user cannot find `l4t-cuda` on NGC, redirect them to the current multi-arch `nvcr.io\u002Fnvidia\u002Fcuda` image instead of third-party images.\n3. **Python package indexes (devpi)** — [Jetson AI Lab PyPI](https:\u002F\u002Fpypi.jetson-ai-lab.io\u002F): browse the tree (for example `jp6\u002Fcu126`, `jp6\u002Fcu128`) and pick the index that matches your **JetPack \u002F CUDA userland**. Prefer these over PyPI-only wheels for GPU-native stacks.\n\n## GPU architecture reminder (why generic ARM fails)\n\n| Jetson family | CUDA compute capability | Build target | Note |\n|---------------|-------------------------|--------------|------|\n| Orin (AGX \u002F NX \u002F Nano) | **8.7** | `sm_87` | Many desktop `aarch64` wheels omit Jetson Orin kernels. |\n| Thor (T5000 \u002F T4000) | **11.0** | `sm_110` | Requires CUDA \u002F wheels \u002F containers that include Blackwell Jetson support. |\n\nA wheel or container may install on **ARM64 Linux** and still be **unusable or slow** if CUDA kernels were not compiled for your Jetson’s SM.\n\nUse CUDA build target names when discussing wheel compatibility: `sm_87` for Jetson Orin and `sm_110` for Jetson Thor. Do not infer the generation from a prompt or a hostname — run `scripts\u002Fartifact_hints.sh` and use its detected `generation`, `variant`, `l4t`, and `cuda_sm_hint` fields before recommending wheels or container tags.\n\n## GPU Python wheels on Jetson\n\nDefault PyPI wheels for GPU-native packages are usually not the right answer on Jetson, even when they claim `aarch64` support. For `onnxruntime-gpu`, PyTorch, vLLM, and similar packages, use the Jetson AI Lab package index as the canonical source and choose the subtree that matches the device's JetPack \u002F CUDA userland.\n\nFor `onnxruntime-gpu`, lead with Jetson AI Lab rather than plain PyPI:\n\n```bash\npip install --extra-index-url https:\u002F\u002Fpypi.jetson-ai-lab.io\u002Fjp6\u002Fcu126\u002F+simple\u002F onnxruntime-gpu\n```\n\nAdjust the `jp6\u002Fcu126` portion to match the detected JetPack \u002F CUDA line. Do not present `pip install onnxruntime-gpu` from default PyPI as an equivalent Jetson GPU option.\n\n## Do not fabricate device facts\n\nDo not invent SKU names, RAM sizes, JetPack versions, CUDA versions, or GPU SM targets. Quote only what `scripts\u002Fartifact_hints.sh` or the user's supplied environment reports. If a field is unavailable, omit it or say it is unknown.\n\n## Prerequisites\n\n- Run package-detection scripts on a Jetson target, not on the host workstation.\n- Network access is needed to inspect GHCR, NGC, or Jetson AI Lab package indexes.\n- Source device facts from `scripts\u002Fartifact_hints.sh`, `jetson-diagnostic`, or user-provided environment output before recommending tags or wheels.\n\n## Available Scripts\n\n| Script | Purpose | Arguments |\n|--------|---------|-----------|\n| `scripts\u002Fartifact_hints.sh` | Emits detected Jetson SKU\u002Fgeneration, CUDA SM hint, canonical package URLs, and a preferred vLLM image hint. | `--human` for a readable summary; no argument for JSON. |\n\nIf your agent runtime supports `run_script`, use it to run `scripts\u002Fartifact_hints.sh` and read the JSON output. Otherwise run the script with `bash` from the repository root.\n\n## Instructions\n\n1. Run `scripts\u002Fartifact_hints.sh` (JSON on stdout). It sources `skills\u002Fjetson-diagnostic\u002Fscripts\u002Fdetect_jetson.sh` and returns `sku`, `generation`, `product_line`, `variant`, `l4t`, a preferred **vLLM** image, `cuda_sm_hint`, and canonical URLs.\n2. For **pip**, open the devpi root in a browser, pick the **jp6** subtree that matches your CUDA line, and set `--extra-index-url` \u002F `PIP_EXTRA_INDEX_URL` — see `references\u002Fpypi-jetson-ai-lab.md`.\n3. For **containers**, see `references\u002Fghcr-images.md` and `jetson-llm-serve` for vLLM.\n\n## Limitations\n\n- This skill points to package catalogs and emits compatibility hints; it does not verify that a specific model checkpoint fits in memory.\n- NGC and GHCR tags change. Treat placeholder tag shapes such as `\u003Ccurrent-tag>-py3` as lookup instructions, not literal tags.\n- If `generation` or `cuda_sm_hint` is unknown, do not guess a container tag.\n\n## Hand off to\n\n- `jetson-llm-serve` — run upstream\u002Fnative vLLM 0.20+ on Thor and Orin JetPack 7.2 \u002F L4T r39+, or `vllm:latest-jetson-orin` on older Orin.\n- `jetson-llm-benchmark` — measure after the stack is installed.\n- `jetson-diagnostic` — if installs succeed but runtime fails, snapshot first.\n\n## Safety\n\nRead-only: points to catalogs and emits hints; does not install or pull.\n\n## Sources\n\n[NVIDIA-AI-IOT GitHub Packages](https:\u002F\u002Fgithub.com\u002Forgs\u002FNVIDIA-AI-IOT\u002Fpackages), [pypi.jetson-ai-lab.io](https:\u002F\u002Fpypi.jetson-ai-lab.io\u002F).\n",{"name":5,"license":15,"version":24,"metadata":25,"description":7},"0.0.1",{"tags":26,"author":30,"languages":31,"data-classification":33},[27,28,29],"jetson","package","containers","Jetson Team",[32],"bash","public","main","86cc27ffd16af6cb85948f1155578e6f3f61cc4c","skillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-package","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn","https:\u002F\u002Fgithub.com\u002FSolizardking","https:\u002F\u002Fmusebook.trade","Got a mile high and never came down","2026-10-08 11:52:53",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add Solizardking\u002Ftrain2earn --skill jetson-package",{"tool":48,"command":49},"bunx","bunx skills add Solizardking\u002Ftrain2earn --skill jetson-package",{"tool":51,"command":52},"pnpm","pnpm dlx skills add Solizardking\u002Ftrain2earn --skill jetson-package","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-package\u002FSKILL.md",true,[56,62,66,70,74,80,84],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"BENCHMARK.md","REFERENCE","参考文档",3302,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-package\u002FBENCHMARK.md",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"metadata.json",350,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-package\u002Fmetadata.json",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fghcr-images.md",1027,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-package\u002Freferences\u002Fghcr-images.md",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fpypi-jetson-ai-lab.md",943,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-package\u002Freferences\u002Fpypi-jetson-ai-lab.md",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002Fartifact_hints.sh","SCRIPT","脚本",3392,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-package\u002Fscripts\u002Fartifact_hints.sh",{"path":81,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":82,"sourceHtmlUrl":83},"skill-card.md",3973,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-package\u002Fskill-card.md",{"path":85,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":86,"sourceHtmlUrl":87},"verification.json",1839,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-package\u002Fverification.json",[89,97,105,113,120,128],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M78B94RSCAKMH1QS79VE6DG9","testing","For testing with Light Protocol programs and clients on localnet, devnet, and mainnet validation.","MIT","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Ftesting\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M78B81BKY8RX12HETPG8YKWK","qedgen","Formally verify programs by writing Lean 4 proofs. Trigger this skill whenever the user wants to formally verify code, generate Lean 4 proofs, prove properties about algorithms or smart contracts, verify invariants, convert program logic into formal specifications, or anything involving Lean 4 and formal verification. Also trigger when the user mentions \"qedgen\", \"lean proof\", \"formal proof\", \"verify my code\", \"prove correctness\", \"formal verification\", or wants mathematical guarantees about their implementation.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-formal-verification\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-formal-verification\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M78B7Q7C5K54E01DN83A60KG","solana-dev","Use when user asks to \"build a Solana dapp\", \"write an Anchor program\", \"create a token\", \"debug Solana errors\", \"set up wallet connection\", \"test my Solana program\", \"deploy to devnet\", or \"explain Solana concepts\" (rent, accounts, PDAs, CPIs, etc.). Also use for quick on-chain lookups via public RPC + curl — \"what's the balance of \u003Cwallet>\", \"look up transaction \u003Csig>\", \"token balance for \u003Caccount>\", \"check this address on mainnet\u002Fdevnet\". End-to-end Solana development playbook covering wallet connection, Anchor\u002FPinocchio programs, Codama client generation, LiteSVM\u002FMollusk\u002FSurfpool testing, security checklists, and JSON-RPC curl lookups against public clusters. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana\u002Fclient + @solana\u002Freact-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana\u002Fkit for client\u002FRPC code, and @solana\u002Fweb3-compat for legacy boundaries.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-dev\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-dev\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M78B7HXD6N6GWKSVRQ8F6Q31","solana-common-errors","Diagnose and fix common Solana development errors — GLIBC mismatches, Anchor version conflicts, cargo build-sbf \u002F platform-tools failures, LiteSVM issues, edition2024 crate pins, RPC airdrops, and Anchor 0.29→0.32 migrations. Use when builds fail, Anchor CLI won't install, or CI breaks on Debian\u002FUbuntu.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-common-errors\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M78B6T7YSYWQ0N4DP40QDXEZ","skill-creator","Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":19},"01M78B1VFT9X5AND7AE1HZPZGF","phantom-wallet-mcp","Execute wallet operations through the Phantom MCP server. Use when the user wants to interact with their Phantom wallet directly — get addresses, transfer SOL or SPL tokens, buy\u002Fswap tokens, sign transactions, and sign messages across Solana, Ethereum, Bitcoin, and Sui. Requires the @phantom\u002Fmcp-server to be configured as an MCP server.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fphantom-wallet-mcp\u002FSKILL.md",[],[]]