[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M789V8GXKB9QQ34EDZ627GSF":3,"skill-same:01M789V8GXKB9QQ34EDZ627GSF":75},{"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":38,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M789V8GXKB9QQ34EDZ627GSF","jetson-print-bsp-info",null,"Use when you need to print Jetson BSP info (L4T version, board configs, rootfs state) from a Linux_for_Tegra root on the host PC. This is an example skill.","Solizardking\u002Fskillhub-main","Solizardking","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F108096810?v=4","01M786KDB10AYV042N0F9BD5B5","Clawd","01M786NYYXSZK1D05WM8JQPC48",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-print-bsp-info\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: jetson-print-bsp-info\ndescription: Use when you need to print Jetson BSP info (L4T version, board configs, rootfs state) from a Linux_for_Tegra root on the host PC. This is an example skill.\nversion: 0.0.1\nlicense: \"Apache-2.0\"\nmetadata:\n  author: \"Jetson Team\"\n  tags: [jetson, bsp, info]\n  languages: [bash]\n  data-classification: public\n---\n\n# jetson-print-bsp-info\n\nPrints a concise summary of a Jetson Linux_for_Tegra (BSP) tree on the host PC.\n\nThis skill is intended as a reference example for the `jetson-bsp-skills` repo and the NVIDIA-wide skills CI. It performs read-only inspection — no flashing, no rootfs changes.\n\n## Purpose\n\nCapture a baseline snapshot of a Linux_for_Tegra BSP tree (release, board configs, rootfs state) before flashing, so issues like \"wrong L4T version\" or \"rootfs never populated\" are caught early.\n\n## When to use\n\n- A user has unpacked a Jetson BSP tarball and wants to confirm the L4T version, supported boards, and rootfs state before flashing.\n- You need a quick sanity check that a `Linux_for_Tegra\u002F` directory looks valid (expected scripts and config files present).\n\n## Prerequisites\n\n- Running on the host PC (Linux), not on the Jetson target.\n- A `Linux_for_Tegra\u002F` directory extracted from a Jetson BSP tarball.\n- Standard CLIs available: `ls`, `head`, `cat`, `paste`, `sed`.\n\n## Inputs\n\n- `L4T_ROOT` (optional): absolute path to the `Linux_for_Tegra\u002F` directory. If unset, use the current working directory.\n\n## Instructions\n\nRun each step in order and print the captured values into the report shown under [Output format](#output-format).\n\n1. **Resolve** `L4T_ROOT` and **validate** the directory is a Linux_for_Tegra root — exit early otherwise. `flash.sh` and `nv_tegra\u002F` are the two anchor artifacts that every BSP ships:\n   ```bash\n   L4T_ROOT=\"${L4T_ROOT:-$PWD}\"\n   if [ ! -f \"$L4T_ROOT\u002Fflash.sh\" ] || [ ! -d \"$L4T_ROOT\u002Fnv_tegra\" ]; then\n     echo \"Not a Linux_for_Tegra root: '$L4T_ROOT' (missing flash.sh or nv_tegra\u002F)\"\n     exit 1\n   fi\n   echo \"$L4T_ROOT\"\n   ```\n2. **Extract** the L4T release header line. The canonical host-side location is `nv_tegra\u002Fnv_tegra_release`; the same file is copied into the rootfs by `apply_binaries.sh`. Only the first line is useful — the rest is a long list of library SHAs:\n   ```bash\n   head -1 \"$L4T_ROOT\u002Fnv_tegra\u002Fnv_tegra_release\" 2>\u002Fdev\u002Fnull \\\n     || head -1 \"$L4T_ROOT\u002Frootfs\u002Fetc\u002Fnv_tegra_release\" 2>\u002Fdev\u002Fnull \\\n     || echo \"L4T release info not found\"\n   ```\n3. **List** supported board config files and **join** them onto one comma-separated line:\n   ```bash\n   (cd \"$L4T_ROOT\" && ls *.conf 2>\u002Fdev\u002Fnull) | paste -sd, -\n   ```\n4. **Check** whether the rootfs has been populated. An empty `rootfs\u002F` means `apply_binaries.sh` has not been run yet:\n   ```bash\n   if [ -f \"$L4T_ROOT\u002Frootfs\u002Fetc\u002Fpasswd\" ]; then\n     echo \"populated\"\n   else\n     echo \"empty\"\n   fi\n   ```\n\n## Output format\n\nPrint a short report with these sections, one line each where possible:\n\n```text\nL4T root:        \u003Cpath>\nL4T release:     \u003Crelease header line>\nBoard configs:   \u003Ccomma-separated list>\nRootfs:          populated | empty\n```\n\n## Examples\n\nExample output on an Orin AGX BSP (L4T R36):\n\n```text\nL4T root:        $HOME\u002FLinux_for_Tegra\nL4T release:     # R36 (release), REVISION: 3.0\nBoard configs:   jetson-agx-orin-devkit.conf,jetson-orin-nano-devkit.conf\nRootfs:          populated\n```\n\nExample output on a freshly untarred BSP where `apply_binaries.sh` has not been run yet:\n\n```text\nL4T root:        \u002Ftmp\u002FLinux_for_Tegra\nL4T release:     # R39 (release), REVISION: 0.0\nBoard configs:   jetson-agx-thor-devkit.conf\nRootfs:          empty\n```\n\n## Error handling\n\nEach command falls back to a clearly labeled `\"... not found\"` string if the underlying file is missing — the skill never errors out mid-report. If `L4T_ROOT` does not contain `flash.sh` and `nv_tegra\u002F`, exit early with a clear \"not a Linux_for_Tegra root\" message rather than printing misleading info.\n\n## Limitations\n\n- Read-only inspection only — does not validate signatures, kernel images, or device-tree overlays.\n- Only checks the presence of `rootfs\u002Fetc\u002Fpasswd` as a populated-rootfs proxy; will not detect a half-populated rootfs.\n- Lists all `*.conf` board configs in `L4T_ROOT\u002F`; does not try to infer which one the user intends to flash.\n\n## Troubleshooting\n\n- **Error:** `Not a Linux_for_Tegra root: '...' (missing flash.sh or nv_tegra\u002F)`\n  **Cause:** `L4T_ROOT` points at a parent directory, an extracted rootfs, or an unrelated path.\n  **Solution:** Point `L4T_ROOT` at the directory that contains `flash.sh` (typically `Linux_for_Tegra\u002F`).\n\n- **Error:** `L4T release info not found`\n  **Cause:** Neither `nv_tegra\u002Fnv_tegra_release` nor `rootfs\u002Fetc\u002Fnv_tegra_release` exists — the BSP tarball may be incomplete or `apply_binaries.sh` was never run.\n  **Solution:** Re-extract the BSP tarball or run `apply_binaries.sh` to populate the rootfs.\n\n## Notes\n\n- Do not modify any files. This skill is read-only.\n- If multiple board config files exist, list all of them — do not try to guess which one the user intends to flash.\n","# jetson-print-bsp-info\n\nPrints a concise summary of a Jetson Linux_for_Tegra (BSP) tree on the host PC.\n\nThis skill is intended as a reference example for the `jetson-bsp-skills` repo and the NVIDIA-wide skills CI. It performs read-only inspection — no flashing, no rootfs changes.\n\n## Purpose\n\nCapture a baseline snapshot of a Linux_for_Tegra BSP tree (release, board configs, rootfs state) before flashing, so issues like \"wrong L4T version\" or \"rootfs never populated\" are caught early.\n\n## When to use\n\n- A user has unpacked a Jetson BSP tarball and wants to confirm the L4T version, supported boards, and rootfs state before flashing.\n- You need a quick sanity check that a `Linux_for_Tegra\u002F` directory looks valid (expected scripts and config files present).\n\n## Prerequisites\n\n- Running on the host PC (Linux), not on the Jetson target.\n- A `Linux_for_Tegra\u002F` directory extracted from a Jetson BSP tarball.\n- Standard CLIs available: `ls`, `head`, `cat`, `paste`, `sed`.\n\n## Inputs\n\n- `L4T_ROOT` (optional): absolute path to the `Linux_for_Tegra\u002F` directory. If unset, use the current working directory.\n\n## Instructions\n\nRun each step in order and print the captured values into the report shown under [Output format](#output-format).\n\n1. **Resolve** `L4T_ROOT` and **validate** the directory is a Linux_for_Tegra root — exit early otherwise. `flash.sh` and `nv_tegra\u002F` are the two anchor artifacts that every BSP ships:\n   ```bash\n   L4T_ROOT=\"${L4T_ROOT:-$PWD}\"\n   if [ ! -f \"$L4T_ROOT\u002Fflash.sh\" ] || [ ! -d \"$L4T_ROOT\u002Fnv_tegra\" ]; then\n     echo \"Not a Linux_for_Tegra root: '$L4T_ROOT' (missing flash.sh or nv_tegra\u002F)\"\n     exit 1\n   fi\n   echo \"$L4T_ROOT\"\n   ```\n2. **Extract** the L4T release header line. The canonical host-side location is `nv_tegra\u002Fnv_tegra_release`; the same file is copied into the rootfs by `apply_binaries.sh`. Only the first line is useful — the rest is a long list of library SHAs:\n   ```bash\n   head -1 \"$L4T_ROOT\u002Fnv_tegra\u002Fnv_tegra_release\" 2>\u002Fdev\u002Fnull \\\n     || head -1 \"$L4T_ROOT\u002Frootfs\u002Fetc\u002Fnv_tegra_release\" 2>\u002Fdev\u002Fnull \\\n     || echo \"L4T release info not found\"\n   ```\n3. **List** supported board config files and **join** them onto one comma-separated line:\n   ```bash\n   (cd \"$L4T_ROOT\" && ls *.conf 2>\u002Fdev\u002Fnull) | paste -sd, -\n   ```\n4. **Check** whether the rootfs has been populated. An empty `rootfs\u002F` means `apply_binaries.sh` has not been run yet:\n   ```bash\n   if [ -f \"$L4T_ROOT\u002Frootfs\u002Fetc\u002Fpasswd\" ]; then\n     echo \"populated\"\n   else\n     echo \"empty\"\n   fi\n   ```\n\n## Output format\n\nPrint a short report with these sections, one line each where possible:\n\n```text\nL4T root:        \u003Cpath>\nL4T release:     \u003Crelease header line>\nBoard configs:   \u003Ccomma-separated list>\nRootfs:          populated | empty\n```\n\n## Examples\n\nExample output on an Orin AGX BSP (L4T R36):\n\n```text\nL4T root:        $HOME\u002FLinux_for_Tegra\nL4T release:     # R36 (release), REVISION: 3.0\nBoard configs:   jetson-agx-orin-devkit.conf,jetson-orin-nano-devkit.conf\nRootfs:          populated\n```\n\nExample output on a freshly untarred BSP where `apply_binaries.sh` has not been run yet:\n\n```text\nL4T root:        \u002Ftmp\u002FLinux_for_Tegra\nL4T release:     # R39 (release), REVISION: 0.0\nBoard configs:   jetson-agx-thor-devkit.conf\nRootfs:          empty\n```\n\n## Error handling\n\nEach command falls back to a clearly labeled `\"... not found\"` string if the underlying file is missing — the skill never errors out mid-report. If `L4T_ROOT` does not contain `flash.sh` and `nv_tegra\u002F`, exit early with a clear \"not a Linux_for_Tegra root\" message rather than printing misleading info.\n\n## Limitations\n\n- Read-only inspection only — does not validate signatures, kernel images, or device-tree overlays.\n- Only checks the presence of `rootfs\u002Fetc\u002Fpasswd` as a populated-rootfs proxy; will not detect a half-populated rootfs.\n- Lists all `*.conf` board configs in `L4T_ROOT\u002F`; does not try to infer which one the user intends to flash.\n\n## Troubleshooting\n\n- **Error:** `Not a Linux_for_Tegra root: '...' (missing flash.sh or nv_tegra\u002F)`\n  **Cause:** `L4T_ROOT` points at a parent directory, an extracted rootfs, or an unrelated path.\n  **Solution:** Point `L4T_ROOT` at the directory that contains `flash.sh` (typically `Linux_for_Tegra\u002F`).\n\n- **Error:** `L4T release info not found`\n  **Cause:** Neither `nv_tegra\u002Fnv_tegra_release` nor `rootfs\u002Fetc\u002Fnv_tegra_release` exists — the BSP tarball may be incomplete or `apply_binaries.sh` was never run.\n  **Solution:** Re-extract the BSP tarball or run `apply_binaries.sh` to populate the rootfs.\n\n## Notes\n\n- Do not modify any files. This skill is read-only.\n- If multiple board config files exist, list all of them — do not try to guess which one the user intends to flash.\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","bsp","info","Jetson Team",[32],"bash","public","main","be3de0244dc1a57e323d8160787ebb40fb64930e","public\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-print-bsp-info","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main","https:\u002F\u002Fskills.x402.wtf","https:\u002F\u002Fgithub.com\u002FSolizardking","https:\u002F\u002Fmusebook.trade","Got a mile high and never came down","2026-10-08 23:20:13",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add Solizardking\u002Fskillhub-main --skill jetson-print-bsp-info",{"tool":49,"command":50},"bunx","bunx skills add Solizardking\u002Fskillhub-main --skill jetson-print-bsp-info",{"tool":52,"command":53},"pnpm","pnpm dlx skills add Solizardking\u002Fskillhub-main --skill jetson-print-bsp-info","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-print-bsp-info\u002FSKILL.md",true,[57,63,67,71],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"BENCHMARK.md","REFERENCE","参考文档",3574,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-print-bsp-info\u002FBENCHMARK.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"metadata.json",368,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-print-bsp-info\u002Fmetadata.json",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"skill-card.md",3621,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-print-bsp-info\u002Fskill-card.md",{"path":72,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":73,"sourceHtmlUrl":74},"verification.json",1357,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-print-bsp-info\u002Fverification.json",[76,84,91,98,105,113],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M78E0TGCAMNPS207BA3G07S7","zkrouter","Self-hosted OpenAI-compatible LLM router — smart tier-based routing, ZK-stamped routing decisions, mode overrides, free OpenRouter at install via the Birth bot. Save 60-80% on inference costs by routing to the cheapest capable model across 12+ OpenRouter models.","MIT","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzkrouter\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M78E0R1Z8BDT6EDTHY17MTNB","zk","For custom ZK Solana programs and privacy-preserving applications to prevent double spending. Guide to integrate rent-free nullifier PDAs for double-spend prevention.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M78E0P3ZTZ1YWF8MD5MM23QE","zk-omni-messaging","Zero-knowledge omnichain messaging between Robinhood Chain and Solana using CheshireZkOmniMessenger (msgType 4) with nullifier anti-replay and the zk-omni-relayer service.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk-omni-messaging\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":80,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M78E0JXZ2PNB1896VXAGDBWD","zerion-wallet-data","Use when the user asks to check a wallet's portfolio, token balances, DeFi positions, PnL, transaction history, or NFTs. Provides interpreted on-chain data across 40+ EVM chains and Solana via x402 pay-per-request or API key — no raw RPC decoding needed.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzerion-wallet-data\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":80,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M78E0G14FH9GRRTQYMKD5E59","youtube-clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\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":80,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M78E0C2ZYA99CFFDNB7ZMK5S","yield-optimization","Multi-chain yield optimization via yield.xyz (StakeKit). Discover 2,988+ yield opportunities across 75+ blockchains, build deposit\u002Fwithdrawal transactions with shell scripts, and sign them with a MoonPay wallet. Use when the user wants to earn yield, find the best lending or staking rate, enter\u002Fexit a position, or check portfolio balances.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyield-optimization\u002FSKILL.md",[],[]]