[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M753G7DJTT2C2P8EYJHTW7X8":3,"skill-same:01M753G7DJTT2C2P8EYJHTW7X8":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M753G7DJTT2C2P8EYJHTW7X8","hub-operations",null,"Operate Hugging Face Hub repositories and API resources with authenticated or mocked Python workflows, explicit revision control, safe mutations, and actionable error recovery.","VectorSpaceLab\u002FAREX-Skill","VectorSpaceLab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F180637102?v=4","01M7538C5WPSJGWF7KHR4EFZ9F","01M7538C6R2GFP53NPXTCZNBRT",351,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fexamples\u002Fcreator\u002Frepo-to-skills\u002Fartifacts\u002Fhuggingface_hub\u002Fhuggingface-hub\u002Fsub-skills\u002Fhub-operations\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: hub-operations\ndescription: \"Operate Hugging Face Hub repositories and API resources with authenticated or mocked Python workflows, explicit revision control, safe mutations, and actionable error recovery.\"\nlicense: Apache-2.0\ndisable-model-invocation: true\nmetadata:\n  disco-role: operating\n---\n\n# Hub Operations\n\nUse this sub-skill for Python workflows that discover or mutate Hub API\nresources: repositories, files and commits, refs, collections, cards,\ndiscussions and pull requests, and webhook registrations. It is grounded in\n`huggingface_hub` 1.29.0.\n\n## Trigger And Route\n\nThis is the routing surface, not a full API manual. Select the smallest\nlinked reference that covers the request, then keep the operation and\nverification boundaries visible.\n\n| Request signal | Route | Read next |\n|---|---|---|\n| create\u002Finspect\u002Fsearch a repo, list files\u002Ftree\u002Fcommits, or manage refs | repository and discovery | [API reference](references\u002Fapi-reference.md) |\n| upload\u002Fcopy\u002Fdelete files, create a commit or PR, or pin a parent SHA | files and commits | [Workflows](references\u002Fworkflows.md) |\n| cards, metadata, collections, discussions, or PR review | collaboration and metadata | [API reference](references\u002Fapi-reference.md) and [Workflows](references\u002Fworkflows.md) |\n| webhook registration, scope, enable\u002Fdisable, or deletion | webhook resources | [Workflows](references\u002Fworkflows.md) |\n| token precedence, access, 401\u002F403\u002F404\u002F409\u002F412\u002F429, or ambiguous mutation | authentication and recovery | [Troubleshooting](references\u002Ftroubleshooting.md) |\n| deterministic unit-style behavior without Hub access | mocked HfApi case | [Mocked recovery case](references\u002Fworkflows.md#13-exercise-a-private-dataset-conflict-with-a-mocked-hfapi) |\n\nUse this route when the request includes one or more of:\n\n- create, list, inspect, update, delete, move, or duplicate a model, dataset,\n  or Space repository;\n- upload, delete, or server-side copy repository files; create a commit or PR;\n- inspect a revision or manage branches and tags;\n- search models, datasets, or Spaces and interpret returned info objects;\n- create or curate collections and repository cards;\n- read or manage discussions, PRs, and their events;\n- create, inspect, enable, disable, update, or delete webhook resources;\n- configure or diagnose authentication needed upstream of these operations;\n- identify and recover from Hub API errors, including stale-parent conflicts.\n\nRoute elsewhere when the primary task is:\n\n- download\u002Fcache behavior, `HfFileSystem`, or buckets: sibling\n  `downloads-and-storage` route;\n- hosted inference or Inference Endpoints: sibling `inference-and-endpoints`\n  route;\n- exact `hf` command syntax, output modes, or shell automation: sibling\n  `cli-and-automation` route;\n- Jobs, sandboxes, Space runtime\u002Fhardware, or a deployed webhook server:\n  sibling `hosted-compute-and-integrations` route.\n\nWebhook registration is owned here; receiving payloads in a server is not.\nSpace repository metadata is owned here; running or scaling the Space is not.\n\n## Operating Contract\n\n1. **Classify the operation.** Label every step `READ-ONLY`, `MUTATION`, or\n   `DESTRUCTIVE`. Do not hide a mutation inside an inspection step.\n2. **Resolve identity.** Record `repo_id`, `repo_type`, `revision`, endpoint,\n   and token source before calling the API. Prefer explicit\n   `namespace\u002Fname`; Python uses singular repo types: `model`, `dataset`,\n   `space`.\n3. **Authenticate safely.** Prefer `HF_TOKEN` or a previously saved login.\n   Never hardcode, log, print, serialize, or include a token in an exception\n   report. Use a write-scoped token only for mutations.\n4. **Inspect before mutation.** Fetch the target object and revision, confirm\n   ownership\u002Ftype\u002Fvisibility, capture the current SHA when concurrency matters,\n   and preview local paths or remote resources affected.\n5. **Use explicit mutation intent.** Set a meaningful `commit_message`; pass\n   `repo_type`; choose `revision`; use `create_pr=True` when review is safer;\n   use `parent_commit` for optimistic concurrency.\n6. **Verify the result.** Assert returned IDs\u002Ftypes and inspect the resulting\n   revision. For PR commits, verify `CommitInfo.pr_revision` and inspect that\n   ref rather than assuming `main` changed.\n7. **Guard destructive actions.** Require an exact target display, a dry-run\n   plan, and explicit confirmation immediately before delete, merge, move, or\n   visibility reduction. Re-inspect after confirmation if the workflow waited.\n8. **Recover narrowly.** Branch on typed exceptions and HTTP status. Retry\n   only operations shown to be safe, bounded, and still valid after re-read.\n\n### Safety confirmations\n\nDeletion, move, visibility reduction, branch\u002Ftag deletion, collection or\nwebhook deletion, irreversible comment hiding, and PR merge require a\nread-only plan, a dry-run gate, exact target confirmation, an immediate SHA or\nstate recheck, one mutation, and a post-check. `--yes` or `APPLY=1` is only a\nmechanism; non-interactive use must receive approval from an upstream reviewed\ncontrol. See [the guarded workflow](references\u002Fworkflows.md#12-explicit-dry-run-and-check-before-delete-pattern).\n\n## Core Concepts\n\n- `repo_id` is normally `namespace\u002Fname`. A bare name can use the authenticated\n  namespace for creation, but explicit IDs are safer in automation.\n- `repo_type=None` means a model for most APIs. Always pass `dataset` or\n  `space`; never pass plural forms to Python methods.\n- A revision can be a branch, tag, commit OID, or PR ref such as `refs\u002Fpr\u002F3`.\n  Mutating methods normally default to `main`; verify the method-specific\n  constraints before combining `revision` and `create_pr`.\n- `exist_ok=True` makes repository, branch, or tag creation tolerant of an\n  existing target. It does not prove that the existing resource has the\n  requested visibility or settings. Collections spell this `exists_ok`.\n- `visibility` accepts `public` or `private`, plus `protected` for Spaces.\n  Do not pass both `private` and `visibility`.\n- `parent_commit` is a full or short commit OID used as an optimistic\n  concurrency check. On conflict, fetch the new head and re-evaluate; do not\n  blindly drop the check.\n- `create_pr=True` places a proposed commit on a PR ref. `CommitInfo` exposes\n  `pr_url`, `pr_num`, and `pr_revision`; `main` is unchanged until merge.\n- `commit_message` is the commit summary. Keep it specific and never place\n  credentials, signed URLs, or private payload content in it.\n- API listings are iterables and returned info fields are often optional.\n  Limit iteration and test for `None`; an `info` query usually contains more\n  detail than a list query.\n\n## Choose The Client Surface\n\nUse `HfApi(...)` when several calls should share an endpoint, token,\nuser-agent, or headers. Root-level helpers such as `create_repo`,\n`upload_file`, and `list_models` expose the same public operations and are\nconvenient for isolated calls. Keep one configured client through a workflow\nso endpoint and credentials cannot drift.\n\nRead [API reference](references\u002Fapi-reference.md) before writing calls or\ninterpreting `RepoUrl`, info, collection, discussion, webhook, or commit\nobjects. It contains signatures verified from the installed 1.29.0 package.\n\nRead [workflows](references\u002Fworkflows.md) when implementing create → inspect →\nupload → revision\u002FPR flows, discovery, refs, cards, collections, discussions,\nwebhook resources, or a check-before-delete plan. Examples explicitly mark\nread-only and mutation boundaries.\n\nRead [troubleshooting](references\u002Ftroubleshooting.md) when credentials,\nidentity, access, revisions, concurrency, upload patterns, rate limits,\nnetwork failures, or destructive safeguards are involved. Follow its typed,\nbounded recovery rules instead of broad retries.\n\n## Output Expectations\n\nReturn or record, without secrets:\n\n- resolved endpoint, `repo_id`, `repo_type`, and requested revision;\n- mutation classification and whether confirmation occurred;\n- observed starting SHA and resulting SHA or PR ref when applicable;\n- concise fields from returned objects, not raw object dumps containing\n  secrets (notably webhook resources);\n- verification observations: resource exists, expected path\u002Fref\u002Fcard\u002Fevent is\n  present, or resource is absent after an approved deletion;\n- typed error, HTTP status, request ID, recovery attempted, and any remaining\n  ambiguity.\n\nStop rather than guess when target ownership, repo type, destructive intent,\ncredential scope, or post-conflict content validity cannot be established.\n","# Hub Operations\n\nUse this sub-skill for Python workflows that discover or mutate Hub API\nresources: repositories, files and commits, refs, collections, cards,\ndiscussions and pull requests, and webhook registrations. It is grounded in\n`huggingface_hub` 1.29.0.\n\n## Trigger And Route\n\nThis is the routing surface, not a full API manual. Select the smallest\nlinked reference that covers the request, then keep the operation and\nverification boundaries visible.\n\n| Request signal | Route | Read next |\n|---|---|---|\n| create\u002Finspect\u002Fsearch a repo, list files\u002Ftree\u002Fcommits, or manage refs | repository and discovery | [API reference](references\u002Fapi-reference.md) |\n| upload\u002Fcopy\u002Fdelete files, create a commit or PR, or pin a parent SHA | files and commits | [Workflows](references\u002Fworkflows.md) |\n| cards, metadata, collections, discussions, or PR review | collaboration and metadata | [API reference](references\u002Fapi-reference.md) and [Workflows](references\u002Fworkflows.md) |\n| webhook registration, scope, enable\u002Fdisable, or deletion | webhook resources | [Workflows](references\u002Fworkflows.md) |\n| token precedence, access, 401\u002F403\u002F404\u002F409\u002F412\u002F429, or ambiguous mutation | authentication and recovery | [Troubleshooting](references\u002Ftroubleshooting.md) |\n| deterministic unit-style behavior without Hub access | mocked HfApi case | [Mocked recovery case](references\u002Fworkflows.md#13-exercise-a-private-dataset-conflict-with-a-mocked-hfapi) |\n\nUse this route when the request includes one or more of:\n\n- create, list, inspect, update, delete, move, or duplicate a model, dataset,\n  or Space repository;\n- upload, delete, or server-side copy repository files; create a commit or PR;\n- inspect a revision or manage branches and tags;\n- search models, datasets, or Spaces and interpret returned info objects;\n- create or curate collections and repository cards;\n- read or manage discussions, PRs, and their events;\n- create, inspect, enable, disable, update, or delete webhook resources;\n- configure or diagnose authentication needed upstream of these operations;\n- identify and recover from Hub API errors, including stale-parent conflicts.\n\nRoute elsewhere when the primary task is:\n\n- download\u002Fcache behavior, `HfFileSystem`, or buckets: sibling\n  `downloads-and-storage` route;\n- hosted inference or Inference Endpoints: sibling `inference-and-endpoints`\n  route;\n- exact `hf` command syntax, output modes, or shell automation: sibling\n  `cli-and-automation` route;\n- Jobs, sandboxes, Space runtime\u002Fhardware, or a deployed webhook server:\n  sibling `hosted-compute-and-integrations` route.\n\nWebhook registration is owned here; receiving payloads in a server is not.\nSpace repository metadata is owned here; running or scaling the Space is not.\n\n## Operating Contract\n\n1. **Classify the operation.** Label every step `READ-ONLY`, `MUTATION`, or\n   `DESTRUCTIVE`. Do not hide a mutation inside an inspection step.\n2. **Resolve identity.** Record `repo_id`, `repo_type`, `revision`, endpoint,\n   and token source before calling the API. Prefer explicit\n   `namespace\u002Fname`; Python uses singular repo types: `model`, `dataset`,\n   `space`.\n3. **Authenticate safely.** Prefer `HF_TOKEN` or a previously saved login.\n   Never hardcode, log, print, serialize, or include a token in an exception\n   report. Use a write-scoped token only for mutations.\n4. **Inspect before mutation.** Fetch the target object and revision, confirm\n   ownership\u002Ftype\u002Fvisibility, capture the current SHA when concurrency matters,\n   and preview local paths or remote resources affected.\n5. **Use explicit mutation intent.** Set a meaningful `commit_message`; pass\n   `repo_type`; choose `revision`; use `create_pr=True` when review is safer;\n   use `parent_commit` for optimistic concurrency.\n6. **Verify the result.** Assert returned IDs\u002Ftypes and inspect the resulting\n   revision. For PR commits, verify `CommitInfo.pr_revision` and inspect that\n   ref rather than assuming `main` changed.\n7. **Guard destructive actions.** Require an exact target display, a dry-run\n   plan, and explicit confirmation immediately before delete, merge, move, or\n   visibility reduction. Re-inspect after confirmation if the workflow waited.\n8. **Recover narrowly.** Branch on typed exceptions and HTTP status. Retry\n   only operations shown to be safe, bounded, and still valid after re-read.\n\n### Safety confirmations\n\nDeletion, move, visibility reduction, branch\u002Ftag deletion, collection or\nwebhook deletion, irreversible comment hiding, and PR merge require a\nread-only plan, a dry-run gate, exact target confirmation, an immediate SHA or\nstate recheck, one mutation, and a post-check. `--yes` or `APPLY=1` is only a\nmechanism; non-interactive use must receive approval from an upstream reviewed\ncontrol. See [the guarded workflow](references\u002Fworkflows.md#12-explicit-dry-run-and-check-before-delete-pattern).\n\n## Core Concepts\n\n- `repo_id` is normally `namespace\u002Fname`. A bare name can use the authenticated\n  namespace for creation, but explicit IDs are safer in automation.\n- `repo_type=None` means a model for most APIs. Always pass `dataset` or\n  `space`; never pass plural forms to Python methods.\n- A revision can be a branch, tag, commit OID, or PR ref such as `refs\u002Fpr\u002F3`.\n  Mutating methods normally default to `main`; verify the method-specific\n  constraints before combining `revision` and `create_pr`.\n- `exist_ok=True` makes repository, branch, or tag creation tolerant of an\n  existing target. It does not prove that the existing resource has the\n  requested visibility or settings. Collections spell this `exists_ok`.\n- `visibility` accepts `public` or `private`, plus `protected` for Spaces.\n  Do not pass both `private` and `visibility`.\n- `parent_commit` is a full or short commit OID used as an optimistic\n  concurrency check. On conflict, fetch the new head and re-evaluate; do not\n  blindly drop the check.\n- `create_pr=True` places a proposed commit on a PR ref. `CommitInfo` exposes\n  `pr_url`, `pr_num`, and `pr_revision`; `main` is unchanged until merge.\n- `commit_message` is the commit summary. Keep it specific and never place\n  credentials, signed URLs, or private payload content in it.\n- API listings are iterables and returned info fields are often optional.\n  Limit iteration and test for `None`; an `info` query usually contains more\n  detail than a list query.\n\n## Choose The Client Surface\n\nUse `HfApi(...)` when several calls should share an endpoint, token,\nuser-agent, or headers. Root-level helpers such as `create_repo`,\n`upload_file`, and `list_models` expose the same public operations and are\nconvenient for isolated calls. Keep one configured client through a workflow\nso endpoint and credentials cannot drift.\n\nRead [API reference](references\u002Fapi-reference.md) before writing calls or\ninterpreting `RepoUrl`, info, collection, discussion, webhook, or commit\nobjects. It contains signatures verified from the installed 1.29.0 package.\n\nRead [workflows](references\u002Fworkflows.md) when implementing create → inspect →\nupload → revision\u002FPR flows, discovery, refs, cards, collections, discussions,\nwebhook resources, or a check-before-delete plan. Examples explicitly mark\nread-only and mutation boundaries.\n\nRead [troubleshooting](references\u002Ftroubleshooting.md) when credentials,\nidentity, access, revisions, concurrency, upload patterns, rate limits,\nnetwork failures, or destructive safeguards are involved. Follow its typed,\nbounded recovery rules instead of broad retries.\n\n## Output Expectations\n\nReturn or record, without secrets:\n\n- resolved endpoint, `repo_id`, `repo_type`, and requested revision;\n- mutation classification and whether confirmation occurred;\n- observed starting SHA and resulting SHA or PR ref when applicable;\n- concise fields from returned objects, not raw object dumps containing\n  secrets (notably webhook resources);\n- verification observations: resource exists, expected path\u002Fref\u002Fcard\u002Fevent is\n  present, or resource is absent after an approved deletion;\n- typed error, HTTP status, request ID, recovery attempted, and any remaining\n  ambiguity.\n\nStop rather than guess when target ownership, repo type, destructive intent,\ncredential scope, or post-conflict content validity cannot be established.\n",{"name":5,"license":14,"metadata":23,"description":7,"disable-model-invocation":25},{"disco-role":24},"operating",true,"main","ac3fe1afa80fb9a09775ecfb2b6cc3ba850a2db6","examples\u002Fcreator\u002Frepo-to-skills\u002Fartifacts\u002Fhuggingface_hub\u002Fhuggingface-hub\u002Fsub-skills\u002Fhub-operations",27,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab","2026-09-03 10:25:21",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add VectorSpaceLab\u002FAREX-Skill --skill hub-operations",{"tool":39,"command":40},"bunx","bunx skills add VectorSpaceLab\u002FAREX-Skill --skill hub-operations",{"tool":42,"command":43},"pnpm","pnpm dlx skills add VectorSpaceLab\u002FAREX-Skill --skill hub-operations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fexamples\u002Fcreator\u002Frepo-to-skills\u002Fartifacts\u002Fhuggingface_hub\u002Fhuggingface-hub\u002Fsub-skills\u002Fhub-operations\u002FSKILL.md",[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fapi-reference.md","REFERENCE","参考文档",21244,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fexamples\u002Fcreator\u002Frepo-to-skills\u002Fartifacts\u002Fhuggingface_hub\u002Fhuggingface-hub\u002Fsub-skills\u002Fhub-operations\u002Freferences\u002Fapi-reference.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Ftroubleshooting.md",16066,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fexamples\u002Fcreator\u002Frepo-to-skills\u002Fartifacts\u002Fhuggingface_hub\u002Fhuggingface-hub\u002Fsub-skills\u002Fhub-operations\u002Freferences\u002Ftroubleshooting.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fworkflows.md",27524,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fexamples\u002Fcreator\u002Frepo-to-skills\u002Fartifacts\u002Fhuggingface_hub\u002Fhuggingface-hub\u002Fsub-skills\u002Fhub-operations\u002Freferences\u002Fworkflows.md",[61,69,76,83,90,97],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":68},"01M799NYSH1R3RVAHSM2D88Y84","passnet-triton-opt","Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block\u002Fgrid\u002Fwarp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-triton-opt\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":68},"01M799NS5APEC0N1FZ7XZVW6BN","passnet-solve","END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-solve\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":68},"01M799NNY9BKSM21V5R7QVTBJX","passnet-skill","PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under .\u002Fpass_dir\u002F, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-skill\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":68},"01M799NHH6NP7Z1RK77KGXAN6S","passnet-pattern-fusion","Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()\u002Freplacement_args()\u002Freplacement_func() files, when a pass \"failed to match\", or when deciding how to fuse multiple kernels\u002Fops.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-pattern-fusion\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":68},"01M799ND2J4WNC2PGAZ0A06NDF","passnet-orchestrate","Round\u002Fbatch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep\u002Frevert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-orchestrate\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":68},"01M799N8SBTMY02ZDG2AZF5ZWE","passnet-feedback","Fast, deterministic feedback for PassNet work: pre-flight pattern\u002Fmatch verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Ftask-oriented\u002FPassNet\u002Fskills\u002Fpassnet-feedback\u002FSKILL.md",[],[]]