[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MP0RZTESWGBN83PARP8R6C":3,"skill-same:01M6MP0RZTESWGBN83PARP8R6C":73},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":72},"01M6MP0RZTESWGBN83PARP8R6C","preflight",null,"Creates or reviews the required Clean Room preflight goal contract before source discovery, decomposition, attended execution, or unattended execution.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhit3rabbit\u002Fclean-room-skill\u002Fskills\u002Fpreflight\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"reviews","new","new goal","unattended","attended","Existing","source","clean room","path","true","execution","contract","decomposition","clean","source discovery","goal","json","discovery","2026-11-10 10:12:30",false,"---\nname: preflight\ndescription: Creates or reviews the required Clean Room preflight goal contract before source discovery, decomposition, attended execution, or unattended execution.\nargument-hint: [new goal details or existing preflight-goal.json path]\ndisable-model-invocation: true\n---\n\n# Clean Room Preflight\n\nCreate or validate `preflight-goal.json` before active clean-room artifacts start.\n\nPreflight stops after a canonical `preflight-goal.json` is created or validated. Do not create behavior specs, handoff packages, skeleton manifests, implementation plans, coverage ledgers, or clean-run-context artifacts during preflight.\n\nUse the canonical `clean-room` workflow and read `skills\u002Fclean-room\u002Freferences\u002FPREFLIGHT.md` when collecting missing goal details. Preserve the clean-room boundary: `preflight-goal.json` is a controller\u002Fcontaminated-side artifact and must not be placed in clean-role readable roots.\n\nIf the user provides output from CLI `clean-room-skill init` (or `npx clean-room-skill@latest init` if the binary is not available), check the generated bootstrap scaffold before creating or copying `preflight-goal.json`: `clean-room-bootstrap.json`, `contaminated\u002F`, `clean\u002F`, the implementation root, `quarantine\u002F`, target repo `.clean-room\u002FREADME.md`, `.clean-room\u002F.gitignore`, and `.clean-room\u002Flocal-state.json` must exist and agree. In the project layout the task root sits at `\u003Cbase>\u002F\u003Cproject>\u002Ftasks\u002F\u003Ctask-id>\u002F`, the implementation root is the shared project-level `implementation\u002F`, and `clean-room-project.json` must exist at the project root. Treat target-repo `.clean-room\u002Ftasks\u002F` as noncanonical unless explicitly configured; active artifacts belong in the external task root. Treat that scaffold as convenience output only; it is not an active `preflight-goal.json`, `init-config.json`, `task-manifest.json`, or `clean-run-context.json`.\n\n## Required Contract\n\nRecord these decisions:\n\n- End goal, success definition, destination kind, and existing destination handling.\n- Target stack: language, runtime, framework, package manager, and test framework.\n- License and dependency policy, including blocked licenses, blocked dependencies, and native dependency approval.\n- Compatibility policy: public behavior\u002FAPI exactness only. Private structure, comments, and internal names must not be mirrored.\n- Feature policy: preserve, remove, add, and non-goals.\n- Code hygiene policy: file line caps, max files per iteration, split strategy, exceptions, and forbidden patterns.\n- Output policy: artifact base root, implementation root, assumed output directory, and write mode.\n- Controller policy: attended or unattended, iteration cap, and whether unattended is allowed after preflight.\n- Intent confirmation: `intent_confirmation` with explicit-user-answer sources for end goal, target stack, and controller mode, plus user-facing summaries of the goal and target stack.\n- Open questions, with blocking questions clearly marked.\n\nThe artifact must use the canonical `preflight-goal.schema.json` shape. Required top-level keys are `goal_id`, `created_at`, `end_goal`, `target_stack`, `license_policy`, `dependency_policy`, `compatibility_policy`, `feature_policy`, `code_hygiene_policy`, `output_policy`, `controller_policy`, and `open_questions`. Completed preflight inputs and unattended contracts also require `intent_confirmation`.\n\nReject non-canonical or legacy-shaped preflight artifacts instead of treating them as complete. Do not accept invented fields such as `version`, `created`, `source`, `destination`, `exactness_policy`, `output_policy.artifact_base`, `output_policy.contaminated_root`, `output_policy.clean_root`, or `output_policy.quarantine_root` as substitutes for canonical fields. Report the missing or invalid canonical fields and stop for review.\n\n## Mode Rules\n\nAttended runs may continue with recorded `open_questions`, but each blocking question becomes a pause gate before the affected work starts.\n\nUnattended runs require a complete `preflight-goal.json` with:\n\n- `controller_policy.mode: \"unattended\"`\n- `controller_policy.unattended_allowed_after_preflight: true`\n- finite `controller_policy.max_iterations`\n- `intent_confirmation` showing the end goal, target stack, and controller mode came from explicit user answers\n- empty `open_questions`\n\nDo not infer end goal, target language, runtime, framework, package manager, test framework, license, dependency policy, exactness policy, output directory, or feature add\u002Fremove policy from source code. If the user's end goal or target stack is unknown, leave blocking `open_questions`, keep unattended disabled, and do not write runner-ready `task-manifest.json` or `clean-run-context.json`.\n\n## CLI Helper\n\nUse `clean-room-skill init` or `npx clean-room-skill@latest init` to create bootstrap scaffolds before this step. Project layout is canonical: `~\u002FDocuments\u002FCleanRoom\u002F\u003Cproject>\u002Ftasks\u002F\u003Ctask-id>\u002F` holds per-task `contaminated\u002F`, `clean\u002F`, and `quarantine\u002F`, while `~\u002FDocuments\u002FCleanRoom\u002F\u003Cproject>\u002Fimplementation\u002F` is shared by every task in that project. Do not accept hand-created folders as a bootstrap substitute.\n\nUse the preflight CLI (`clean-room-skill` if installed, or `npx clean-room-skill@latest` as fallback) only for template creation or validation\u002Fcopying:\n\nThe safest path is `clean-room-skill preflight --template` for drafts and `clean-room-skill preflight --input` for completed contracts.\n\n```bash\nclean-room-skill preflight --template --output ~\u002FDocuments\u002FCleanRoom\u002Ftask-xxxxxxxx\u002Fcontaminated\u002Fpreflight-goal.json\nclean-room-skill preflight --input .\u002Fpreflight-goal.json --output ~\u002FDocuments\u002FCleanRoom\u002Ftask-xxxxxxxx\u002Fcontaminated\u002Fpreflight-goal.json\nclean-room-skill preflight --template --bootstrap ~\u002FDocuments\u002FCleanRoom\u002Ftask-xxxxxxxx\nclean-room-skill preflight --template --bootstrap ~\u002FDocuments\u002FCleanRoom\u002F\u003Cproject>\u002Ftasks\u002Ftask-xxxxxxxx\n```\n\n`--template` writes an attended draft with blocking open questions. It does not support unattended mode. Use `--input` for completed contracts. `--bootstrap` accepts either the generated task root or `clean-room-bootstrap.json`, writes to the generated contaminated artifact root after scaffold validation, and requires completed input contracts to match the bootstrap artifact and implementation roots.\n\n## Handoff\n\nAgent 0 must record `preflight_goal_ref`, `preflight_goal_sha256`, and the required `handoff_sequence` in `task-manifest.json`.\n\nClean roles receive only the clean-safe goal subset through `clean-run-context.json` `goal_contract` plus `code_hygiene_policy` and optional Agent 4 local commit policy. Do not send the full `preflight-goal.json` to Agent 1.5, Agent 2, Agent 3, Agent 4, or clean handoff packages.\n","# Clean Room Preflight\n\nCreate or validate `preflight-goal.json` before active clean-room artifacts start.\n\nPreflight stops after a canonical `preflight-goal.json` is created or validated. Do not create behavior specs, handoff packages, skeleton manifests, implementation plans, coverage ledgers, or clean-run-context artifacts during preflight.\n\nUse the canonical `clean-room` workflow and read `skills\u002Fclean-room\u002Freferences\u002FPREFLIGHT.md` when collecting missing goal details. Preserve the clean-room boundary: `preflight-goal.json` is a controller\u002Fcontaminated-side artifact and must not be placed in clean-role readable roots.\n\nIf the user provides output from CLI `clean-room-skill init` (or `npx clean-room-skill@latest init` if the binary is not available), check the generated bootstrap scaffold before creating or copying `preflight-goal.json`: `clean-room-bootstrap.json`, `contaminated\u002F`, `clean\u002F`, the implementation root, `quarantine\u002F`, target repo `.clean-room\u002FREADME.md`, `.clean-room\u002F.gitignore`, and `.clean-room\u002Flocal-state.json` must exist and agree. In the project layout the task root sits at `\u003Cbase>\u002F\u003Cproject>\u002Ftasks\u002F\u003Ctask-id>\u002F`, the implementation root is the shared project-level `implementation\u002F`, and `clean-room-project.json` must exist at the project root. Treat target-repo `.clean-room\u002Ftasks\u002F` as noncanonical unless explicitly configured; active artifacts belong in the external task root. Treat that scaffold as convenience output only; it is not an active `preflight-goal.json`, `init-config.json`, `task-manifest.json`, or `clean-run-context.json`.\n\n## Required Contract\n\nRecord these decisions:\n\n- End goal, success definition, destination kind, and existing destination handling.\n- Target stack: language, runtime, framework, package manager, and test framework.\n- License and dependency policy, including blocked licenses, blocked dependencies, and native dependency approval.\n- Compatibility policy: public behavior\u002FAPI exactness only. Private structure, comments, and internal names must not be mirrored.\n- Feature policy: preserve, remove, add, and non-goals.\n- Code hygiene policy: file line caps, max files per iteration, split strategy, exceptions, and forbidden patterns.\n- Output policy: artifact base root, implementation root, assumed output directory, and write mode.\n- Controller policy: attended or unattended, iteration cap, and whether unattended is allowed after preflight.\n- Intent confirmation: `intent_confirmation` with explicit-user-answer sources for end goal, target stack, and controller mode, plus user-facing summaries of the goal and target stack.\n- Open questions, with blocking questions clearly marked.\n\nThe artifact must use the canonical `preflight-goal.schema.json` shape. Required top-level keys are `goal_id`, `created_at`, `end_goal`, `target_stack`, `license_policy`, `dependency_policy`, `compatibility_policy`, `feature_policy`, `code_hygiene_policy`, `output_policy`, `controller_policy`, and `open_questions`. Completed preflight inputs and unattended contracts also require `intent_confirmation`.\n\nReject non-canonical or legacy-shaped preflight artifacts instead of treating them as complete. Do not accept invented fields such as `version`, `created`, `source`, `destination`, `exactness_policy`, `output_policy.artifact_base`, `output_policy.contaminated_root`, `output_policy.clean_root`, or `output_policy.quarantine_root` as substitutes for canonical fields. Report the missing or invalid canonical fields and stop for review.\n\n## Mode Rules\n\nAttended runs may continue with recorded `open_questions`, but each blocking question becomes a pause gate before the affected work starts.\n\nUnattended runs require a complete `preflight-goal.json` with:\n\n- `controller_policy.mode: \"unattended\"`\n- `controller_policy.unattended_allowed_after_preflight: true`\n- finite `controller_policy.max_iterations`\n- `intent_confirmation` showing the end goal, target stack, and controller mode came from explicit user answers\n- empty `open_questions`\n\nDo not infer end goal, target language, runtime, framework, package manager, test framework, license, dependency policy, exactness policy, output directory, or feature add\u002Fremove policy from source code. If the user's end goal or target stack is unknown, leave blocking `open_questions`, keep unattended disabled, and do not write runner-ready `task-manifest.json` or `clean-run-context.json`.\n\n## CLI Helper\n\nUse `clean-room-skill init` or `npx clean-room-skill@latest init` to create bootstrap scaffolds before this step. Project layout is canonical: `~\u002FDocuments\u002FCleanRoom\u002F\u003Cproject>\u002Ftasks\u002F\u003Ctask-id>\u002F` holds per-task `contaminated\u002F`, `clean\u002F`, and `quarantine\u002F`, while `~\u002FDocuments\u002FCleanRoom\u002F\u003Cproject>\u002Fimplementation\u002F` is shared by every task in that project. Do not accept hand-created folders as a bootstrap substitute.\n\nUse the preflight CLI (`clean-room-skill` if installed, or `npx clean-room-skill@latest` as fallback) only for template creation or validation\u002Fcopying:\n\nThe safest path is `clean-room-skill preflight --template` for drafts and `clean-room-skill preflight --input` for completed contracts.\n\n```bash\nclean-room-skill preflight --template --output ~\u002FDocuments\u002FCleanRoom\u002Ftask-xxxxxxxx\u002Fcontaminated\u002Fpreflight-goal.json\nclean-room-skill preflight --input .\u002Fpreflight-goal.json --output ~\u002FDocuments\u002FCleanRoom\u002Ftask-xxxxxxxx\u002Fcontaminated\u002Fpreflight-goal.json\nclean-room-skill preflight --template --bootstrap ~\u002FDocuments\u002FCleanRoom\u002Ftask-xxxxxxxx\nclean-room-skill preflight --template --bootstrap ~\u002FDocuments\u002FCleanRoom\u002F\u003Cproject>\u002Ftasks\u002Ftask-xxxxxxxx\n```\n\n`--template` writes an attended draft with blocking open questions. It does not support unattended mode. Use `--input` for completed contracts. `--bootstrap` accepts either the generated task root or `clean-room-bootstrap.json`, writes to the generated contaminated artifact root after scaffold validation, and requires completed input contracts to match the bootstrap artifact and implementation roots.\n\n## Handoff\n\nAgent 0 must record `preflight_goal_ref`, `preflight_goal_sha256`, and the required `handoff_sequence` in `task-manifest.json`.\n\nClean roles receive only the clean-safe goal subset through `clean-run-context.json` `goal_contract` plus `code_hygiene_policy` and optional Agent 4 local commit policy. Do not send the full `preflight-goal.json` to Agent 1.5, Agent 2, Agent 3, Agent 4, or clean handoff packages.\n",{"name":5,"description":7,"argument-hint":47,"disable-model-invocation":49},[48],"new goal details or existing preflight-goal.json path",true,"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fwhit3rabbit\u002Fclean-room-skill\u002Fskills\u002Fpreflight",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":49},[62,65,68],{"tool":63,"command":64},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill preflight",{"tool":66,"command":67},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill preflight",{"tool":69,"command":70},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill preflight","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhit3rabbit\u002Fclean-room-skill\u002Fskills\u002Fpreflight\u002FSKILL.md",[],[74,84,92,100,108,116],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":83},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":83},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":83},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":83},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":83},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"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":78,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":83},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]