[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78883YP4RAZAR1X43A6F532":3,"skill-same:01M78883YP4RAZAR1X43A6F532":115},{"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":35,"commitSha":36,"skillDirectory":37,"forksCount":14,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M78883YP4RAZAR1X43A6F532","tao-finetune-clip",null,"CLIP vision-language model for image-text retrieval, zero-shot classification, embedding extraction, ONNX export, and TensorRT deployment. Use when fine-tuning or training CLIP, running zero-shot classification, computing image embeddings, or deploying CLIP to ONNX\u002FTensorRT.","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\u002Ftao-finetune-clip\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tao-finetune-clip\ndescription: CLIP vision-language model for image-text retrieval, zero-shot classification, embedding extraction, ONNX\n  export, and TensorRT deployment. Use when fine-tuning or training CLIP, running zero-shot classification, computing image\n  embeddings, or deploying CLIP to ONNX\u002FTensorRT.\nlicense: Apache-2.0\ncompatibility: Requires docker + nvidia-container-toolkit.\nmetadata:\n  author: NVIDIA Corporation\n  version: \"0.1.0\"\nallowed-tools: Read Bash\ntags:\n- vision-language\n- classification\n- embedding\n- zero-shot\n- deployment\n---\n\n# CLIP\n\nContrastive Language-Image Pre-training model for zero-shot and fine-tuned image classification, image-text retrieval, and embedding extraction. Fine-tuning adapts CLIP's shared image-text embedding space to domain-specific image-caption data.\n\nNo default NGC pretrained checkpoint is required for spec construction, but unset checkpoint behavior is action-specific. In the validation-fixes PyTorch image, `export.checkpoint: null` exports the selected CLIP architecture and may initialize weights when pretrained weights are unavailable. Do not assume `inference.checkpoint: null` loads pretrained weights: `clip inference` currently calls the checkpoint loader with `None` and fails before embedding extraction. For PyTorch inference, checkpoint-backed evaluation\u002Fexport, resume, and retrain flows, resolve and pass an exact checkpoint from the parent train output. For trusted TAO checkpoints produced by the current run or a known parent job, set `TORCH_FORCE_NO_WEIGHTS_ONLY_LOAD=1` on checkpoint-dependent PyTorch actions so PyTorch 2.6 can load the Lightning checkpoint metadata; do not set this for untrusted checkpoints.\n\nSupported actions: `train`, `evaluate`, `inference`, `export`, `gen_trt_engine`.\n\n## Train Action Policy\n\nThis model is AutoML-enabled at the model layer. Before handling any train-stage request, read `references\u002Fskill_info.yaml` and resolve the run override from either an explicit `automl_policy` value or the user's workflow request. Use `automl_policy: on` by default and only expose `on` \u002F `off` in new launch prompts. Treat phrases like \"turn off AutoML\", \"disable AutoML\", \"no HPO\", or \"plain training\" as `automl_policy: off` for this run only. When `automl_policy: on`, `automl_enabled: true`, and both `schemas\u002Ftrain.schema.json` and `references\u002Fspec_template_train.yaml` are packaged, route the train action through `tao-skill-bank:tao-run-automl` by default with this model's `skill_dir`. Preserve workflow\u002Fapplication overrides for datasets, specs, output directories, GPU\u002Fplatform settings, parent checkpoints, and `automl_policy`. Use direct model training only when `automl_policy: off` or the packaged train schema\u002Ftemplate is missing; in the missing-schema case, report that AutoML is enabled but not runnable for this model until schemas are generated.\n\nThe packaged CLIP train schema enables `train.optim.vision_lr` and `train.optim.text_lr` as default AutoML search parameters. For smoke tests, keep the search small by using the Bayesian algorithm with two recommendations and narrow LR ranges.\n\nNon-train actions such as `evaluate`, `inference`, `export`, and deploy flows stay in this model skill. The per-run `automl_policy` override does not change model metadata.\n\n## Instructions\n\nUse this skill for NVIDIA TAO CLIP jobs: training, evaluation, embedding inference, ONNX export, and TensorRT engine generation. Start by identifying the requested action, then load only the referenced files needed for that action: `defaults.json` for default parameters, `config.json` for action\u002Fdata-source wiring, `references\u002Fspec_template.yaml` for full spec shape, and `references\u002Fmodel_info.yaml` for SDK metadata.\n\nFor dataset-backed actions, collect the required image, caption, list, or prompt files from the user and place the resolved paths in `spec_overrides`. For local Docker runs, mount extracted folders in the container and point `image_dir` \u002F `caption_dir` at those folders; if a data source provides `.tar.gz` archives, extract them before running the in-container CLIP commands. For `export` and `gen_trt_engine`, infer parent artifacts from the upstream job when available; otherwise require explicit checkpoint, ONNX, or engine paths. Run `gen_trt_engine`, TensorRT `evaluate`, and TensorRT `inference` in the TAO Deploy image.\n\nFor TAO Deploy TensorRT actions (`gen_trt_engine`, TensorRT `evaluate`, and TensorRT `inference`), read `references\u002Ftao-deploy-clip.md` first. Deploy spec templates live in this skill's `references\u002F` folder with the `spec_template_deploy_*.yaml` prefix.\n\n## Training Requirements\n\n- **Dataset type:** image_text\n- **Formats:** custom image\u002Fcaption folders or WebDataset shards\n- **Monitoring metric:** val\u002Ft2i_mAP\n\n### Supported Models\n\n- **OpenCLIP \u002F NV-CLIP:** `ViT-L-14-SigLIP-CLIPA-224` (default), `ViT-L-14-SigLIP-CLIPA-336`, `ViT-H-14-SigLIP-CLIPA-224`, `ViT-H-14-SigLIP-CLIPA-336`, `ViT-H-14-SigLIP-CLIPA-574`\n- **Radio-CLIP:** `c-radio_v3-b`, `c-radio_v3-l`, `c-radio_v3-h`, `c-radio_v3-g`\n- **SigLIP2:** `siglip2-so400m-patch16-256`, `siglip2-so400m-patch14-224`, `siglip2-so400m-patch14-384`, `siglip2-so400m-patch16-384`, `siglip2-so400m-patch16-512`, `siglip2-so400m-patch16-naflex`\n\nRadio-CLIP requires `model.adaptor_name` to be set to `siglip` or `clip`.\n\n### Per-Action Dataset Requirements\n\n| Action | Spec Key | Source | Files | List? |\n|---|---|---|---|---|\n| train | dataset.train.datasets | train_datasets | image_dir: images.tar.gz, image_list_file: image_list.txt, caption_dir: captions.tar.gz | Yes |\n| train | dataset.train.wds.root_dir | train_wds_dataset | root directory containing `.tar` shards | No |\n| train | dataset.train.wds.shard_list_file | train_wds_dataset | shards.txt listing shard paths | No |\n| train | dataset.val.datasets | eval_dataset | image_dir: images.tar.gz, image_list_file: image_list.txt, caption_dir: captions.tar.gz | Yes |\n| evaluate | dataset.val.datasets | eval_dataset | image_dir: images.tar.gz, image_list_file: image_list.txt, caption_dir: captions.tar.gz | Yes |\n| inference | inference.datasets | inference_dataset | image_dir: images.tar.gz | Yes |\n| inference | inference.text_file | inference_dataset | prompts.txt | No |\n| export | export.checkpoint | parent train job or explicit checkpoint | checkpoint .pth, optional for pretrained export | No |\n| gen_trt_engine | gen_trt_engine.onnx_file | parent export job or explicit ONNX | clip_model.onnx | No |\n\nFor custom training, set `dataset.train.type: custom` and provide `dataset.train.datasets` entries. Image and caption files must share the same base name. `caption_file_suffix` defaults to `.txt`, and `image_list_file` is optional.\n\nWhen no native CLIP image-caption dataset is available, do not silently treat image-classification data as CLIP data. If the user explicitly allows a plumbing-only validation fallback, derive caption files from class labels, document that the captions are generated from labels, and keep each image\u002Fcaption pair on the same base filename. Without an `image_list_file`, the TAO custom loader scans the configured image directory for image files; keep validation folders flat unless you provide a list file.\n\nFor WDS training, set `dataset.train.type: wds` and provide at least one of `dataset.train.wds.root_dir` or `dataset.train.wds.shard_list_file`. `root_dir` is scanned recursively for `.tar` shards. `shard_list_file` is a text file with one shard path per line; relative lines resolve under the list-file directory unless `root_dir` is also supplied, in which case they resolve under `root_dir`. Validation\u002Fevaluation data remains custom format via `dataset.val.datasets`.\n\n### Typical Spec Overrides\n\nData source overrides are mandatory for dataset-backed actions. Construct paths from the Per-Action Dataset Requirements table and include them in `spec_overrides`. For inference, provide at least one of `inference.datasets` or `inference.text_file`.\n\n```python\nS3_TRAIN = \"s3:\u002F\u002Fbucket\u002Fdata\u002Ftrain\"\nS3_WDS = \"s3:\u002F\u002Fbucket\u002Fdata\u002Fwds\"\nS3_EVAL = \"s3:\u002F\u002Fbucket\u002Fdata\u002Feval\"\nS3_INFER = \"s3:\u002F\u002Fbucket\u002Fdata\u002Finfer\"\n```\n\n**train, custom dataset:**\n```python\n{\n    \"train.num_epochs\": 10,\n    \"dataset.train.type\": \"custom\",\n    \"dataset.train.datasets\": [{\"image_dir\": f\"{S3_TRAIN}\u002Fimages.tar.gz\", \"image_list_file\": f\"{S3_TRAIN}\u002Fimage_list.txt\", \"caption_dir\": f\"{S3_TRAIN}\u002Fcaptions.tar.gz\"}],\n    \"dataset.val.datasets\": [{\"image_dir\": f\"{S3_EVAL}\u002Fimages.tar.gz\", \"image_list_file\": f\"{S3_EVAL}\u002Fimage_list.txt\", \"caption_dir\": f\"{S3_EVAL}\u002Fcaptions.tar.gz\"}],\n}\n```\n\n**train, WDS dataset:**\n```python\n{\n    \"train.num_epochs\": 10,\n    \"dataset.train.type\": \"wds\",\n    \"dataset.train.wds.root_dir\": f\"{S3_WDS}\",\n    \"dataset.train.wds.shard_list_file\": f\"{S3_WDS}\u002Fshards.txt\",\n    \"dataset.train.wds.samples_per_shard\": 10000,\n    \"dataset.val.datasets\": [{\"image_dir\": f\"{S3_EVAL}\u002Fimages.tar.gz\", \"image_list_file\": f\"{S3_EVAL}\u002Fimage_list.txt\", \"caption_dir\": f\"{S3_EVAL}\u002Fcaptions.tar.gz\"}],\n}\n```\n\n**evaluate:**\n```python\n{\n    \"dataset.val.datasets\": [{\"image_dir\": f\"{S3_EVAL}\u002Fimages.tar.gz\", \"image_list_file\": f\"{S3_EVAL}\u002Fimage_list.txt\", \"caption_dir\": f\"{S3_EVAL}\u002Fcaptions.tar.gz\"}],\n}\n```\n\nLeave `evaluate.checkpoint` unset for zero-shot evaluation with pretrained weights. Set `evaluate.trt_engine` instead of `evaluate.checkpoint` for TensorRT evaluation.\n\n**inference:**\n```python\n{\n    \"inference.datasets\": [{\"image_dir\": f\"{S3_INFER}\u002Fimages.tar.gz\"}],\n    \"inference.text_file\": f\"{S3_INFER}\u002Fprompts.txt\",\n}\n```\n\nInference writes `image_embeddings.h5` and\u002For `text_embeddings.h5` under `results_dir`. The saved embeddings are L2-normalized.\n\n**export:**\n```python\n{\n    \"export.onnx_file\": \"${results_dir}\u002Fexport\u002Fclip_model.onnx\",\n    \"export.encoder_type\": \"combined\",\n    \"export.batch_size\": -1,\n}\n```\n\nSet `export.encoder_type: separate` when deployment should use independent vision and text encoders. Separate export writes `_vision.onnx` and `_text.onnx` variants derived from the base `export.onnx_file`.\n\nFor checkpoint-dependent actions, use the model-specific checkpoint resolver output from the parent train job. CLIP training writes checkpoints such as `model_epoch_000_step_00020.pth` and a `clip_latest.pth` symlink. Use the exact resolved checkpoint for `evaluate.checkpoint`, `inference.checkpoint`, `export.checkpoint`, and `train.resume_training_checkpoint_path`; use `clip_latest.pth` only when the user explicitly asks for latest.\n\nWhen the resolved checkpoint is trusted TAO output, checkpoint-backed PyTorch `evaluate`, `inference`, `export`, and resume training should run with `TORCH_FORCE_NO_WEIGHTS_ONLY_LOAD=1`. PyTorch 2.6 otherwise defaults checkpoint loading to weights-only mode and can reject CLIP Lightning checkpoints containing NumPy scalar metadata.\n\n**gen_trt_engine:**\n```python\n{\n    \"gen_trt_engine.onnx_file\": \"${results_dir}\u002Fexport\u002Fclip_model.onnx\",\n    \"gen_trt_engine.trt_engine\": \"${results_dir}\u002Fdeploy\u002Fclip_model.engine\",\n    \"gen_trt_engine.batch_size\": -1,\n    \"gen_trt_engine.tensorrt.data_type\": \"fp16\",\n    \"gen_trt_engine.tensorrt.min_batch_size\": 1,\n    \"gen_trt_engine.tensorrt.opt_batch_size\": 1,\n    \"gen_trt_engine.tensorrt.max_batch_size\": 16,\n}\n```\n\n## Eval Dataset\n\nOptional for training. If provided, validation metrics are computed at validation intervals. Required for `evaluate`.\n\n## Deploy Workflow\n\nThe skill exposes `gen_trt_engine` as the deploy action. In generated SDK runners, use `model_info[\"actions\"][\"gen_trt_engine\"]` and run it in the TAO Deploy image, not the PyTorch training image. The in-container command is `clip gen_trt_engine -e {config_path}`; direct TAO Launcher usage spells the same action as `tao deploy clip gen_trt_engine -e \u002Fpath\u002Fto\u002Fspec.yaml`.\n\nTAO Deploy inference can discover combined engines, paired separate engines, or single-pillar `_vision.engine` \u002F `_text.engine` files. For full TensorRT retrieval evaluation or image+text TensorRT inference, export with `export.encoder_type: separate` and run `clip gen_trt_engine` twice: build `clip_model_vision.onnx` to an engine ending in `_vision.engine`, then build `clip_model_text.onnx` to the matching `_text.engine` in the same directory. For image-only TensorRT inference, building only the `_vision.engine` is sufficient and `inference.text_file` must be `null`. TensorRT `evaluate` and text inference require a text-capable engine; if only a vision engine is present, deploy evaluation fails because text embeddings cannot be extracted.\n\nUse `evaluate.trt_engine` for TensorRT evaluation and `inference.trt_engine` for TensorRT embedding extraction. These TensorRT paths also run in the TAO Deploy image. Direct TAO Launcher usage spells these as `tao deploy clip evaluate` and `tao deploy clip inference`.\n\n## Important Parameters\n\n- **model.type**: Backbone family and resolution. Use a TAO-registered CLIP model ID such as `ViT-L-14-SigLIP-CLIPA-224`. Prefer the listed OpenCLIP \u002F NV-CLIP IDs for AutoML smoke tests because the current TAO container registry routes them through the supported augmentation adapter.\n- **model.adaptor_name**: Required for Radio-CLIP. Set to `siglip` or `clip`.\n- **model.image_size**: Training transform image resolution. Keep it aligned with the selected fixed-resolution backbone.\n- **train.num_epochs**: CLIP fine-tuning often converges quickly. Start with 10-20 epochs for domain adaptation, then increase only if validation loss is still improving.\n- **train.optim.vision_lr \u002F train.optim.text_lr**: Learning rates for the two encoders. CLIP is sensitive to high learning rates; reduce both if loss is unstable.\n- **model.freeze_vision_encoder \u002F model.freeze_text_encoder**: Defaults are false. Freezing one encoder can help when the dataset is small or only one modality needs adaptation.\n- **train.loss_type**: `siglip` is recommended for SigLIP2 and Radio-CLIP. Use `clip` for CLIP-style softmax loss.\n- **export.encoder_type**: `combined` exports one ONNX graph. `separate` exports independent vision and text graphs.\n- **gen_trt_engine.tensorrt.data_type**: TensorRT deployment supports `fp16` and `fp32`.\n\n## Hardware\n\nSingle-GPU training works for small datasets. Use 4+ GPUs for datasets with more than 100k images or large backbones. Use 16GB+ VRAM per GPU for small\u002Ffixed-resolution runs and larger GPUs for Radio-CLIP or high-resolution OpenCLIP variants.\n\n## Error Patterns\n\nSee `references\u002Ferror-patterns.md` for the full list of CLIP error symptoms and fixes (CUDA OOM, NaN loss, retrieval quality, dataset format\u002Fsize, Radio-CLIP and model-ID validation, ONNX external data, TensorRT shape mismatch, PyTorch 2.6 checkpoint load, null-checkpoint inference, TensorRT text\u002Fretrieval failures, `attention_mask` handling, and spec\u002Fschema merge errors).\n\n## Spec Param \u002F Parent Model Inference\n\nSee `references\u002Fspec-param-inference.md` for the model-specific inference mappings (the full `clip.config.json` action\u002Fspec-field\u002Finference-function table) that generated runners apply with SDK helpers before `create_job()`, plus `parent_job_id` resolution rules.\n\n## Deployment\n\n- [tao-deploy-clip](references\u002Ftao-deploy-clip.md)\n","# CLIP\n\nContrastive Language-Image Pre-training model for zero-shot and fine-tuned image classification, image-text retrieval, and embedding extraction. Fine-tuning adapts CLIP's shared image-text embedding space to domain-specific image-caption data.\n\nNo default NGC pretrained checkpoint is required for spec construction, but unset checkpoint behavior is action-specific. In the validation-fixes PyTorch image, `export.checkpoint: null` exports the selected CLIP architecture and may initialize weights when pretrained weights are unavailable. Do not assume `inference.checkpoint: null` loads pretrained weights: `clip inference` currently calls the checkpoint loader with `None` and fails before embedding extraction. For PyTorch inference, checkpoint-backed evaluation\u002Fexport, resume, and retrain flows, resolve and pass an exact checkpoint from the parent train output. For trusted TAO checkpoints produced by the current run or a known parent job, set `TORCH_FORCE_NO_WEIGHTS_ONLY_LOAD=1` on checkpoint-dependent PyTorch actions so PyTorch 2.6 can load the Lightning checkpoint metadata; do not set this for untrusted checkpoints.\n\nSupported actions: `train`, `evaluate`, `inference`, `export`, `gen_trt_engine`.\n\n## Train Action Policy\n\nThis model is AutoML-enabled at the model layer. Before handling any train-stage request, read `references\u002Fskill_info.yaml` and resolve the run override from either an explicit `automl_policy` value or the user's workflow request. Use `automl_policy: on` by default and only expose `on` \u002F `off` in new launch prompts. Treat phrases like \"turn off AutoML\", \"disable AutoML\", \"no HPO\", or \"plain training\" as `automl_policy: off` for this run only. When `automl_policy: on`, `automl_enabled: true`, and both `schemas\u002Ftrain.schema.json` and `references\u002Fspec_template_train.yaml` are packaged, route the train action through `tao-skill-bank:tao-run-automl` by default with this model's `skill_dir`. Preserve workflow\u002Fapplication overrides for datasets, specs, output directories, GPU\u002Fplatform settings, parent checkpoints, and `automl_policy`. Use direct model training only when `automl_policy: off` or the packaged train schema\u002Ftemplate is missing; in the missing-schema case, report that AutoML is enabled but not runnable for this model until schemas are generated.\n\nThe packaged CLIP train schema enables `train.optim.vision_lr` and `train.optim.text_lr` as default AutoML search parameters. For smoke tests, keep the search small by using the Bayesian algorithm with two recommendations and narrow LR ranges.\n\nNon-train actions such as `evaluate`, `inference`, `export`, and deploy flows stay in this model skill. The per-run `automl_policy` override does not change model metadata.\n\n## Instructions\n\nUse this skill for NVIDIA TAO CLIP jobs: training, evaluation, embedding inference, ONNX export, and TensorRT engine generation. Start by identifying the requested action, then load only the referenced files needed for that action: `defaults.json` for default parameters, `config.json` for action\u002Fdata-source wiring, `references\u002Fspec_template.yaml` for full spec shape, and `references\u002Fmodel_info.yaml` for SDK metadata.\n\nFor dataset-backed actions, collect the required image, caption, list, or prompt files from the user and place the resolved paths in `spec_overrides`. For local Docker runs, mount extracted folders in the container and point `image_dir` \u002F `caption_dir` at those folders; if a data source provides `.tar.gz` archives, extract them before running the in-container CLIP commands. For `export` and `gen_trt_engine`, infer parent artifacts from the upstream job when available; otherwise require explicit checkpoint, ONNX, or engine paths. Run `gen_trt_engine`, TensorRT `evaluate`, and TensorRT `inference` in the TAO Deploy image.\n\nFor TAO Deploy TensorRT actions (`gen_trt_engine`, TensorRT `evaluate`, and TensorRT `inference`), read `references\u002Ftao-deploy-clip.md` first. Deploy spec templates live in this skill's `references\u002F` folder with the `spec_template_deploy_*.yaml` prefix.\n\n## Training Requirements\n\n- **Dataset type:** image_text\n- **Formats:** custom image\u002Fcaption folders or WebDataset shards\n- **Monitoring metric:** val\u002Ft2i_mAP\n\n### Supported Models\n\n- **OpenCLIP \u002F NV-CLIP:** `ViT-L-14-SigLIP-CLIPA-224` (default), `ViT-L-14-SigLIP-CLIPA-336`, `ViT-H-14-SigLIP-CLIPA-224`, `ViT-H-14-SigLIP-CLIPA-336`, `ViT-H-14-SigLIP-CLIPA-574`\n- **Radio-CLIP:** `c-radio_v3-b`, `c-radio_v3-l`, `c-radio_v3-h`, `c-radio_v3-g`\n- **SigLIP2:** `siglip2-so400m-patch16-256`, `siglip2-so400m-patch14-224`, `siglip2-so400m-patch14-384`, `siglip2-so400m-patch16-384`, `siglip2-so400m-patch16-512`, `siglip2-so400m-patch16-naflex`\n\nRadio-CLIP requires `model.adaptor_name` to be set to `siglip` or `clip`.\n\n### Per-Action Dataset Requirements\n\n| Action | Spec Key | Source | Files | List? |\n|---|---|---|---|---|\n| train | dataset.train.datasets | train_datasets | image_dir: images.tar.gz, image_list_file: image_list.txt, caption_dir: captions.tar.gz | Yes |\n| train | dataset.train.wds.root_dir | train_wds_dataset | root directory containing `.tar` shards | No |\n| train | dataset.train.wds.shard_list_file | train_wds_dataset | shards.txt listing shard paths | No |\n| train | dataset.val.datasets | eval_dataset | image_dir: images.tar.gz, image_list_file: image_list.txt, caption_dir: captions.tar.gz | Yes |\n| evaluate | dataset.val.datasets | eval_dataset | image_dir: images.tar.gz, image_list_file: image_list.txt, caption_dir: captions.tar.gz | Yes |\n| inference | inference.datasets | inference_dataset | image_dir: images.tar.gz | Yes |\n| inference | inference.text_file | inference_dataset | prompts.txt | No |\n| export | export.checkpoint | parent train job or explicit checkpoint | checkpoint .pth, optional for pretrained export | No |\n| gen_trt_engine | gen_trt_engine.onnx_file | parent export job or explicit ONNX | clip_model.onnx | No |\n\nFor custom training, set `dataset.train.type: custom` and provide `dataset.train.datasets` entries. Image and caption files must share the same base name. `caption_file_suffix` defaults to `.txt`, and `image_list_file` is optional.\n\nWhen no native CLIP image-caption dataset is available, do not silently treat image-classification data as CLIP data. If the user explicitly allows a plumbing-only validation fallback, derive caption files from class labels, document that the captions are generated from labels, and keep each image\u002Fcaption pair on the same base filename. Without an `image_list_file`, the TAO custom loader scans the configured image directory for image files; keep validation folders flat unless you provide a list file.\n\nFor WDS training, set `dataset.train.type: wds` and provide at least one of `dataset.train.wds.root_dir` or `dataset.train.wds.shard_list_file`. `root_dir` is scanned recursively for `.tar` shards. `shard_list_file` is a text file with one shard path per line; relative lines resolve under the list-file directory unless `root_dir` is also supplied, in which case they resolve under `root_dir`. Validation\u002Fevaluation data remains custom format via `dataset.val.datasets`.\n\n### Typical Spec Overrides\n\nData source overrides are mandatory for dataset-backed actions. Construct paths from the Per-Action Dataset Requirements table and include them in `spec_overrides`. For inference, provide at least one of `inference.datasets` or `inference.text_file`.\n\n```python\nS3_TRAIN = \"s3:\u002F\u002Fbucket\u002Fdata\u002Ftrain\"\nS3_WDS = \"s3:\u002F\u002Fbucket\u002Fdata\u002Fwds\"\nS3_EVAL = \"s3:\u002F\u002Fbucket\u002Fdata\u002Feval\"\nS3_INFER = \"s3:\u002F\u002Fbucket\u002Fdata\u002Finfer\"\n```\n\n**train, custom dataset:**\n```python\n{\n    \"train.num_epochs\": 10,\n    \"dataset.train.type\": \"custom\",\n    \"dataset.train.datasets\": [{\"image_dir\": f\"{S3_TRAIN}\u002Fimages.tar.gz\", \"image_list_file\": f\"{S3_TRAIN}\u002Fimage_list.txt\", \"caption_dir\": f\"{S3_TRAIN}\u002Fcaptions.tar.gz\"}],\n    \"dataset.val.datasets\": [{\"image_dir\": f\"{S3_EVAL}\u002Fimages.tar.gz\", \"image_list_file\": f\"{S3_EVAL}\u002Fimage_list.txt\", \"caption_dir\": f\"{S3_EVAL}\u002Fcaptions.tar.gz\"}],\n}\n```\n\n**train, WDS dataset:**\n```python\n{\n    \"train.num_epochs\": 10,\n    \"dataset.train.type\": \"wds\",\n    \"dataset.train.wds.root_dir\": f\"{S3_WDS}\",\n    \"dataset.train.wds.shard_list_file\": f\"{S3_WDS}\u002Fshards.txt\",\n    \"dataset.train.wds.samples_per_shard\": 10000,\n    \"dataset.val.datasets\": [{\"image_dir\": f\"{S3_EVAL}\u002Fimages.tar.gz\", \"image_list_file\": f\"{S3_EVAL}\u002Fimage_list.txt\", \"caption_dir\": f\"{S3_EVAL}\u002Fcaptions.tar.gz\"}],\n}\n```\n\n**evaluate:**\n```python\n{\n    \"dataset.val.datasets\": [{\"image_dir\": f\"{S3_EVAL}\u002Fimages.tar.gz\", \"image_list_file\": f\"{S3_EVAL}\u002Fimage_list.txt\", \"caption_dir\": f\"{S3_EVAL}\u002Fcaptions.tar.gz\"}],\n}\n```\n\nLeave `evaluate.checkpoint` unset for zero-shot evaluation with pretrained weights. Set `evaluate.trt_engine` instead of `evaluate.checkpoint` for TensorRT evaluation.\n\n**inference:**\n```python\n{\n    \"inference.datasets\": [{\"image_dir\": f\"{S3_INFER}\u002Fimages.tar.gz\"}],\n    \"inference.text_file\": f\"{S3_INFER}\u002Fprompts.txt\",\n}\n```\n\nInference writes `image_embeddings.h5` and\u002For `text_embeddings.h5` under `results_dir`. The saved embeddings are L2-normalized.\n\n**export:**\n```python\n{\n    \"export.onnx_file\": \"${results_dir}\u002Fexport\u002Fclip_model.onnx\",\n    \"export.encoder_type\": \"combined\",\n    \"export.batch_size\": -1,\n}\n```\n\nSet `export.encoder_type: separate` when deployment should use independent vision and text encoders. Separate export writes `_vision.onnx` and `_text.onnx` variants derived from the base `export.onnx_file`.\n\nFor checkpoint-dependent actions, use the model-specific checkpoint resolver output from the parent train job. CLIP training writes checkpoints such as `model_epoch_000_step_00020.pth` and a `clip_latest.pth` symlink. Use the exact resolved checkpoint for `evaluate.checkpoint`, `inference.checkpoint`, `export.checkpoint`, and `train.resume_training_checkpoint_path`; use `clip_latest.pth` only when the user explicitly asks for latest.\n\nWhen the resolved checkpoint is trusted TAO output, checkpoint-backed PyTorch `evaluate`, `inference`, `export`, and resume training should run with `TORCH_FORCE_NO_WEIGHTS_ONLY_LOAD=1`. PyTorch 2.6 otherwise defaults checkpoint loading to weights-only mode and can reject CLIP Lightning checkpoints containing NumPy scalar metadata.\n\n**gen_trt_engine:**\n```python\n{\n    \"gen_trt_engine.onnx_file\": \"${results_dir}\u002Fexport\u002Fclip_model.onnx\",\n    \"gen_trt_engine.trt_engine\": \"${results_dir}\u002Fdeploy\u002Fclip_model.engine\",\n    \"gen_trt_engine.batch_size\": -1,\n    \"gen_trt_engine.tensorrt.data_type\": \"fp16\",\n    \"gen_trt_engine.tensorrt.min_batch_size\": 1,\n    \"gen_trt_engine.tensorrt.opt_batch_size\": 1,\n    \"gen_trt_engine.tensorrt.max_batch_size\": 16,\n}\n```\n\n## Eval Dataset\n\nOptional for training. If provided, validation metrics are computed at validation intervals. Required for `evaluate`.\n\n## Deploy Workflow\n\nThe skill exposes `gen_trt_engine` as the deploy action. In generated SDK runners, use `model_info[\"actions\"][\"gen_trt_engine\"]` and run it in the TAO Deploy image, not the PyTorch training image. The in-container command is `clip gen_trt_engine -e {config_path}`; direct TAO Launcher usage spells the same action as `tao deploy clip gen_trt_engine -e \u002Fpath\u002Fto\u002Fspec.yaml`.\n\nTAO Deploy inference can discover combined engines, paired separate engines, or single-pillar `_vision.engine` \u002F `_text.engine` files. For full TensorRT retrieval evaluation or image+text TensorRT inference, export with `export.encoder_type: separate` and run `clip gen_trt_engine` twice: build `clip_model_vision.onnx` to an engine ending in `_vision.engine`, then build `clip_model_text.onnx` to the matching `_text.engine` in the same directory. For image-only TensorRT inference, building only the `_vision.engine` is sufficient and `inference.text_file` must be `null`. TensorRT `evaluate` and text inference require a text-capable engine; if only a vision engine is present, deploy evaluation fails because text embeddings cannot be extracted.\n\nUse `evaluate.trt_engine` for TensorRT evaluation and `inference.trt_engine` for TensorRT embedding extraction. These TensorRT paths also run in the TAO Deploy image. Direct TAO Launcher usage spells these as `tao deploy clip evaluate` and `tao deploy clip inference`.\n\n## Important Parameters\n\n- **model.type**: Backbone family and resolution. Use a TAO-registered CLIP model ID such as `ViT-L-14-SigLIP-CLIPA-224`. Prefer the listed OpenCLIP \u002F NV-CLIP IDs for AutoML smoke tests because the current TAO container registry routes them through the supported augmentation adapter.\n- **model.adaptor_name**: Required for Radio-CLIP. Set to `siglip` or `clip`.\n- **model.image_size**: Training transform image resolution. Keep it aligned with the selected fixed-resolution backbone.\n- **train.num_epochs**: CLIP fine-tuning often converges quickly. Start with 10-20 epochs for domain adaptation, then increase only if validation loss is still improving.\n- **train.optim.vision_lr \u002F train.optim.text_lr**: Learning rates for the two encoders. CLIP is sensitive to high learning rates; reduce both if loss is unstable.\n- **model.freeze_vision_encoder \u002F model.freeze_text_encoder**: Defaults are false. Freezing one encoder can help when the dataset is small or only one modality needs adaptation.\n- **train.loss_type**: `siglip` is recommended for SigLIP2 and Radio-CLIP. Use `clip` for CLIP-style softmax loss.\n- **export.encoder_type**: `combined` exports one ONNX graph. `separate` exports independent vision and text graphs.\n- **gen_trt_engine.tensorrt.data_type**: TensorRT deployment supports `fp16` and `fp32`.\n\n## Hardware\n\nSingle-GPU training works for small datasets. Use 4+ GPUs for datasets with more than 100k images or large backbones. Use 16GB+ VRAM per GPU for small\u002Ffixed-resolution runs and larger GPUs for Radio-CLIP or high-resolution OpenCLIP variants.\n\n## Error Patterns\n\nSee `references\u002Ferror-patterns.md` for the full list of CLIP error symptoms and fixes (CUDA OOM, NaN loss, retrieval quality, dataset format\u002Fsize, Radio-CLIP and model-ID validation, ONNX external data, TensorRT shape mismatch, PyTorch 2.6 checkpoint load, null-checkpoint inference, TensorRT text\u002Fretrieval failures, `attention_mask` handling, and spec\u002Fschema merge errors).\n\n## Spec Param \u002F Parent Model Inference\n\nSee `references\u002Fspec-param-inference.md` for the model-specific inference mappings (the full `clip.config.json` action\u002Fspec-field\u002Finference-function table) that generated runners apply with SDK helpers before `create_job()`, plus `parent_job_id` resolution rules.\n\n## Deployment\n\n- [tao-deploy-clip](references\u002Ftao-deploy-clip.md)\n",{"name":5,"tags":24,"license":15,"metadata":30,"description":7,"allowed-tools":33,"compatibility":34},[25,26,27,28,29],"vision-language","classification","embedding","zero-shot","deployment",{"author":31,"version":32},"NVIDIA Corporation","0.1.0","Read Bash","Requires docker + nvidia-container-toolkit.","main","86cc27ffd16af6cb85948f1155578e6f3f61cc4c","skillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip","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":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add Solizardking\u002Ftrain2earn --skill tao-finetune-clip",{"tool":49,"command":50},"bunx","bunx skills add Solizardking\u002Ftrain2earn --skill tao-finetune-clip",{"tool":52,"command":53},"pnpm","pnpm dlx skills add Solizardking\u002Ftrain2earn --skill tao-finetune-clip","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002FSKILL.md",true,[57,63,67,71,75,79,83,87,91,95,99,103,107,111],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"BENCHMARK.md","REFERENCE","参考文档",3924,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002FBENCHMARK.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"metadata.json",476,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002Fmetadata.json",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Ferror-patterns.md",4015,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002Freferences\u002Ferror-patterns.md",{"path":72,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fskill_info.yaml",4796,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002Freferences\u002Fskill_info.yaml",{"path":76,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fspec_template_deploy.yaml",616,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002Freferences\u002Fspec_template_deploy.yaml",{"path":80,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fspec_template_evaluate.yaml",1411,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002Freferences\u002Fspec_template_evaluate.yaml",{"path":84,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fspec_template_export.yaml",1494,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002Freferences\u002Fspec_template_export.yaml",{"path":88,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fspec_template_train.yaml",1321,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002Freferences\u002Fspec_template_train.yaml",{"path":92,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fspec_template.yaml",2078,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002Freferences\u002Fspec_template.yaml",{"path":96,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fspec-param-inference.md",2523,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002Freferences\u002Fspec-param-inference.md",{"path":100,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Ftao-deploy-clip.md",5818,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002Freferences\u002Ftao-deploy-clip.md",{"path":104,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Ftao-deploy-clip.skill_info.yaml",2195,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002Freferences\u002Ftao-deploy-clip.skill_info.yaml",{"path":108,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":109,"sourceHtmlUrl":110},"skill-card.md",3882,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002Fskill-card.md",{"path":112,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":113,"sourceHtmlUrl":114},"verification.json",3214,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Ftao-finetune-clip\u002Fverification.json",[116,124,132,140,147,155],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":120,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":120,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"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":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":120,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"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":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":120,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"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":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":151,"sourceHtmlUrl":152,"categories":153,"keywords":154,"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":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":120,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"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",[],[]]