[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M787VCFXAZJZNBMGFPKYCKHM":3,"skill-same:01M787VCFXAZJZNBMGFPKYCKHM":73},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":14,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M787VCFXAZJZNBMGFPKYCKHM","jetson-init-image",null,"Extract Jetson Linux + sample-rootfs tarballs and run apply_binaries.sh for the active target, then record bsp_image in the profile. Use after jetson-init-target; not for source-tree setup.","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-init-image\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: jetson-init-image\ndescription: >-\n  Extract Jetson Linux + sample-rootfs tarballs and run\n  apply_binaries.sh for the active target, then record bsp_image in\n  the profile. Use after jetson-init-target; not for source-tree\n  setup.\nversion: 0.0.1\nlicense: \"Apache-2.0\"\nmetadata:\n  data-classification: public\n  author: \"Jetson Team\"\n  tags:\n    - bsp\n    - image\n    - bootstrap\n  domain: meta\n---\n\n# Initialize BSP Image\n\nOutput is only `bsp_image:` in the active profile: derived `version`\nplus `root_path` only when overriding `\u003Cworkspace>\u002FImage`.\n\n## When to invoke\n\n- The user asks to extract, prepare, or initialize the BSP image.\n- A downstream skill reports missing\n  `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F`.\n- The active profile has no `bsp_image:` block yet.\n\n## Procedure\n\n### Resolve target and image path\n\nResolve the active profile per\n[`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md).\nRefuse if there is no active profile or `reference_devkit:` is missing.\n\n`\u003Cworkspace>` is the parent of the active profile's `target-platform\u002F`\ndirectory. `\u003Cbsp_image.root_path>` defaults to `\u003Cworkspace>\u002FImage`.\n\n| Profile state | Action |\n|---|---|\n| `bsp_image.root_path` exists | Use it without prompting. |\n| `bsp_image:` exists without `root_path` | Use `\u003Cworkspace>\u002FImage`. |\n| No `bsp_image:` block | Ask once: Enter for default, or absolute override path. |\n\nFor an override, validate that the closest existing parent is writable.\nOmit `root_path` when the default is used.\n\n### Determine GPU stack\n\nUse the shared GPU-driver invariant from\n[`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md#derived-platform-facts).\nDerive the expected stack from `reference_devkit.module.id` and the\ncatalogue:\n\n| Chip family | Module IDs | Stack | `apply_binaries.sh` flag |\n|---|---|---|---|\n| T234 \u002F Orin | `p3701`, `p3767` | nvgpu | none |\n| T264 and later \u002F Thor+ | `p3834` | OpenRM | `--openrm` |\n\nRefuse unknown module IDs. The `--openrm` flag is only valid on BSP\nreleases that ship the OpenRM stack; if the active BSP doesn't expose\nthe flag, omit it regardless of what the target wants.\n\n### Reuse or extract\n\nIf `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F` already exists:\n\n1. Do not extract over it unless the user explicitly requested\n   re-extraction and accepted the overwrite risk.\n2. Derive the on-disk version from `Linux_for_Tegra\u002Fnv_tegra_release`.\n   Ask before replacing a different recorded `bsp_image.version`.\n3. Verify the installed GPU stack against the platform-derived\n   expectation when possible. Detection precedence (first probe that\n   yields a definitive answer wins):\n\n   1. `Linux_for_Tegra\u002Frootfs\u002Fetc\u002Fnv_tegra_release` carries an\n      `INSTALL_TYPE=` token on BSP releases that expose it (newer\n      lines). Read and compare directly.\n   2. Otherwise, `find Linux_for_Tegra -name nvgpu.ko`: present →\n      nvgpu, absent → OpenRM.\n   3. If the chip family has only ever shipped one stack (e.g. T234 \u002F\n      Orin is always nvgpu in current BSPs), fall back to the\n      catalogue-derived expectation without disk probing.\n\nIf the installed stack conflicts with the active target, refuse and ask\nthe user to re-extract with the correct stack or fix the target profile.\nOtherwise skip extraction and update the profile.\n\n### Locate tarballs\n\nWhen extraction is needed, search:\n\n1. `\u003Cbsp_image.root_path>\u002F`\n2. `\u003Cworkspace>\u002F`\n3. current working directory\n\nPrompt for absolute paths for anything missing. Required filenames:\n\n- `Jetson_Linux_R\u003Cver>_aarch64.tbz2`\n- `Tegra_Linux_Sample-Root-Filesystem_R\u003Cver>_aarch64.tbz2`\n\nBoth filenames must contain the same `R\u003Cver>` token. Refuse mismatches\nand record `\u003Cver>` as `bsp_image.version`. Do not download tarballs.\n\n### Extract and apply binaries\n\nUse absolute tarball paths; they may live outside\n`\u003Cbsp_image.root_path>`.\n\n```bash\nROOT=\"\u003Cbsp_image.root_path>\"\nBSP_TARBALL=\"\u003Cabsolute path to Jetson_Linux_R\u003Cver>_aarch64.tbz2>\"\nROOTFS_TARBALL=\"\u003Cabsolute path to Tegra_Linux_Sample-Root-Filesystem_R\u003Cver>_aarch64.tbz2>\"\n\nmkdir -p \"$ROOT\"\ntar xjf \"$BSP_TARBALL\" -C \"$ROOT\"\nsudo tar xpjf \"$ROOTFS_TARBALL\" -C \"$ROOT\u002FLinux_for_Tegra\u002Frootfs\"\n\ncd \"$ROOT\u002FLinux_for_Tegra\"\nif [ \"$GPU_STACK\" = \"openrm\" ]; then\n  sudo .\u002Fapply_binaries.sh --openrm\nelse\n  sudo .\u002Fapply_binaries.sh\nfi\n```\n\nSet `GPU_STACK` from the \"Determine GPU stack\" step above. Abort on the first failing command and\nsurface the failed command.\n\n### Update the active profile\n\nPersist the resolved BSP image metadata in the active target profile so\nlater skills can find the BSP without re-prompting. Preserve existing\nblocks, comments, and quoted SKU values; use a round-tripping YAML\nwriter such as `ruamel.yaml`.\n\n```yaml\nbsp_image:\n  root_path: \u003Cabsolute override path>  # omit for \u003Cworkspace>\u002FImage\n  version: \"\u003Cderived version>\"\n```\n\nRules:\n\n- Same version and same root path: no rewrite.\n- Different version: ask before updating.\n- Different recorded `root_path`: refuse automatic rewrite.\n- Always quote `version`.\n\n## Finish\n\nReport the image path, extracted vs reused state, GPU stack, derived\nversion, and profile update status. Then suggest `\u002Fjetson-init-source`.\n\n## Purpose\n\nMaterialize `Linux_for_Tegra\u002F` on disk by extracting the right Jetson\nLinux + sample-rootfs tarballs and running `apply_binaries.sh` with\nthe GPU-stack flag derived from the active target (nvgpu for T234,\nOpenRM for T264+). Then commit the derived BSP version into the\nprofile's `bsp_image:` block.\n\n## Prerequisites\n\n- Active target profile resolved per\n  `..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`.\n- Jetson Linux BSP tarball and matching sample-rootfs tarball staged\n  on disk (e.g. by `\u002Fjetson-download-bsp` or hand-placed).\n- Write access to the workspace `Image\u002F` root (or the override\n  `bsp_image.root_path`).\n- `sudo` available for `apply_binaries.sh`.\n\n## Limitations\n\n- Writes only the `bsp_image:` block; source tree, documents, and\n  carrier profile are owned by sibling skills.\n- Refuses to overwrite an existing `Linux_for_Tegra\u002F` without explicit\n  user direction.\n- Does not download tarballs; rely on `\u002Fjetson-download-bsp` or\n  hand-stage the inputs.\n\n## Troubleshooting\n\n- **`apply_binaries.sh` exits non-zero** — re-read its console output;\n  most failures are missing `sudo`, missing rootfs tarball, or wrong\n  GPU stack flag for the SoC generation.\n- **`nv_tegra_release` absent after extract** — extraction stopped\n  early; verify tarball integrity and rerun.\n- **Recorded `version` disagrees with the tarball filename** — the\n  tarball was renamed; trust the value parsed from\n  `Linux_for_Tegra\u002Fnv_tegra_release` over filenames.\n- **Different recorded `root_path` already in profile** — refuse and\n  ask the user to confirm before overwriting.\n\n## References\n\n- [`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md)\n- [`..\u002F..\u002Freferences\u002Fbsp-platforms-catalogue.md`](..\u002F..\u002Freferences\u002Fbsp-platforms-catalogue.md)\n- [`..\u002F..\u002Freferences\u002Fplatform_template.yaml`](..\u002F..\u002Freferences\u002Fplatform_template.yaml)\n- [`..\u002Fjetson-init-target\u002FSKILL.md`](..\u002Fjetson-init-target\u002FSKILL.md)\n- [`..\u002Fjetson-init-source\u002FSKILL.md`](..\u002Fjetson-init-source\u002FSKILL.md)\n- [`..\u002Fjetson-flash-image\u002FSKILL.md`](..\u002Fjetson-flash-image\u002FSKILL.md)\n","# Initialize BSP Image\n\nOutput is only `bsp_image:` in the active profile: derived `version`\nplus `root_path` only when overriding `\u003Cworkspace>\u002FImage`.\n\n## When to invoke\n\n- The user asks to extract, prepare, or initialize the BSP image.\n- A downstream skill reports missing\n  `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F`.\n- The active profile has no `bsp_image:` block yet.\n\n## Procedure\n\n### Resolve target and image path\n\nResolve the active profile per\n[`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md).\nRefuse if there is no active profile or `reference_devkit:` is missing.\n\n`\u003Cworkspace>` is the parent of the active profile's `target-platform\u002F`\ndirectory. `\u003Cbsp_image.root_path>` defaults to `\u003Cworkspace>\u002FImage`.\n\n| Profile state | Action |\n|---|---|\n| `bsp_image.root_path` exists | Use it without prompting. |\n| `bsp_image:` exists without `root_path` | Use `\u003Cworkspace>\u002FImage`. |\n| No `bsp_image:` block | Ask once: Enter for default, or absolute override path. |\n\nFor an override, validate that the closest existing parent is writable.\nOmit `root_path` when the default is used.\n\n### Determine GPU stack\n\nUse the shared GPU-driver invariant from\n[`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md#derived-platform-facts).\nDerive the expected stack from `reference_devkit.module.id` and the\ncatalogue:\n\n| Chip family | Module IDs | Stack | `apply_binaries.sh` flag |\n|---|---|---|---|\n| T234 \u002F Orin | `p3701`, `p3767` | nvgpu | none |\n| T264 and later \u002F Thor+ | `p3834` | OpenRM | `--openrm` |\n\nRefuse unknown module IDs. The `--openrm` flag is only valid on BSP\nreleases that ship the OpenRM stack; if the active BSP doesn't expose\nthe flag, omit it regardless of what the target wants.\n\n### Reuse or extract\n\nIf `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F` already exists:\n\n1. Do not extract over it unless the user explicitly requested\n   re-extraction and accepted the overwrite risk.\n2. Derive the on-disk version from `Linux_for_Tegra\u002Fnv_tegra_release`.\n   Ask before replacing a different recorded `bsp_image.version`.\n3. Verify the installed GPU stack against the platform-derived\n   expectation when possible. Detection precedence (first probe that\n   yields a definitive answer wins):\n\n   1. `Linux_for_Tegra\u002Frootfs\u002Fetc\u002Fnv_tegra_release` carries an\n      `INSTALL_TYPE=` token on BSP releases that expose it (newer\n      lines). Read and compare directly.\n   2. Otherwise, `find Linux_for_Tegra -name nvgpu.ko`: present →\n      nvgpu, absent → OpenRM.\n   3. If the chip family has only ever shipped one stack (e.g. T234 \u002F\n      Orin is always nvgpu in current BSPs), fall back to the\n      catalogue-derived expectation without disk probing.\n\nIf the installed stack conflicts with the active target, refuse and ask\nthe user to re-extract with the correct stack or fix the target profile.\nOtherwise skip extraction and update the profile.\n\n### Locate tarballs\n\nWhen extraction is needed, search:\n\n1. `\u003Cbsp_image.root_path>\u002F`\n2. `\u003Cworkspace>\u002F`\n3. current working directory\n\nPrompt for absolute paths for anything missing. Required filenames:\n\n- `Jetson_Linux_R\u003Cver>_aarch64.tbz2`\n- `Tegra_Linux_Sample-Root-Filesystem_R\u003Cver>_aarch64.tbz2`\n\nBoth filenames must contain the same `R\u003Cver>` token. Refuse mismatches\nand record `\u003Cver>` as `bsp_image.version`. Do not download tarballs.\n\n### Extract and apply binaries\n\nUse absolute tarball paths; they may live outside\n`\u003Cbsp_image.root_path>`.\n\n```bash\nROOT=\"\u003Cbsp_image.root_path>\"\nBSP_TARBALL=\"\u003Cabsolute path to Jetson_Linux_R\u003Cver>_aarch64.tbz2>\"\nROOTFS_TARBALL=\"\u003Cabsolute path to Tegra_Linux_Sample-Root-Filesystem_R\u003Cver>_aarch64.tbz2>\"\n\nmkdir -p \"$ROOT\"\ntar xjf \"$BSP_TARBALL\" -C \"$ROOT\"\nsudo tar xpjf \"$ROOTFS_TARBALL\" -C \"$ROOT\u002FLinux_for_Tegra\u002Frootfs\"\n\ncd \"$ROOT\u002FLinux_for_Tegra\"\nif [ \"$GPU_STACK\" = \"openrm\" ]; then\n  sudo .\u002Fapply_binaries.sh --openrm\nelse\n  sudo .\u002Fapply_binaries.sh\nfi\n```\n\nSet `GPU_STACK` from the \"Determine GPU stack\" step above. Abort on the first failing command and\nsurface the failed command.\n\n### Update the active profile\n\nPersist the resolved BSP image metadata in the active target profile so\nlater skills can find the BSP without re-prompting. Preserve existing\nblocks, comments, and quoted SKU values; use a round-tripping YAML\nwriter such as `ruamel.yaml`.\n\n```yaml\nbsp_image:\n  root_path: \u003Cabsolute override path>  # omit for \u003Cworkspace>\u002FImage\n  version: \"\u003Cderived version>\"\n```\n\nRules:\n\n- Same version and same root path: no rewrite.\n- Different version: ask before updating.\n- Different recorded `root_path`: refuse automatic rewrite.\n- Always quote `version`.\n\n## Finish\n\nReport the image path, extracted vs reused state, GPU stack, derived\nversion, and profile update status. Then suggest `\u002Fjetson-init-source`.\n\n## Purpose\n\nMaterialize `Linux_for_Tegra\u002F` on disk by extracting the right Jetson\nLinux + sample-rootfs tarballs and running `apply_binaries.sh` with\nthe GPU-stack flag derived from the active target (nvgpu for T234,\nOpenRM for T264+). Then commit the derived BSP version into the\nprofile's `bsp_image:` block.\n\n## Prerequisites\n\n- Active target profile resolved per\n  `..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`.\n- Jetson Linux BSP tarball and matching sample-rootfs tarball staged\n  on disk (e.g. by `\u002Fjetson-download-bsp` or hand-placed).\n- Write access to the workspace `Image\u002F` root (or the override\n  `bsp_image.root_path`).\n- `sudo` available for `apply_binaries.sh`.\n\n## Limitations\n\n- Writes only the `bsp_image:` block; source tree, documents, and\n  carrier profile are owned by sibling skills.\n- Refuses to overwrite an existing `Linux_for_Tegra\u002F` without explicit\n  user direction.\n- Does not download tarballs; rely on `\u002Fjetson-download-bsp` or\n  hand-stage the inputs.\n\n## Troubleshooting\n\n- **`apply_binaries.sh` exits non-zero** — re-read its console output;\n  most failures are missing `sudo`, missing rootfs tarball, or wrong\n  GPU stack flag for the SoC generation.\n- **`nv_tegra_release` absent after extract** — extraction stopped\n  early; verify tarball integrity and rerun.\n- **Recorded `version` disagrees with the tarball filename** — the\n  tarball was renamed; trust the value parsed from\n  `Linux_for_Tegra\u002Fnv_tegra_release` over filenames.\n- **Different recorded `root_path` already in profile** — refuse and\n  ask the user to confirm before overwriting.\n\n## References\n\n- [`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md)\n- [`..\u002F..\u002Freferences\u002Fbsp-platforms-catalogue.md`](..\u002F..\u002Freferences\u002Fbsp-platforms-catalogue.md)\n- [`..\u002F..\u002Freferences\u002Fplatform_template.yaml`](..\u002F..\u002Freferences\u002Fplatform_template.yaml)\n- [`..\u002Fjetson-init-target\u002FSKILL.md`](..\u002Fjetson-init-target\u002FSKILL.md)\n- [`..\u002Fjetson-init-source\u002FSKILL.md`](..\u002Fjetson-init-source\u002FSKILL.md)\n- [`..\u002Fjetson-flash-image\u002FSKILL.md`](..\u002Fjetson-flash-image\u002FSKILL.md)\n",{"name":5,"license":15,"version":24,"metadata":25,"description":7},"0.0.1",{"tags":26,"author":30,"domain":31,"data-classification":32},[27,28,29],"bsp","image","bootstrap","Jetson Team","meta","public","main","86cc27ffd16af6cb85948f1155578e6f3f61cc4c","skillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-init-image","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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add Solizardking\u002Ftrain2earn --skill jetson-init-image",{"tool":47,"command":48},"bunx","bunx skills add Solizardking\u002Ftrain2earn --skill jetson-init-image",{"tool":50,"command":51},"pnpm","pnpm dlx skills add Solizardking\u002Ftrain2earn --skill jetson-init-image","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-init-image\u002FSKILL.md",true,[55,61,65,69],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"BENCHMARK.md","REFERENCE","参考文档",3812,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-init-image\u002FBENCHMARK.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"metadata.json",390,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-init-image\u002Fmetadata.json",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"skill-card.md",4087,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-init-image\u002Fskill-card.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"verification.json",1375,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-init-image\u002Fverification.json",[74,82,90,98,105,113],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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",[],[]]