[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7930BA58F04K16C8PRCS1DE":3,"skill-same:01M7930BA58F04K16C8PRCS1DE":71},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":46},"01M7930BA58F04K16C8PRCS1DE","repo-development",null,"Maintain Prefect itself safely: repo layout, scoped AGENTS rules, focused validation, generated artifacts, and package-boundary caveats.","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\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fprefect\u002Fsub-skills\u002Frepo-development\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: repo-development\ndescription: \"Maintain Prefect itself safely: repo layout, scoped AGENTS rules,\n  focused validation, generated artifacts, and package-boundary caveats.\"\ndisable-model-invocation: true\nmetadata:\n  disco-role: operating\nlicense: Apache 2.0\n---\n\n# Prefect Repo Development\n\nUse this sub-skill when the task is to change the Prefect repository itself rather than author user flows, operate deployments, call the API, or run the CLI as an end user.\n\n## Route Here For\n\n- Choosing source and test files for changes under `src\u002Fprefect\u002F`, `tests\u002F`, `docs\u002F`, `client\u002F`, `src\u002Fintegrations\u002F`, or `ui-v2\u002F`.\n- Applying scoped `AGENTS.md` rules, including the source\u002Ftest mirror, client\u002Fserver boundaries, docs generation rules, integration boundaries, and UI-v2 workflow.\n- Selecting focused pytest, ruff, pre-commit, docs, generated-schema, or `prefect-client` validation commands before broader checks.\n- Maintaining generated files such as settings types, schemas, CLI docs, OpenAPI docs, API references, examples, and integration docs.\n- Creating issue repro scripts under `repros\u002F` and avoiding maintainer anti-patterns such as bypassing server orchestration state transitions.\n\n## Route Elsewhere\n\n- Use `flow-task-authoring` for user-facing `@flow`, `@task`, states, futures, task runners, caching, and result behavior.\n- Use `deployments-workers` for deployments, `prefect.yaml`, serve, workers, work pools, and run submission as a user workflow.\n- Use `cli-server-operations` for operating the Prefect CLI, profiles, server startup\u002Fstatus, variables, artifacts, and diagnostics.\n- Use `api-client-settings` for Python client usage, settings\u002Fprofile APIs, schemas as a user, and the `prefect-client` package distinction.\n- Use `events-blocks-assets` for events, automations, blocks, assets, variables, and concurrency primitives as user-facing features.\n\n## Working Pattern\n\n1. Read the nearest scoped `AGENTS.md` before editing; deeper files override broader files.\n2. Map changed source paths to mirrored tests and component-specific invariants before writing code.\n3. Keep behavior changes minimal, preserve public APIs unless explicitly approved, and update docs or generated artifacts when source-of-truth files change.\n4. Run the most focused safe validation first, then broaden only when the change affects shared behavior, schemas, docs, client packaging, or CI selection.\n5. Keep service-heavy, Docker, Postgres, integration, UI browser, and release\u002Fpublish commands opt-in unless the task explicitly requires them.\n\n## References\n\n- Start with [repo-layout](references\u002Frepo-layout.md) for source\u002Ftest mapping, scoped instructions, package boundaries, and maintainer caveats.\n- Use [testing-and-validation](references\u002Ftesting-and-validation.md) to choose focused pytest, lint, pre-commit, CI matrix, and repro-script checks.\n- Use [generated-artifacts](references\u002Fgenerated-artifacts.md) when schemas, settings, docs, API references, examples, UI service types, or `prefect-client` metadata may be stale.\n- Use [troubleshooting](references\u002Ftroubleshooting.md) for missing tools, dependency drift, AGENTS conflicts, async test context failures, service requirements, and state-transition anti-patterns.\n\n## Bundled Helper\n\nRun `python scripts\u002Fselect_prefect_tests.py --help` from this sub-skill directory to inspect a safe test-selection helper. It accepts changed paths and prints suggested validation commands without running tests, starting services, reading git history, or mutating files.\n","# Prefect Repo Development\n\nUse this sub-skill when the task is to change the Prefect repository itself rather than author user flows, operate deployments, call the API, or run the CLI as an end user.\n\n## Route Here For\n\n- Choosing source and test files for changes under `src\u002Fprefect\u002F`, `tests\u002F`, `docs\u002F`, `client\u002F`, `src\u002Fintegrations\u002F`, or `ui-v2\u002F`.\n- Applying scoped `AGENTS.md` rules, including the source\u002Ftest mirror, client\u002Fserver boundaries, docs generation rules, integration boundaries, and UI-v2 workflow.\n- Selecting focused pytest, ruff, pre-commit, docs, generated-schema, or `prefect-client` validation commands before broader checks.\n- Maintaining generated files such as settings types, schemas, CLI docs, OpenAPI docs, API references, examples, and integration docs.\n- Creating issue repro scripts under `repros\u002F` and avoiding maintainer anti-patterns such as bypassing server orchestration state transitions.\n\n## Route Elsewhere\n\n- Use `flow-task-authoring` for user-facing `@flow`, `@task`, states, futures, task runners, caching, and result behavior.\n- Use `deployments-workers` for deployments, `prefect.yaml`, serve, workers, work pools, and run submission as a user workflow.\n- Use `cli-server-operations` for operating the Prefect CLI, profiles, server startup\u002Fstatus, variables, artifacts, and diagnostics.\n- Use `api-client-settings` for Python client usage, settings\u002Fprofile APIs, schemas as a user, and the `prefect-client` package distinction.\n- Use `events-blocks-assets` for events, automations, blocks, assets, variables, and concurrency primitives as user-facing features.\n\n## Working Pattern\n\n1. Read the nearest scoped `AGENTS.md` before editing; deeper files override broader files.\n2. Map changed source paths to mirrored tests and component-specific invariants before writing code.\n3. Keep behavior changes minimal, preserve public APIs unless explicitly approved, and update docs or generated artifacts when source-of-truth files change.\n4. Run the most focused safe validation first, then broaden only when the change affects shared behavior, schemas, docs, client packaging, or CI selection.\n5. Keep service-heavy, Docker, Postgres, integration, UI browser, and release\u002Fpublish commands opt-in unless the task explicitly requires them.\n\n## References\n\n- Start with [repo-layout](references\u002Frepo-layout.md) for source\u002Ftest mapping, scoped instructions, package boundaries, and maintainer caveats.\n- Use [testing-and-validation](references\u002Ftesting-and-validation.md) to choose focused pytest, lint, pre-commit, CI matrix, and repro-script checks.\n- Use [generated-artifacts](references\u002Fgenerated-artifacts.md) when schemas, settings, docs, API references, examples, UI service types, or `prefect-client` metadata may be stale.\n- Use [troubleshooting](references\u002Ftroubleshooting.md) for missing tools, dependency drift, AGENTS conflicts, async test context failures, service requirements, and state-transition anti-patterns.\n\n## Bundled Helper\n\nRun `python scripts\u002Fselect_prefect_tests.py --help` from this sub-skill directory to inspect a safe test-selection helper. It accepts changed paths and prints suggested validation commands without running tests, starting services, reading git history, or mutating files.\n",{"name":5,"license":23,"metadata":24,"description":7,"disable-model-invocation":26},"Apache 2.0",{"disco-role":25},"operating",true,"main","ac3fe1afa80fb9a09775ecfb2b6cc3ba850a2db6","skills\u002Frepositories\u002Frepo-skills\u002Fprefect\u002Fsub-skills\u002Frepo-development",27,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill","https:\u002F\u002Fgithub.com\u002FVectorSpaceLab","2026-09-03 10:25:21",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":26},[36,39,42],{"tool":37,"command":38},"npx","npx skills add VectorSpaceLab\u002FAREX-Skill --skill repo-development",{"tool":40,"command":41},"bunx","bunx skills add VectorSpaceLab\u002FAREX-Skill --skill repo-development",{"tool":43,"command":44},"pnpm","pnpm dlx skills add VectorSpaceLab\u002FAREX-Skill --skill repo-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fprefect\u002Fsub-skills\u002Frepo-development\u002FSKILL.md",[47,53,57,61,65],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fgenerated-artifacts.md","REFERENCE","参考文档",6761,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fprefect\u002Fsub-skills\u002Frepo-development\u002Freferences\u002Fgenerated-artifacts.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Frepo-layout.md",8274,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fprefect\u002Fsub-skills\u002Frepo-development\u002Freferences\u002Frepo-layout.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Ftesting-and-validation.md",7101,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fprefect\u002Fsub-skills\u002Frepo-development\u002Freferences\u002Ftesting-and-validation.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Ftroubleshooting.md",8329,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fprefect\u002Fsub-skills\u002Frepo-development\u002Freferences\u002Ftroubleshooting.md",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Fselect_prefect_tests.py","SCRIPT","脚本",20911,"https:\u002F\u002Fgithub.com\u002FVectorSpaceLab\u002FAREX-Skill\u002Fblob\u002Fmain\u002Fskills\u002Frepositories\u002Frepo-skills\u002Fprefect\u002Fsub-skills\u002Frepo-development\u002Fscripts\u002Fselect_prefect_tests.py",[72,79,86,93,100,107],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"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",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":18},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":18},"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",[],[]]