[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M788MMN4DY17RF1AE6748P7S":3,"skill-same:01M788MMN4DY17RF1AE6748P7S":81},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M788MMN4DY17RF1AE6748P7S","vss-setup-video-analytics-api",null,"Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.","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\u002Fvss-setup-video-analytics-api\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vss-setup-video-analytics-api\ndescription: Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.\nlicense: Apache-2.0\nmetadata:\n  author: \"NVIDIA Video Search and Summarization team\"\n  version: \"3.2.0\"\n  github-url: \"https:\u002F\u002Fgithub.com\u002FNVIDIA-AI-Blueprints\u002Fvideo-search-and-summarization\"\n  tags: \"nvidia blueprint operational deployment video-analytics-api rest-api\"\n---\n## Purpose\n\nDeploy the video-analytics-api REST service standalone with the user's chosen config, data-log bind, and Elasticsearch \u002F Kafka connectivity.\n\n## Instructions\n\nFollow the routing tables and step-by-step workflows below. Each section that ends in *workflow*, *quick start*, or *flow* is intended to be executed top-to-bottom. Detailed reference material lives in `references\u002F`.\n\n## Examples\n\nWorked end-to-end examples are kept under `evals\u002F` (each `*.json` manifest\ncontains a runnable scenario). Run a Tier-3 evaluation to replay them:\n\n```bash\nnv-base validate skills\u002Fvss-setup-video-analytics-api --agent-eval\n```\n\nA minimal standalone bring-up looks like:\n\n```bash\ncd $REPO\u002Fdeploy\u002Fdocker\nexport VSS_APPS_DIR=$(pwd)\nexport VSS_DATA_DIR=${VSS_DATA_DIR:-\u002Ftmp\u002Fvss-data}\nmkdir -p \"$VSS_DATA_DIR\u002Fdata_log\u002Fvss_video_analytics_api\"\ndocker compose -f services\u002Fanalytics\u002Fvideo-analytics-api\u002Fcompose.yml up -d vss-video-analytics-api\ncurl -sf http:\u002F\u002Flocalhost:8081\u002Flivez\n```\n\nFollow [`references\u002Fdeploy-video-analytics-api-service.md`](references\u002Fdeploy-video-analytics-api-service.md) for the full\nworkflow (config source, data-log bind, infrastructure dependencies, REST endpoints).\nFor the field-by-field JSON config reference, see [`references\u002Fconfiguration.md`](references\u002Fconfiguration.md).\n\n## Limitations\n\n- Requires the matching VSS profile \u002F microservice to be deployed and reachable from the caller.\n- NGC-hosted models and NIMs may be subject to rate-limits, GPU memory requirements, and license restrictions.\n- Concurrency, GPU memory, and storage limits depend on the host hardware and the profile's compose file.\n\n## Troubleshooting\n\n- **Error**: REST call returns connection refused. **Cause**: target microservice not running. **Solution**: probe `\u002Fdocs` or `\u002Fhealth`; redeploy via `vss-deploy-profile` or the matching `vss-deploy-*` skill.\n- **Error**: HTTP 401\u002F403 from NGC pulls. **Cause**: missing\u002Fexpired `NGC_CLI_API_KEY`. **Solution**: `docker login nvcr.io` and re-export the key before retrying.\n- **Error**: container OOM or model fails to load. **Cause**: insufficient GPU memory for the selected profile. **Solution**: switch to a smaller variant or free GPUs via `docker compose down`.\n\n# VSS Setup Video Analytics API — Standalone\n\nDeploy **just** the `vss-video-analytics-api` container (the Node.js REST API from the upstream `video-analytics-api` repo), not as part of the full warehouse blueprint stack.\n\nThe full operational walkthrough — config-source options, data-log volume behavior, infrastructure dependencies, REST API endpoints, deploy + verify, troubleshooting — lives in [`references\u002Fdeploy-video-analytics-api-service.md`](references\u002Fdeploy-video-analytics-api-service.md). The field-by-field JSON config reference lives in [`references\u002Fconfiguration.md`](references\u002Fconfiguration.md). This SKILL.md only handles routing and prerequisites.\n\n## When to use\n\n- \"Deploy video analytics api\" \u002F \"run video-analytics-api standalone\"\n- \"I just want to run the REST API, not the full stack\"\n- \"Use my own video-analytics-api config\"\n- \"Point the API at a different Elasticsearch \u002F Kafka\"\n- \"Start the API without Kafka\" \u002F \"run the API broker-less\"\n- \"Check what REST endpoints are available\"\n\n## Prerequisites\n\n1. **Repo checkout** with `$VSS_APPS_DIR` pointing at `\u003Crepo>\u002Fdeploy\u002Fdocker\u002F`. Required by the service compose's volume binds.\n2. **NGC credentials** — `$NGC_CLI_API_KEY` set so docker can pull the image. See [`references\u002Fngc-api-key-registry-login.md`](references\u002Fngc-api-key-registry-login.md).\n\n   > **Secure-handling note for `NGC_CLI_API_KEY`**: this key is a\n   > long-lived credential that pulls all NVIDIA private images\n   > available to your NGC org. Never commit the key, never paste it\n   > into chat, never store it in `\u002Ftmp`. Read it interactively\n   > (`read -rs NGC_CLI_API_KEY`) or load it from your secret manager\n   > (Vault, AWS Secrets Manager, sealed-secrets) at deploy time.\n   > Write any derived `.env` files with `umask 077` + `chmod 600`,\n   > add them to `.gitignore`, and rotate the key on a defined\n   > cadence and after every host decommission. If it has ever been\n   > exposed (host snapshot, shared screen, ticket attachment),\n   > rotate immediately.\n3. **Docker runtime** — Docker Engine **28.3.3** with Docker Compose plugin **v2.39.1+**. Verify with `docker --version` and `docker compose version`.\n4. **Elasticsearch** — must be reachable at the URL configured in `elasticsearch.node`. The server pings ES on startup; if unreachable, it exits (and `restart: always` brings it back). If you need to bring up ES too, use the infra compose: `docker compose -f services\u002Finfra\u002Fcompose.yml up -d elasticsearch`.\n5. **Optional Kafka broker**. The API can run without Kafka. If you want a quiet broker-less deployment, use the image-baked config or a custom config with `kafka.brokers: []`; the service-shipped compose config points at `localhost:9092`, so Kafka-dependent features (dynamic config, dynamic calibration, RTLS\u002FAMR) will fail until a broker is reachable.\n6. **`$VSS_DATA_DIR` for the default compose.** The base compose bind-mounts `$VSS_DATA_DIR\u002Fdata_log\u002Fvss_video_analytics_api` for multipart upload handling and file-backed assets such as calibration images. Set the directory to a writable host path and pre-create it, or remove that mount if image uploads are not needed.\n\nIf any required prerequisite fails, surface the gap before going further.\n\n## Workflow\n\nHand the user [`references\u002Fdeploy-video-analytics-api-service.md`](references\u002Fdeploy-video-analytics-api-service.md) and walk them through its steps in order:\n\n1. Choose a config — image-baked default, service-shipped, or custom.\n2. Decide whether a data-log volume is needed for file uploads.\n3. Confirm infrastructure dependencies — Elasticsearch (required), Kafka (optional).\n4. Deploy + verify with `docker compose up` and health check.\n\nThe compose-file edits, config options, deploy + verify commands, REST API endpoint table, and troubleshooting table all live in that reference — don't duplicate them here.\n\n## Endpoint Reference\n\nUse [`references\u002Fdeploy-video-analytics-api-service.md`](references\u002Fdeploy-video-analytics-api-service.md) for the REST endpoint table and runtime dependency notes.\n\n## Kafka-dependent features (runtime, requires broker)\n\nOnce the container is up **and a Kafka broker is reachable**, three additional capabilities are available:\n\n### Dynamic config\n\nThe API acts as the **producer** for dynamic config updates. When an operator POSTs to `\u002Fconfig`, the API publishes an `upsert` message to the `mdx-notification` topic with Kafka key `behavior-analytics-config`. The downstream `behavior-analytics` container consumes this and ACKs back. The API also handles the bootstrap flow — when `behavior-analytics` starts, it publishes a `request-config` message, and the API replies with `upsert-all` containing the latest verified config from Elasticsearch.\n\nConsumer-side validation, ACK semantics, and the full wire contract are documented in the `vss-setup-behavior-analytics` dynamic-config reference.\n\n### Dynamic calibration\n\nThe API produces calibration update notifications on `mdx-notification` with Kafka key `calibration`. Supports `upsert-all` (full snapshot), `upsert` (per-sensor merge), and `delete` (per-sensor removal). The downstream `behavior-analytics` container consumes these and applies them to the live calibration.\n\nConsumer-side validation and per-action policy are documented in the `vss-setup-behavior-analytics` dynamic-calibration reference.\n\n### RTLS \u002F AMR\n\nThe API consumes real-time location (`mdx-rtls`) and AMR (`mdx-amr`) messages from Kafka and exposes them via REST endpoints.\n\n## Routing rules\n\n- If the user wants \"the full stack\" (UI \u002F agent \u002F perception): hand off to `vss-deploy-profile` with profile `warehouse` (or `alerts`). Don't run this skill in parallel.\n- If the user wants to deploy the analytics pipeline (behavior creation, incident detection): hand off to `vss-setup-behavior-analytics`.\n- If the user wants to publish a runtime config \u002F calibration update through the REST API: confirm Kafka is reachable, then use the `\u002Fconfig` or calibration endpoints and point them at the behavior-analytics dynamic-update references for the consumer wire contract.\n- If the user wants to understand the dynamic config \u002F dynamic calibration wire contract from the **consumer** (behavior-analytics) side: point them at the `vss-setup-behavior-analytics` dynamic-config and dynamic-calibration references.\n- If the user wants to query or interact with the REST API endpoints: the deploy reference endpoint table covers what's available. For the full OpenAPI spec, see `src\u002Fapp\u002Fspecification\u002Fopenapi.json` in the `video-analytics-api` repo.\n\n\nbump:1\n","## Purpose\n\nDeploy the video-analytics-api REST service standalone with the user's chosen config, data-log bind, and Elasticsearch \u002F Kafka connectivity.\n\n## Instructions\n\nFollow the routing tables and step-by-step workflows below. Each section that ends in *workflow*, *quick start*, or *flow* is intended to be executed top-to-bottom. Detailed reference material lives in `references\u002F`.\n\n## Examples\n\nWorked end-to-end examples are kept under `evals\u002F` (each `*.json` manifest\ncontains a runnable scenario). Run a Tier-3 evaluation to replay them:\n\n```bash\nnv-base validate skills\u002Fvss-setup-video-analytics-api --agent-eval\n```\n\nA minimal standalone bring-up looks like:\n\n```bash\ncd $REPO\u002Fdeploy\u002Fdocker\nexport VSS_APPS_DIR=$(pwd)\nexport VSS_DATA_DIR=${VSS_DATA_DIR:-\u002Ftmp\u002Fvss-data}\nmkdir -p \"$VSS_DATA_DIR\u002Fdata_log\u002Fvss_video_analytics_api\"\ndocker compose -f services\u002Fanalytics\u002Fvideo-analytics-api\u002Fcompose.yml up -d vss-video-analytics-api\ncurl -sf http:\u002F\u002Flocalhost:8081\u002Flivez\n```\n\nFollow [`references\u002Fdeploy-video-analytics-api-service.md`](references\u002Fdeploy-video-analytics-api-service.md) for the full\nworkflow (config source, data-log bind, infrastructure dependencies, REST endpoints).\nFor the field-by-field JSON config reference, see [`references\u002Fconfiguration.md`](references\u002Fconfiguration.md).\n\n## Limitations\n\n- Requires the matching VSS profile \u002F microservice to be deployed and reachable from the caller.\n- NGC-hosted models and NIMs may be subject to rate-limits, GPU memory requirements, and license restrictions.\n- Concurrency, GPU memory, and storage limits depend on the host hardware and the profile's compose file.\n\n## Troubleshooting\n\n- **Error**: REST call returns connection refused. **Cause**: target microservice not running. **Solution**: probe `\u002Fdocs` or `\u002Fhealth`; redeploy via `vss-deploy-profile` or the matching `vss-deploy-*` skill.\n- **Error**: HTTP 401\u002F403 from NGC pulls. **Cause**: missing\u002Fexpired `NGC_CLI_API_KEY`. **Solution**: `docker login nvcr.io` and re-export the key before retrying.\n- **Error**: container OOM or model fails to load. **Cause**: insufficient GPU memory for the selected profile. **Solution**: switch to a smaller variant or free GPUs via `docker compose down`.\n\n# VSS Setup Video Analytics API — Standalone\n\nDeploy **just** the `vss-video-analytics-api` container (the Node.js REST API from the upstream `video-analytics-api` repo), not as part of the full warehouse blueprint stack.\n\nThe full operational walkthrough — config-source options, data-log volume behavior, infrastructure dependencies, REST API endpoints, deploy + verify, troubleshooting — lives in [`references\u002Fdeploy-video-analytics-api-service.md`](references\u002Fdeploy-video-analytics-api-service.md). The field-by-field JSON config reference lives in [`references\u002Fconfiguration.md`](references\u002Fconfiguration.md). This SKILL.md only handles routing and prerequisites.\n\n## When to use\n\n- \"Deploy video analytics api\" \u002F \"run video-analytics-api standalone\"\n- \"I just want to run the REST API, not the full stack\"\n- \"Use my own video-analytics-api config\"\n- \"Point the API at a different Elasticsearch \u002F Kafka\"\n- \"Start the API without Kafka\" \u002F \"run the API broker-less\"\n- \"Check what REST endpoints are available\"\n\n## Prerequisites\n\n1. **Repo checkout** with `$VSS_APPS_DIR` pointing at `\u003Crepo>\u002Fdeploy\u002Fdocker\u002F`. Required by the service compose's volume binds.\n2. **NGC credentials** — `$NGC_CLI_API_KEY` set so docker can pull the image. See [`references\u002Fngc-api-key-registry-login.md`](references\u002Fngc-api-key-registry-login.md).\n\n   > **Secure-handling note for `NGC_CLI_API_KEY`**: this key is a\n   > long-lived credential that pulls all NVIDIA private images\n   > available to your NGC org. Never commit the key, never paste it\n   > into chat, never store it in `\u002Ftmp`. Read it interactively\n   > (`read -rs NGC_CLI_API_KEY`) or load it from your secret manager\n   > (Vault, AWS Secrets Manager, sealed-secrets) at deploy time.\n   > Write any derived `.env` files with `umask 077` + `chmod 600`,\n   > add them to `.gitignore`, and rotate the key on a defined\n   > cadence and after every host decommission. If it has ever been\n   > exposed (host snapshot, shared screen, ticket attachment),\n   > rotate immediately.\n3. **Docker runtime** — Docker Engine **28.3.3** with Docker Compose plugin **v2.39.1+**. Verify with `docker --version` and `docker compose version`.\n4. **Elasticsearch** — must be reachable at the URL configured in `elasticsearch.node`. The server pings ES on startup; if unreachable, it exits (and `restart: always` brings it back). If you need to bring up ES too, use the infra compose: `docker compose -f services\u002Finfra\u002Fcompose.yml up -d elasticsearch`.\n5. **Optional Kafka broker**. The API can run without Kafka. If you want a quiet broker-less deployment, use the image-baked config or a custom config with `kafka.brokers: []`; the service-shipped compose config points at `localhost:9092`, so Kafka-dependent features (dynamic config, dynamic calibration, RTLS\u002FAMR) will fail until a broker is reachable.\n6. **`$VSS_DATA_DIR` for the default compose.** The base compose bind-mounts `$VSS_DATA_DIR\u002Fdata_log\u002Fvss_video_analytics_api` for multipart upload handling and file-backed assets such as calibration images. Set the directory to a writable host path and pre-create it, or remove that mount if image uploads are not needed.\n\nIf any required prerequisite fails, surface the gap before going further.\n\n## Workflow\n\nHand the user [`references\u002Fdeploy-video-analytics-api-service.md`](references\u002Fdeploy-video-analytics-api-service.md) and walk them through its steps in order:\n\n1. Choose a config — image-baked default, service-shipped, or custom.\n2. Decide whether a data-log volume is needed for file uploads.\n3. Confirm infrastructure dependencies — Elasticsearch (required), Kafka (optional).\n4. Deploy + verify with `docker compose up` and health check.\n\nThe compose-file edits, config options, deploy + verify commands, REST API endpoint table, and troubleshooting table all live in that reference — don't duplicate them here.\n\n## Endpoint Reference\n\nUse [`references\u002Fdeploy-video-analytics-api-service.md`](references\u002Fdeploy-video-analytics-api-service.md) for the REST endpoint table and runtime dependency notes.\n\n## Kafka-dependent features (runtime, requires broker)\n\nOnce the container is up **and a Kafka broker is reachable**, three additional capabilities are available:\n\n### Dynamic config\n\nThe API acts as the **producer** for dynamic config updates. When an operator POSTs to `\u002Fconfig`, the API publishes an `upsert` message to the `mdx-notification` topic with Kafka key `behavior-analytics-config`. The downstream `behavior-analytics` container consumes this and ACKs back. The API also handles the bootstrap flow — when `behavior-analytics` starts, it publishes a `request-config` message, and the API replies with `upsert-all` containing the latest verified config from Elasticsearch.\n\nConsumer-side validation, ACK semantics, and the full wire contract are documented in the `vss-setup-behavior-analytics` dynamic-config reference.\n\n### Dynamic calibration\n\nThe API produces calibration update notifications on `mdx-notification` with Kafka key `calibration`. Supports `upsert-all` (full snapshot), `upsert` (per-sensor merge), and `delete` (per-sensor removal). The downstream `behavior-analytics` container consumes these and applies them to the live calibration.\n\nConsumer-side validation and per-action policy are documented in the `vss-setup-behavior-analytics` dynamic-calibration reference.\n\n### RTLS \u002F AMR\n\nThe API consumes real-time location (`mdx-rtls`) and AMR (`mdx-amr`) messages from Kafka and exposes them via REST endpoints.\n\n## Routing rules\n\n- If the user wants \"the full stack\" (UI \u002F agent \u002F perception): hand off to `vss-deploy-profile` with profile `warehouse` (or `alerts`). Don't run this skill in parallel.\n- If the user wants to deploy the analytics pipeline (behavior creation, incident detection): hand off to `vss-setup-behavior-analytics`.\n- If the user wants to publish a runtime config \u002F calibration update through the REST API: confirm Kafka is reachable, then use the `\u002Fconfig` or calibration endpoints and point them at the behavior-analytics dynamic-update references for the consumer wire contract.\n- If the user wants to understand the dynamic config \u002F dynamic calibration wire contract from the **consumer** (behavior-analytics) side: point them at the `vss-setup-behavior-analytics` dynamic-config and dynamic-calibration references.\n- If the user wants to query or interact with the REST API endpoints: the deploy reference endpoint table covers what's available. For the full OpenAPI spec, see `src\u002Fapp\u002Fspecification\u002Fopenapi.json` in the `video-analytics-api` repo.\n\n\nbump:1\n",{"name":5,"license":15,"metadata":24,"description":7},{"tags":25,"author":26,"version":27,"github-url":28},"nvidia blueprint operational deployment video-analytics-api rest-api","NVIDIA Video Search and Summarization team","3.2.0","https:\u002F\u002Fgithub.com\u002FNVIDIA-AI-Blueprints\u002Fvideo-search-and-summarization","main","86cc27ffd16af6cb85948f1155578e6f3f61cc4c","skillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api","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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Solizardking\u002Ftrain2earn --skill vss-setup-video-analytics-api",{"tool":43,"command":44},"bunx","bunx skills add Solizardking\u002Ftrain2earn --skill vss-setup-video-analytics-api",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Solizardking\u002Ftrain2earn --skill vss-setup-video-analytics-api","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002FSKILL.md",true,[51,57,61,65,69,73,77],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"BENCHMARK.md","REFERENCE","参考文档",3933,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002FBENCHMARK.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"metadata.json",396,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002Fmetadata.json",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fconfiguration.md",4078,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002Freferences\u002Fconfiguration.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fdeploy-video-analytics-api-service.md",15349,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002Freferences\u002Fdeploy-video-analytics-api-service.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fngc-api-key-registry-login.md",2018,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002Freferences\u002Fngc-api-key-registry-login.md",{"path":74,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":75,"sourceHtmlUrl":76},"skill-card.md",3964,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002Fskill-card.md",{"path":78,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":79,"sourceHtmlUrl":80},"verification.json",1935,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002Fverification.json",[82,90,98,106,113,121],{"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":86,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"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",[],[]]