[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PSD4AEQ6TPK5CWQ5T0MSP5":3,"skill-same:01M6PSD4AEQ6TPK5CWQ5T0MSP5":96},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":14,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6PSD4AEQ6TPK5CWQ5T0MSP5","tao-launch-workflow",null,"Shared launch intake for any TAO workflow or action. Use when the user wants to run TAO AutoML, train, evaluate, infer, export, generate TensorRT engines, or launch DEFT\u002Fworkflow jobs on an execution platform.","headmktlucca-ui\u002Fneuroads-lp","headmktlucca-ui","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F247379838?v=4","01M6PDVAV6M1W96D1SR1PDF8CS","NeuroAds","01M6PDVAZ4P281GNDKD45CYTF5",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftao-launch-workflow\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"launch","tao launch workflow","tao","workflow","platform","generate","evaluate","for","bank","helper","scripts","infer","run","shared","use","read","Bash","execution","NVIDIA","intake","2026-11-10 10:12:30",false,"---\nname: tao-launch-workflow\ndescription: >-\n  Shared launch intake for any TAO workflow or action. Use when the user wants\n  to run TAO AutoML, train, evaluate, infer, export, generate TensorRT engines,\n  or launch DEFT\u002Fworkflow jobs on an execution platform.\nlicense: Apache-2.0\ncompatibility: Requires the packaged TAO skill bank helper scripts.\nmetadata:\n  author: NVIDIA Corporation\n  version: \"0.1.0\"\nallowed-tools: Read Bash\ntags:\n- tao\n- workflow\n- launch\n---\n\n# TAO Workflow Launch Intake\n\nUse this skill before launching any TAO workflow or model action.\n\n## Quick Start\n\nRun the platform helper, ask for platform and monitoring preferences, then run\nthe selected platform detail helper before asking for credentials.\n\n## Non-Negotiable Launch Gate\n\nDo **not** create runner scripts, launch scripts, compatibility shims,\nworkspace folders, state files, logs, or dependency-install side effects until\nthe launch preflight passes.\n\nPreflight passes only after all of these are true:\n\n1. The execution platform is selected from the packaged platform helper.\n2. Platform credentials and required credential groups are satisfied.\n3. Model-specific credentials are satisfied.\n4. The default container image is resolved from packaged model\u002Faction metadata,\n   shown to the user, and either confirmed or replaced by an explicit\n   `image=\u003Coverride>`.\n5. The platform access check succeeds from the launch host.\n6. Dataset inputs are mapped to concrete spec keys and verified from the\n   selected platform's point of view.\n7. Required compute shape fields from the model\u002Fworkflow skill are known.\n\nIf any item is missing, ask for the missing input and stop before generating\nartifacts. This applies to AutoML, normal train\u002Feval\u002Finfer\u002Fexport\u002FTRT, and\nDEFT\u002Fapplication workflows.\n\n## Initial Questions\n\nAfter the user confirms what they want to do, ask for the execution platform\nusing the packaged helper. Do not scan platform docs, skill folders, or config\nfolders to build the choices.\n\n```bash\n${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external}\u002Fscripts\u002Flist_tao_platforms.py \\\n  --skill-bank ${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external} --format text\n```\n\nThen ask:\n\n- Which supported platform should run this workflow?\n- Should I monitor the run in this chat? Monitoring means I keep polling the\n  backend\u002Fjob logs after launch and report progress until the job finishes,\n  fails, or you ask me to stop, even if the job stays queued for hours or days.\n  If disabled, I launch the job, give you the job id\u002Flog path, and stop\n  polling. Default: monitor in chat.\n- How often should I post status? Default: every 5 minutes. Use 1-2 minutes for\n  smoke tests, 5 minutes for normal training, or 10-15 minutes for long runs.\n\nUse `long_running_enabled=true` and `status_interval_minutes=5` when the user\naccepts the defaults.\n\nWhen monitoring is enabled, do not send a final summary just because several\npolls have elapsed or the job is still `PENDING`. Keep the turn attached and\nemit status every `status_interval_minutes` until a terminal state or explicit\nuser stop\u002Fdetach request. If the runtime environment cannot keep the chat turn\nopen, say that clearly and leave a durable watcher\u002Flog path; do not imply that\nchat updates will continue after the turn ends.\n\nFinal-answer rule: a `final` response ends chat-side monitoring. While\n`long_running_enabled=true` and any launched job is non-terminal, status\nmessages must be sent as in-progress updates and the agent must continue\npolling. Only send a final response when the workflow reaches terminal state,\nthe user explicitly asks to detach\u002Fstop monitoring, or the runtime genuinely\ncannot keep the turn open; in that last case, say it is a runtime limitation\nand provide the exact durable status command\u002Flog path.\n\n## Missing-Input Prompt Shape\n\nWhen asking for launch inputs, include concrete examples and both dataset input\nmodes. Do not ask only for \"dataset root\".\n\nUse this structure and adapt spec keys to the selected model\u002Faction:\n\n```text\nI need these launch inputs before I can create specs or runner files:\n\n1. Execution platform: lepton, brev, slurm, local-docker, or kubernetes.\n\n2. Dataset inputs. You can provide either mode:\n   A) Root mode: give train\u002Feval roots and I map required files automatically.\n      Example Cosmos-RL:\n      train_root=\u002Flustre\u002Ffsw\u002F...\u002Fcosmos\u002Ftrain\n      -> custom.train_dataset.annotation_path=train_root\u002Fannotations.json\n      -> custom.train_dataset.media_path=train_root\n   B) Direct spec mode: give the exact config\u002Fspec parameters yourself.\n      Example:\n      custom.train_dataset.annotation_path=\u002Flustre\u002Ffsw\u002F...\u002Ftrain_annotations.json\n      custom.train_dataset.media_path=\u002Flustre\u002Ffsw\u002F...\u002Fvideos_train.tar.gz\n      custom.val_dataset.annotation_path=\u002Flustre\u002Ffsw\u002F...\u002Feval_annotations.json\n      custom.val_dataset.media_path=\u002Flustre\u002Ffsw\u002F...\u002Feval_videos\u002F\n\n   Platform examples:\n   - SLURM\u002FLustre: \u002Flustre\u002Ffsw\u002F...\u002Fdata\u002Ftrain or lustre:\u002F\u002F\u002Flustre\u002Ffsw\u002F...\u002Fdata\u002Ftrain\n   - Lepton\u002FBrev\u002FKubernetes: s3:\u002F\u002Fbucket\u002Fpath\u002Ftrain and s3:\u002F\u002Fbucket\u002Fpath\u002Feval\n   - local-docker: \u002Fdata\u002Ftao\u002F\u003Cmodel>\u002Ftrain or file:\u002F\u002F\u002Fdata\u002Ftao\u002F\u003Cmodel>\u002Feval\n\n3. Container image. I will resolve the default from packaged model metadata and\n   show it before launch, for example:\n   default image for \u003Cmodel>\u002F\u003Caction>: \u003Cresolved container image>\n   Use this image, or provide image=\u003Coverride> to pin a different TAO build.\n\n4. Compute shape required by the model, for example GPUs\u002Fnodes.\n\n5. Required credentials from platform\u002Fmodel docs, for example HF_TOKEN for\n   gated Hugging Face models.\n\n6. Monitoring preference. By default I monitor in this chat and post progress\n   every 5 minutes; choose 1-2 minutes for smoke tests or 10-15 minutes for\n   long training.\n```\n\n## Container Image Confirmation\n\nBefore creating specs, runner scripts, workspaces, logs, state files, or\nsubmitting a job, resolve the image for the selected model\u002Faction:\n\n```bash\n${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external}\u002Fscripts\u002Fresolve_tao_image.py \\\n  --skill-bank ${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external} \\\n  --model \u003Cnetwork> --action \u003Caction> --format text\n```\n\nIf the helper is unavailable, read `skills\u002Fmodels\u002F\u003Cnetwork>\u002Fconfig.json` through\n`SkillBank().get_model_config(network_arch)`. Resolve image fields in this\norder:\n\n1. `actions.\u003Caction>.container_image`\n2. `actions.\u003Caction>.image`\n3. top-level `container_image`\n4. top-level `image`\n\nShow the exact image and ask:\n\n```text\nContainer image for \u003Cnetwork>\u002F\u003Caction>:\ndefault=\u003Cresolved image>\n\nUse this image, or provide image=\u003Coverride>?\n```\n\nIf the user accepts, pass the resolved image as the job `image`. If the user\noverrides, require a non-empty image reference and pass that value instead.\nDo not silently launch on the default image. This confirmation applies to\ntraining, AutoML recommendations, evaluation, inference, export, TensorRT\nengine generation, and application workflows that submit TAO containers.\n\n## Credential Filtering\n\nAfter the user chooses a platform, get the credential list for only that\nplatform:\n\n```bash\n${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external}\u002Fscripts\u002Flist_tao_platforms.py \\\n  --skill-bank ${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external} \\\n  --platform \u003Cplatform> --format text\n```\n\nAsk only for credentials returned by that command, plus model-specific\ncredentials from the selected model skill. Do not ask for Lepton credentials on\nSLURM, Kubernetes, or local Docker. Do not ask for SLURM credentials on Lepton,\nBrev, Kubernetes, or local Docker. Ask S3 credentials only when the selected\nplatform and the dataset\u002Fresult URIs require `s3:\u002F\u002F` access.\n\nFor initial launch intake, ask for required credentials and required credential\ngroups only. Treat the helper's optional credentials\u002Fsettings section as\nreference material; do not request those values unless their `only_when`\ncondition applies, the selected workflow cannot proceed without them, or the\nuser asks to customize that setting.\n\nWhen the helper output includes a \"Required credential groups\" section, satisfy\none credential from each group before proceeding. Explain each requested value\nusing the helper's description and \"How to get it\" text.\n\nFor SLURM, user-facing prompts should ask for `SSH_KEY_PATH` first. Mention\n`SSH_AUTH_SOCK` only if the user says they already use an SSH agent.\n\n## Dataset Intake\n\nAccept dataset inputs in either mode:\n\n- **Dataset root mode:** the user gives train\u002Feval\u002Fcalibration roots, and the\n  model skill maps required files by convention. Example for Cosmos-RL train:\n  `custom.train_dataset.annotation_path=\u003Croot>\u002Fannotations.json` and\n  `custom.train_dataset.media_path=\u003Croot>`.\n- **Direct spec mode:** the user gives exact spec-key paths when annotations,\n  media archives, videos, or image folders live in different places. Preserve\n  those keys directly, for example\n  `custom.train_dataset.annotation_path=\u002Flustre\u002F...\u002Ftrain_annotations.json`\n  and `custom.train_dataset.media_path=\u002Flustre\u002F...\u002Fvideos.tar.gz`.\n\nAsk for dataset examples that match the selected platform:\n\n- SLURM: shared cluster paths such as\n  `\u002Flustre\u002Ffsw\u002Fportfolios\u002F\u003Cteam>\u002F\u003Cyour-dir>\u002Fdata\u002F\u003Cmodel>\u002Ftrain` (where\n  `\u003Cyour-dir>` is your per-user directory on the cluster), or direct spec\n  paths under `\u002Flustre\u002F...`.\n- Lepton, Brev, Kubernetes: usually `s3:\u002F\u002Fbucket\u002Fpath\u002Ftrain` and\n  `s3:\u002F\u002Fbucket\u002Fpath\u002Feval` unless the platform profile mounts shared storage.\n- Local Docker: local paths visible to the Docker host, such as\n  `\u002Fdata\u002Ftao\u002F\u003Cmodel>\u002Ftrain`, or direct spec paths visible inside the planned\n  container mount.\n\nDo not assume \"dataset root\" is the only acceptable input. When direct spec\npaths are supplied, validate the exact spec paths rather than appending default\nfilenames.\n\n## Platform Preflight\n\nRun the selected platform's preflight checks before any launch artifact is\ncreated.\n\nPrefer the packaged preflight helper when the needed inputs are available:\n\n```bash\n${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external}\u002Fscripts\u002Fcheck_tao_launch_preflight.py \\\n  --skill-bank ${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external} \\\n  --platform \u003Cplatform> \\\n  --path train_annotation=\u003Cpath> \\\n  --path train_media=\u003Cpath>\n```\n\nPass exact direct spec paths when the user supplied them. For root-mode inputs,\nexpand model-required files first, then pass those concrete annotation\u002Fmedia\npaths to the helper.\n\nWhen a model skill lists annotation-level required fields, pass them with\n`--json-required-field \u003Cpath-label>=\u003Cfield>[,\u003Cfield>...]` so schema\u002Fdata\ncontent issues fail during preflight rather than inside the first training\ncontainer. For example, Cosmos-RL train\u002FAutoML requires\n`--json-required-field train_annotation=video_fps` and\n`--json-required-field val_annotation=video_fps`.\n\nDo not use `--skip-platform-access` for a real launch. That flag is only for\ndry environment checks or for cases where the user has already provided explicit\nmanual proof of platform and storage access. If the helper cannot verify remote\nAPI, CLI, cluster, or object-store access, treat preflight as failed and do not\ngenerate launch artifacts.\n\nFor SLURM:\n\n1. Require `SLURM_USER`, `SLURM_HOSTNAME`, `SLURM_PARTITION`, and one of\n   `SSH_KEY_PATH` or `SSH_AUTH_SOCK`.\n   Use the selected platform helper's `Resource defaults` for runtime values.\n   For the packaged SLURM defaults, generate launchers with\n   `SLURM_TIME_HOURS=4` and `SLURM_TIMEOUT_HOURS=3.8`; never invent a\n   12-hour default for the 4-hour partition list.\n   Launching the orchestrator with `nohup` or in the background is allowed for\n   durability, but it does not satisfy chat monitoring by itself. After launch,\n   keep a foreground chat-side polling loop attached until terminal state or\n   explicit detach.\n2. Split comma-separated `SLURM_HOSTNAME`, resolve hosts where possible, and\n   require passwordless `ssh -o BatchMode=yes` to at least one host.\n3. If SSH fails, do not offer several equivalent choices. Ask for\n   `SSH_KEY_PATH=\u002Fpath\u002Fto\u002Fprivate_key` and show the passwordless setup steps:\n   create a key if needed with\n   `ssh-keygen -t ed25519 -N \"\" -f ~\u002F.ssh\u002Fid_ed25519`; install it with\n   `ssh-copy-id -i ~\u002F.ssh\u002Fid_ed25519.pub \u003CSLURM_USER>@\u003Clogin-host>`; trust the\n   host with `ssh-keyscan -H \u003Clogin-host> >> ~\u002F.ssh\u002Fknown_hosts`; set\n   `chmod 600 ~\u002F.ssh\u002Fid_ed25519`; verify with\n   `ssh -o BatchMode=yes -i ~\u002F.ssh\u002Fid_ed25519 \u003CSLURM_USER>@\u003Clogin-host> 'hostname'`;\n   then rerun with `SSH_KEY_PATH=~\u002F.ssh\u002Fid_ed25519`.\n4. After SSH passes, validate dataset annotation\u002Fmedia paths on the remote login\n   host with `test -e` or an equivalent read-only command.\n5. Only then create runner scripts, specs, workspaces, or submit jobs.\n\nFor local Docker, validate Docker\u002FGPU access and local dataset paths before\nwriting launch artifacts. For Lepton, Brev, and Kubernetes, validate API or\ncluster access plus object-storage credentials and `aws s3 ls` readability for\n`s3:\u002F\u002F` inputs before writing launch artifacts. For mounted shared-storage or\nPVC paths on those remote platforms, require manual proof that the path is\nmounted into the job environment; the helper fails closed rather than accepting\nunverified remote mount paths.\n","# TAO Workflow Launch Intake\n\nUse this skill before launching any TAO workflow or model action.\n\n## Quick Start\n\nRun the platform helper, ask for platform and monitoring preferences, then run\nthe selected platform detail helper before asking for credentials.\n\n## Non-Negotiable Launch Gate\n\nDo **not** create runner scripts, launch scripts, compatibility shims,\nworkspace folders, state files, logs, or dependency-install side effects until\nthe launch preflight passes.\n\nPreflight passes only after all of these are true:\n\n1. The execution platform is selected from the packaged platform helper.\n2. Platform credentials and required credential groups are satisfied.\n3. Model-specific credentials are satisfied.\n4. The default container image is resolved from packaged model\u002Faction metadata,\n   shown to the user, and either confirmed or replaced by an explicit\n   `image=\u003Coverride>`.\n5. The platform access check succeeds from the launch host.\n6. Dataset inputs are mapped to concrete spec keys and verified from the\n   selected platform's point of view.\n7. Required compute shape fields from the model\u002Fworkflow skill are known.\n\nIf any item is missing, ask for the missing input and stop before generating\nartifacts. This applies to AutoML, normal train\u002Feval\u002Finfer\u002Fexport\u002FTRT, and\nDEFT\u002Fapplication workflows.\n\n## Initial Questions\n\nAfter the user confirms what they want to do, ask for the execution platform\nusing the packaged helper. Do not scan platform docs, skill folders, or config\nfolders to build the choices.\n\n```bash\n${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external}\u002Fscripts\u002Flist_tao_platforms.py \\\n  --skill-bank ${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external} --format text\n```\n\nThen ask:\n\n- Which supported platform should run this workflow?\n- Should I monitor the run in this chat? Monitoring means I keep polling the\n  backend\u002Fjob logs after launch and report progress until the job finishes,\n  fails, or you ask me to stop, even if the job stays queued for hours or days.\n  If disabled, I launch the job, give you the job id\u002Flog path, and stop\n  polling. Default: monitor in chat.\n- How often should I post status? Default: every 5 minutes. Use 1-2 minutes for\n  smoke tests, 5 minutes for normal training, or 10-15 minutes for long runs.\n\nUse `long_running_enabled=true` and `status_interval_minutes=5` when the user\naccepts the defaults.\n\nWhen monitoring is enabled, do not send a final summary just because several\npolls have elapsed or the job is still `PENDING`. Keep the turn attached and\nemit status every `status_interval_minutes` until a terminal state or explicit\nuser stop\u002Fdetach request. If the runtime environment cannot keep the chat turn\nopen, say that clearly and leave a durable watcher\u002Flog path; do not imply that\nchat updates will continue after the turn ends.\n\nFinal-answer rule: a `final` response ends chat-side monitoring. While\n`long_running_enabled=true` and any launched job is non-terminal, status\nmessages must be sent as in-progress updates and the agent must continue\npolling. Only send a final response when the workflow reaches terminal state,\nthe user explicitly asks to detach\u002Fstop monitoring, or the runtime genuinely\ncannot keep the turn open; in that last case, say it is a runtime limitation\nand provide the exact durable status command\u002Flog path.\n\n## Missing-Input Prompt Shape\n\nWhen asking for launch inputs, include concrete examples and both dataset input\nmodes. Do not ask only for \"dataset root\".\n\nUse this structure and adapt spec keys to the selected model\u002Faction:\n\n```text\nI need these launch inputs before I can create specs or runner files:\n\n1. Execution platform: lepton, brev, slurm, local-docker, or kubernetes.\n\n2. Dataset inputs. You can provide either mode:\n   A) Root mode: give train\u002Feval roots and I map required files automatically.\n      Example Cosmos-RL:\n      train_root=\u002Flustre\u002Ffsw\u002F...\u002Fcosmos\u002Ftrain\n      -> custom.train_dataset.annotation_path=train_root\u002Fannotations.json\n      -> custom.train_dataset.media_path=train_root\n   B) Direct spec mode: give the exact config\u002Fspec parameters yourself.\n      Example:\n      custom.train_dataset.annotation_path=\u002Flustre\u002Ffsw\u002F...\u002Ftrain_annotations.json\n      custom.train_dataset.media_path=\u002Flustre\u002Ffsw\u002F...\u002Fvideos_train.tar.gz\n      custom.val_dataset.annotation_path=\u002Flustre\u002Ffsw\u002F...\u002Feval_annotations.json\n      custom.val_dataset.media_path=\u002Flustre\u002Ffsw\u002F...\u002Feval_videos\u002F\n\n   Platform examples:\n   - SLURM\u002FLustre: \u002Flustre\u002Ffsw\u002F...\u002Fdata\u002Ftrain or lustre:\u002F\u002F\u002Flustre\u002Ffsw\u002F...\u002Fdata\u002Ftrain\n   - Lepton\u002FBrev\u002FKubernetes: s3:\u002F\u002Fbucket\u002Fpath\u002Ftrain and s3:\u002F\u002Fbucket\u002Fpath\u002Feval\n   - local-docker: \u002Fdata\u002Ftao\u002F\u003Cmodel>\u002Ftrain or file:\u002F\u002F\u002Fdata\u002Ftao\u002F\u003Cmodel>\u002Feval\n\n3. Container image. I will resolve the default from packaged model metadata and\n   show it before launch, for example:\n   default image for \u003Cmodel>\u002F\u003Caction>: \u003Cresolved container image>\n   Use this image, or provide image=\u003Coverride> to pin a different TAO build.\n\n4. Compute shape required by the model, for example GPUs\u002Fnodes.\n\n5. Required credentials from platform\u002Fmodel docs, for example HF_TOKEN for\n   gated Hugging Face models.\n\n6. Monitoring preference. By default I monitor in this chat and post progress\n   every 5 minutes; choose 1-2 minutes for smoke tests or 10-15 minutes for\n   long training.\n```\n\n## Container Image Confirmation\n\nBefore creating specs, runner scripts, workspaces, logs, state files, or\nsubmitting a job, resolve the image for the selected model\u002Faction:\n\n```bash\n${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external}\u002Fscripts\u002Fresolve_tao_image.py \\\n  --skill-bank ${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external} \\\n  --model \u003Cnetwork> --action \u003Caction> --format text\n```\n\nIf the helper is unavailable, read `skills\u002Fmodels\u002F\u003Cnetwork>\u002Fconfig.json` through\n`SkillBank().get_model_config(network_arch)`. Resolve image fields in this\norder:\n\n1. `actions.\u003Caction>.container_image`\n2. `actions.\u003Caction>.image`\n3. top-level `container_image`\n4. top-level `image`\n\nShow the exact image and ask:\n\n```text\nContainer image for \u003Cnetwork>\u002F\u003Caction>:\ndefault=\u003Cresolved image>\n\nUse this image, or provide image=\u003Coverride>?\n```\n\nIf the user accepts, pass the resolved image as the job `image`. If the user\noverrides, require a non-empty image reference and pass that value instead.\nDo not silently launch on the default image. This confirmation applies to\ntraining, AutoML recommendations, evaluation, inference, export, TensorRT\nengine generation, and application workflows that submit TAO containers.\n\n## Credential Filtering\n\nAfter the user chooses a platform, get the credential list for only that\nplatform:\n\n```bash\n${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external}\u002Fscripts\u002Flist_tao_platforms.py \\\n  --skill-bank ${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external} \\\n  --platform \u003Cplatform> --format text\n```\n\nAsk only for credentials returned by that command, plus model-specific\ncredentials from the selected model skill. Do not ask for Lepton credentials on\nSLURM, Kubernetes, or local Docker. Do not ask for SLURM credentials on Lepton,\nBrev, Kubernetes, or local Docker. Ask S3 credentials only when the selected\nplatform and the dataset\u002Fresult URIs require `s3:\u002F\u002F` access.\n\nFor initial launch intake, ask for required credentials and required credential\ngroups only. Treat the helper's optional credentials\u002Fsettings section as\nreference material; do not request those values unless their `only_when`\ncondition applies, the selected workflow cannot proceed without them, or the\nuser asks to customize that setting.\n\nWhen the helper output includes a \"Required credential groups\" section, satisfy\none credential from each group before proceeding. Explain each requested value\nusing the helper's description and \"How to get it\" text.\n\nFor SLURM, user-facing prompts should ask for `SSH_KEY_PATH` first. Mention\n`SSH_AUTH_SOCK` only if the user says they already use an SSH agent.\n\n## Dataset Intake\n\nAccept dataset inputs in either mode:\n\n- **Dataset root mode:** the user gives train\u002Feval\u002Fcalibration roots, and the\n  model skill maps required files by convention. Example for Cosmos-RL train:\n  `custom.train_dataset.annotation_path=\u003Croot>\u002Fannotations.json` and\n  `custom.train_dataset.media_path=\u003Croot>`.\n- **Direct spec mode:** the user gives exact spec-key paths when annotations,\n  media archives, videos, or image folders live in different places. Preserve\n  those keys directly, for example\n  `custom.train_dataset.annotation_path=\u002Flustre\u002F...\u002Ftrain_annotations.json`\n  and `custom.train_dataset.media_path=\u002Flustre\u002F...\u002Fvideos.tar.gz`.\n\nAsk for dataset examples that match the selected platform:\n\n- SLURM: shared cluster paths such as\n  `\u002Flustre\u002Ffsw\u002Fportfolios\u002F\u003Cteam>\u002F\u003Cyour-dir>\u002Fdata\u002F\u003Cmodel>\u002Ftrain` (where\n  `\u003Cyour-dir>` is your per-user directory on the cluster), or direct spec\n  paths under `\u002Flustre\u002F...`.\n- Lepton, Brev, Kubernetes: usually `s3:\u002F\u002Fbucket\u002Fpath\u002Ftrain` and\n  `s3:\u002F\u002Fbucket\u002Fpath\u002Feval` unless the platform profile mounts shared storage.\n- Local Docker: local paths visible to the Docker host, such as\n  `\u002Fdata\u002Ftao\u002F\u003Cmodel>\u002Ftrain`, or direct spec paths visible inside the planned\n  container mount.\n\nDo not assume \"dataset root\" is the only acceptable input. When direct spec\npaths are supplied, validate the exact spec paths rather than appending default\nfilenames.\n\n## Platform Preflight\n\nRun the selected platform's preflight checks before any launch artifact is\ncreated.\n\nPrefer the packaged preflight helper when the needed inputs are available:\n\n```bash\n${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external}\u002Fscripts\u002Fcheck_tao_launch_preflight.py \\\n  --skill-bank ${TAO_SKILL_BANK_PATH:-~\u002Ftao-skills-external} \\\n  --platform \u003Cplatform> \\\n  --path train_annotation=\u003Cpath> \\\n  --path train_media=\u003Cpath>\n```\n\nPass exact direct spec paths when the user supplied them. For root-mode inputs,\nexpand model-required files first, then pass those concrete annotation\u002Fmedia\npaths to the helper.\n\nWhen a model skill lists annotation-level required fields, pass them with\n`--json-required-field \u003Cpath-label>=\u003Cfield>[,\u003Cfield>...]` so schema\u002Fdata\ncontent issues fail during preflight rather than inside the first training\ncontainer. For example, Cosmos-RL train\u002FAutoML requires\n`--json-required-field train_annotation=video_fps` and\n`--json-required-field val_annotation=video_fps`.\n\nDo not use `--skip-platform-access` for a real launch. That flag is only for\ndry environment checks or for cases where the user has already provided explicit\nmanual proof of platform and storage access. If the helper cannot verify remote\nAPI, CLI, cluster, or object-store access, treat preflight as failed and do not\ngenerate launch artifacts.\n\nFor SLURM:\n\n1. Require `SLURM_USER`, `SLURM_HOSTNAME`, `SLURM_PARTITION`, and one of\n   `SSH_KEY_PATH` or `SSH_AUTH_SOCK`.\n   Use the selected platform helper's `Resource defaults` for runtime values.\n   For the packaged SLURM defaults, generate launchers with\n   `SLURM_TIME_HOURS=4` and `SLURM_TIMEOUT_HOURS=3.8`; never invent a\n   12-hour default for the 4-hour partition list.\n   Launching the orchestrator with `nohup` or in the background is allowed for\n   durability, but it does not satisfy chat monitoring by itself. After launch,\n   keep a foreground chat-side polling loop attached until terminal state or\n   explicit detach.\n2. Split comma-separated `SLURM_HOSTNAME`, resolve hosts where possible, and\n   require passwordless `ssh -o BatchMode=yes` to at least one host.\n3. If SSH fails, do not offer several equivalent choices. Ask for\n   `SSH_KEY_PATH=\u002Fpath\u002Fto\u002Fprivate_key` and show the passwordless setup steps:\n   create a key if needed with\n   `ssh-keygen -t ed25519 -N \"\" -f ~\u002F.ssh\u002Fid_ed25519`; install it with\n   `ssh-copy-id -i ~\u002F.ssh\u002Fid_ed25519.pub \u003CSLURM_USER>@\u003Clogin-host>`; trust the\n   host with `ssh-keyscan -H \u003Clogin-host> >> ~\u002F.ssh\u002Fknown_hosts`; set\n   `chmod 600 ~\u002F.ssh\u002Fid_ed25519`; verify with\n   `ssh -o BatchMode=yes -i ~\u002F.ssh\u002Fid_ed25519 \u003CSLURM_USER>@\u003Clogin-host> 'hostname'`;\n   then rerun with `SSH_KEY_PATH=~\u002F.ssh\u002Fid_ed25519`.\n4. After SSH passes, validate dataset annotation\u002Fmedia paths on the remote login\n   host with `test -e` or an equivalent read-only command.\n5. Only then create runner scripts, specs, workspaces, or submit jobs.\n\nFor local Docker, validate Docker\u002FGPU access and local dataset paths before\nwriting launch artifacts. For Lepton, Brev, and Kubernetes, validate API or\ncluster access plus object-storage credentials and `aws s3 ls` readability for\n`s3:\u002F\u002F` inputs before writing launch artifacts. For mounted shared-storage or\nPVC paths on those remote platforms, require manual proof that the path is\nmounted into the job environment; the helper fails closed rather than accepting\nunverified remote mount paths.\n",{"name":5,"tags":49,"license":15,"metadata":50,"description":7,"allowed-tools":53,"compatibility":54},[26,27,24],{"author":51,"version":52},"NVIDIA Corporation","0.1.0","Read Bash","Requires the packaged TAO skill bank helper scripts.","main","7a940b8e5af16c95e5c190a524421d32fc7445a9",".claude\u002Fskills\u002Ftao-launch-workflow","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui","https:\u002F\u002Fneuroads.com.br","2026-08-12 00:42:44",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add headmktlucca-ui\u002Fneuroads-lp --skill tao-launch-workflow",{"tool":68,"command":69},"bunx","bunx skills add headmktlucca-ui\u002Fneuroads-lp --skill tao-launch-workflow",{"tool":71,"command":72},"pnpm","pnpm dlx skills add headmktlucca-ui\u002Fneuroads-lp --skill tao-launch-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftao-launch-workflow\u002FSKILL.md",true,[76,82,86,90],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"BENCHMARK.md","REFERENCE","参考文档",4243,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftao-launch-workflow\u002FBENCHMARK.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fevals.json",797,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftao-launch-workflow\u002Fevals\u002Fevals.json",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"skill-card.md",3887,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftao-launch-workflow\u002Fskill-card.md",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"skill.oms.sig","OTHER","其他",4593,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftao-launch-workflow\u002Fskill.oms.sig",[97,119,143,169,187,221],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":108,"publishedAt":44},"01M6PTDCZTXTGSTX4RFK901YSZ","xunit-skill","Generates xUnit.net tests in C#. Covers Fact\u002FTheory, constructor injection, IClassFixture, and FluentAssertions. Use when user mentions \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal\", \"C# xUnit\". Triggers on: \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal C#\", \"xUnit.net\".","MIT","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxunit-skill\u002FSKILL.md",[104,107],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[109,110,111,112,113,38,114,115,116,117,118],"xunit","xunit skill","testing","injection","user","tests","triggers","unit","unit-testing","C#",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":127,"publishedAt":44},"01M6PTCB59ZTG5FTMWGPYEMMBP","xcuitest-skill","Generates XCUITest UI tests for iOS\u002FiPadOS apps in Swift. Apple's native testing framework for reliable, fast UI automation. Supports local simulators and TestMu AI cloud real devices. Use when user mentions \"XCUITest\", \"XCTest\", \"iOS UI test\", \"Swift test\", \"XCUIApplication\". Triggers on: \"XCUITest\", \"XCTest UI\", \"iOS UI test\", \"Swift UI test\", \"XCUIApplication\", \"TestMu\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxcuitest-skill\u002FSKILL.md",[125,126],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[128,129,111,130,131,132,133,134,38,135,136,137,138,139,114,115,140,141,31,142],"xcuitest","xcuitest skill","automation","test","testing framework","ios","devices","mobile","mobile-testing","ui test","local","apple","apps","native","objective",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":153,"publishedAt":44},"01M6PTATMNTY9NF4J7KSR76YK6","world-builder","Create and manage generative game zones for Dorothy's Pokemon-style world. Use this skill when creating, updating, or designing game worlds via MCP tools.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworld-builder\u002FSKILL.md",[149,152],{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[154,155,156,157,158,159,160,161,38,162,163,164,165,166,167,31,168],"builder","world","world builder","MCP","create","mcp tools","Tools","game","pokemon","manage","style","via","theme","zone","generative",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":177,"publishedAt":44},"01M6PT9Z92JTSQEHE1QR0NNW5F","webdriverio-skill","Generates WebdriverIO (WDIO) automation tests in JavaScript or TypeScript. Supports local and TestMu AI cloud. Use when user mentions \"WebdriverIO\", \"WDIO\", \"wdio.conf\", \"browser.url\", \"$\", \"$$\". Triggers on: \"WebdriverIO\", \"WDIO\", \"wdio\", \"browser.$\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebdriverio-skill\u002FSKILL.md",[175,176],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[178,111,179,130,180,181,182,183,113,38,184,138,114,115,185,186],"webdriverio skill","typescript","javascript","browser","cloud","e2e","e2e-testing","URL","conf",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":202,"publishedAt":44},"01M6PT9NVK36ZWCQ69YXK3FR4K","web-design-guidelines","Web platform design and accessibility guidelines. Use when building web interfaces, auditing accessibility, implementing responsive layouts, or reviewing web UI code. Triggers on tasks involving HTML, CSS, web components, WCAG compliance, responsive design, or web performance.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb\u002FSKILL.md",[193,196,197],{"categoryNo":194,"categoryName":195,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":198,"categoryName":199,"taxonomyType":200,"taxonomyTypeDesc":201},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,28,115,220],"design","web","guidelines","web design guidelines","web design","css","performance","components","web components","tasks","code","web performance","ui","platform design","html","responsive design","responsive","implementing",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":229,"publishedAt":44},"01M6PT9A3JKRE3X34276F2FW5R","watchos-design-guidelines","Apple Human Interface Guidelines for Apple Watch. Use when building watchOS apps, complications, or workout features. Triggers on tasks involving Watch UI, Digital Crown, glanceable interfaces, or wrist-based interactions.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwatchos\u002FSKILL.md",[227,228],{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":198,"categoryName":199,"taxonomyType":200,"taxonomyTypeDesc":201},[203,205,230,212,215,38,231,232,139,28,233,115,140,234,31,235,236],"watchos design guidelines","workout","human","watch","interface","platform-design","features"]