[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVND75WAMN8PYPAE8TAGC9":3,"skill-same:01M6JVND75WAMN8PYPAE8TAGC9":80},{"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":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6JVND75WAMN8PYPAE8TAGC9","sw-pre-start",null,"Load mandatory SolidWorks conventions, design rules, task-relevant knowledge documents, standards data, and initial design-rule checks before any modeling or CAD code. Use at the beginning of every SolidWorks create, modify, repair, assembly, drawing, or API task, before touching SolidWorks; also use its final phase before save and export.","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\u002FErfouni\u002Fsolidworks-GPT-plugin\u002Fplugins\u002Fsolidworks-gpt-plugin\u002Fskills\u002Fsw-pre-start\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"sw pre start","start","use","phase","at","load","relevant","modeling","repair","standards","assembly","export","design","Rules","knowledge","save","api","data","code","create","documents","2026-11-10 10:12:30",false,"---\nname: sw-pre-start\ndescription: Load mandatory SolidWorks conventions, design rules, task-relevant knowledge documents, standards data, and initial design-rule checks before any modeling or CAD code. Use at the beginning of every SolidWorks create, modify, repair, assembly, drawing, or API task, before touching SolidWorks; also use its final phase before save and export.\n---\n\n# SolidWorks Pre-Start\n\nRun all phases in order. Do not model, generate CAD code, or call a SolidWorks\nAPI until Phases 1 through 4 complete or a documented KB outage forces the\noffline fallback.\n\n## Phase 0: non-negotiable engineering requirement (ENG-001)\n\n**This phase has no network dependency and is exempt from the offline fallback.**\nThe KB carries the same rule as a convention, but a documented outage must never\nbe the reason it stops applying.\n\nDo not create schematic, decorative, conceptual, simplified, placeholder, or\nvisually representative components.\n\n**Every component must be a real, functional, manufacturable, technically\naccurate part. No component - regardless of size or importance - may be created\nmerely for visual representation.**\n\nFor every individual component, including a single screw:\n\n1. Research it against reliable technical sources: peer-reviewed papers,\n   engineering references, manufacturer documentation, and the latest\n   applicable standards.\n2. Design from validated research - engineering principles, formulas,\n   calculations, material properties, manufacturing constraints, tolerances,\n   and safety requirements.\n3. Justify every value. Dimensions, geometries, connections, interfaces, loads,\n   clearances, fasteners, materials and mechanical properties must all be\n   realistic and technically defensible.\n4. Never invent. No assumptions, invented specifications, arbitrary dimensions,\n   fake mechanisms, or purely visual detail.\n5. Cite the standards, formulas, calculations and references used for each part.\n\n**Model every physical component separately.** If an assembly contains 10,000\nparts, all 10,000 are researched, engineered and modelled individually. No group\nof parts may be replaced by a simplified block, visual shell, placeholder,\ntexture, or symbolic representation. This covers screws, nuts, washers,\nbearings, seals, cables, connectors, welds, joints, gears, springs, housings,\nelectronic components and internal mechanisms alike.\n\nThe finished design must be fully functional, physically realistic,\nengineering-accurate, dimensionally consistent, manufacturable, properly\nassembled, based on validated calculations, compliant with the latest applicable\nstandards, and free of decorative, fictional or representational parts.\n\n### When the information is not available\n\nIf sufficient technical information or reliable references are unavailable for a\ncomponent, **do not fabricate or guess.** State plainly what is missing and what\nmust be researched or specified before that component can be designed accurately.\n\nStopping to ask is the correct outcome. A plausible-looking part built from\ninvented numbers is a failure, not a partial success - it looks finished and\nwill therefore be trusted.\n\nAn offline KB makes this *more* likely to be the right answer, not less: losing\nthe standards tables means less grounding for a dimension, never permission to\ninvent one.\n\nSet `KB_HOST` from `SW_KB_HOST`; default to\n`https:\u002F\u002Fsw-plugin.ideep.org`. Use `curl` through the shell for every runtime\nrequest. Quote the complete URL. Do not use browser or web-fetch tools for this\nKB.\n\nOn Windows, run `curl.exe` instead of `curl`: in Windows PowerShell 5.1\n`curl` is an alias for `Invoke-WebRequest`, which rejects curl options such\nas `-sS`. `curl.exe` is the real curl in every Windows shell.\n\n## Phase 1: conventions\n\nRun:\n\n```text\ncurl -sS \"{KB_HOST}\u002Fapi\u002Fknowledge?kind=convention\"\n```\n\nLoad every returned `body` once per Codex task. Treat conventions as hard rules\nunless the user explicitly overrides one. Read Persian and English documents.\nExpect conventions for metric units, ISO 2768-mK defaults, material defaults,\nfully-defined parametric sketches, `PRJ-\u003Cpart>-NNN` naming, `work\u002F` and\n`exports\u002F` paths, clean rebuilds, assigned material, rule checks, STEP, and\ndrawing PDF deliverables.\n\nIf required geometry or safety input remains unknown, ask the user; a KB\ndefault does not authorize inventing geometry-driving values.\n\n## Phase 2: active design rules\n\nRun:\n\n```text\ncurl -sS \"{KB_HOST}\u002Fapi\u002Fdesign-rules\"\n```\n\nSkip entries with `deprecated: true`. Internalize the rest by category.\nEnforce severity as follows:\n\n- `critical`: block until resolved;\n- `high`: fix before completion;\n- `medium`: fix unless the user explicitly overrides;\n- `low`: advisory, apply when possible.\n\n## Phase 3: task knowledge\n\nCreate a concise URL-encoded query for the requested component and likely\nSolidWorks features, then run:\n\n```text\ncurl -sS \"{KB_HOST}\u002Fapi\u002Fknowledge\u002Fsearch?q={query}\"\n```\n\nRead the top five to eight results, or up to ten for a complex assembly,\nthread, or sheet-metal task. Prioritize `playbook`, then `reference`,\n`strategy`, and `convention`. Read the complete reference for every SolidWorks\nAPI method about to be used. Fetch a known document with\n`GET \u002Fapi\u002Fknowledge\u002F{slug}` when necessary.\n\n## Phase 4: initial rule check\n\nBuild a JSON object from known values. Omit unknown keys; never fabricate them.\nTypical fields are:\n\n```json\n{\n  \"welded\": false,\n  \"tolerance_class\": \"m\",\n  \"process\": \"machined_aluminum\",\n  \"wall_thickness_mm\": 2.0,\n  \"nominal_dimension_mm\": 50.0,\n  \"fastener\": \"M8\",\n  \"hole_mm\": 9.0,\n  \"material\": \"6061-T6\"\n}\n```\n\nPOST it with `curl`:\n\n```text\ncurl -sS -X POST \"{KB_HOST}\u002Fapi\u002Fcheck-context\" -H \"Content-Type: application\u002Fjson\" --data-binary \"@\u003Ccontext.json>\"\n```\n\nReact to each result:\n\n- `pass`: continue;\n- `fail`: stop CAD work and fix the input, explaining the rule and change;\n- `warn`: flag it and fix when possible;\n- `advisory`: apply it as a design constraint;\n- `na`: ignore it.\n\nDo not proceed while `summary.fail` is greater than zero.\n\n## Phase 5: standards on demand\n\nQuery only the table needed for the current decision:\n\n- `GET \u002Fapi\u002Fstandards\u002Fmaterials[\u002F\u003Cname>]` for density, yield, and modulus;\n- `GET \u002Fapi\u002Fstandards\u002Ffits` for ISO 286 hole and shaft deviations;\n- `GET \u002Fapi\u002Fstandards\u002Fclearance_holes[\u002F\u003Cdesignation>]` for ISO 273 holes;\n- `GET \u002Fapi\u002Fstandards\u002Ftolerances_iso2768` for general tolerances;\n- `GET \u002Fapi\u002Fstandards\u002Ffasteners[\u002F\u003Cdesignation>]` for fastener geometry;\n- `GET \u002Fapi\u002Fstandards\u002Fsheet_metal_gauges` for gauge thickness;\n- `GET \u002Fapi\u002Fstandards\u002Fpreferred_numbers` for R-series dimensions.\n\nRecord units. The KB database convention is mm, MPa, and g\u002Fcm3.\n\n## Phase 6: final rule check\n\nAfter geometry is complete and before final save or export, POST a more\ncomplete final context to `\u002Fapi\u002Fcheck-context`. Resolve every `fail`; document\nall advisories in the session `issues` narrative.\n\n## Offline and error behavior\n\n- Unreachable server: record `KB offline - proceeding without pre-start\n  checks` and continue using verified engineering context.\n- Search `404`: continue with available knowledge.\n- Check-context `422`: retry once with fewer fields, then continue and record\n  the issue.\n- `5xx` or timeout: skip the failed phase and record it.\n\nThe KB accelerates the task; it is not a gatekeeper.\n","# SolidWorks Pre-Start\n\nRun all phases in order. Do not model, generate CAD code, or call a SolidWorks\nAPI until Phases 1 through 4 complete or a documented KB outage forces the\noffline fallback.\n\n## Phase 0: non-negotiable engineering requirement (ENG-001)\n\n**This phase has no network dependency and is exempt from the offline fallback.**\nThe KB carries the same rule as a convention, but a documented outage must never\nbe the reason it stops applying.\n\nDo not create schematic, decorative, conceptual, simplified, placeholder, or\nvisually representative components.\n\n**Every component must be a real, functional, manufacturable, technically\naccurate part. No component - regardless of size or importance - may be created\nmerely for visual representation.**\n\nFor every individual component, including a single screw:\n\n1. Research it against reliable technical sources: peer-reviewed papers,\n   engineering references, manufacturer documentation, and the latest\n   applicable standards.\n2. Design from validated research - engineering principles, formulas,\n   calculations, material properties, manufacturing constraints, tolerances,\n   and safety requirements.\n3. Justify every value. Dimensions, geometries, connections, interfaces, loads,\n   clearances, fasteners, materials and mechanical properties must all be\n   realistic and technically defensible.\n4. Never invent. No assumptions, invented specifications, arbitrary dimensions,\n   fake mechanisms, or purely visual detail.\n5. Cite the standards, formulas, calculations and references used for each part.\n\n**Model every physical component separately.** If an assembly contains 10,000\nparts, all 10,000 are researched, engineered and modelled individually. No group\nof parts may be replaced by a simplified block, visual shell, placeholder,\ntexture, or symbolic representation. This covers screws, nuts, washers,\nbearings, seals, cables, connectors, welds, joints, gears, springs, housings,\nelectronic components and internal mechanisms alike.\n\nThe finished design must be fully functional, physically realistic,\nengineering-accurate, dimensionally consistent, manufacturable, properly\nassembled, based on validated calculations, compliant with the latest applicable\nstandards, and free of decorative, fictional or representational parts.\n\n### When the information is not available\n\nIf sufficient technical information or reliable references are unavailable for a\ncomponent, **do not fabricate or guess.** State plainly what is missing and what\nmust be researched or specified before that component can be designed accurately.\n\nStopping to ask is the correct outcome. A plausible-looking part built from\ninvented numbers is a failure, not a partial success - it looks finished and\nwill therefore be trusted.\n\nAn offline KB makes this *more* likely to be the right answer, not less: losing\nthe standards tables means less grounding for a dimension, never permission to\ninvent one.\n\nSet `KB_HOST` from `SW_KB_HOST`; default to\n`https:\u002F\u002Fsw-plugin.ideep.org`. Use `curl` through the shell for every runtime\nrequest. Quote the complete URL. Do not use browser or web-fetch tools for this\nKB.\n\nOn Windows, run `curl.exe` instead of `curl`: in Windows PowerShell 5.1\n`curl` is an alias for `Invoke-WebRequest`, which rejects curl options such\nas `-sS`. `curl.exe` is the real curl in every Windows shell.\n\n## Phase 1: conventions\n\nRun:\n\n```text\ncurl -sS \"{KB_HOST}\u002Fapi\u002Fknowledge?kind=convention\"\n```\n\nLoad every returned `body` once per Codex task. Treat conventions as hard rules\nunless the user explicitly overrides one. Read Persian and English documents.\nExpect conventions for metric units, ISO 2768-mK defaults, material defaults,\nfully-defined parametric sketches, `PRJ-\u003Cpart>-NNN` naming, `work\u002F` and\n`exports\u002F` paths, clean rebuilds, assigned material, rule checks, STEP, and\ndrawing PDF deliverables.\n\nIf required geometry or safety input remains unknown, ask the user; a KB\ndefault does not authorize inventing geometry-driving values.\n\n## Phase 2: active design rules\n\nRun:\n\n```text\ncurl -sS \"{KB_HOST}\u002Fapi\u002Fdesign-rules\"\n```\n\nSkip entries with `deprecated: true`. Internalize the rest by category.\nEnforce severity as follows:\n\n- `critical`: block until resolved;\n- `high`: fix before completion;\n- `medium`: fix unless the user explicitly overrides;\n- `low`: advisory, apply when possible.\n\n## Phase 3: task knowledge\n\nCreate a concise URL-encoded query for the requested component and likely\nSolidWorks features, then run:\n\n```text\ncurl -sS \"{KB_HOST}\u002Fapi\u002Fknowledge\u002Fsearch?q={query}\"\n```\n\nRead the top five to eight results, or up to ten for a complex assembly,\nthread, or sheet-metal task. Prioritize `playbook`, then `reference`,\n`strategy`, and `convention`. Read the complete reference for every SolidWorks\nAPI method about to be used. Fetch a known document with\n`GET \u002Fapi\u002Fknowledge\u002F{slug}` when necessary.\n\n## Phase 4: initial rule check\n\nBuild a JSON object from known values. Omit unknown keys; never fabricate them.\nTypical fields are:\n\n```json\n{\n  \"welded\": false,\n  \"tolerance_class\": \"m\",\n  \"process\": \"machined_aluminum\",\n  \"wall_thickness_mm\": 2.0,\n  \"nominal_dimension_mm\": 50.0,\n  \"fastener\": \"M8\",\n  \"hole_mm\": 9.0,\n  \"material\": \"6061-T6\"\n}\n```\n\nPOST it with `curl`:\n\n```text\ncurl -sS -X POST \"{KB_HOST}\u002Fapi\u002Fcheck-context\" -H \"Content-Type: application\u002Fjson\" --data-binary \"@\u003Ccontext.json>\"\n```\n\nReact to each result:\n\n- `pass`: continue;\n- `fail`: stop CAD work and fix the input, explaining the rule and change;\n- `warn`: flag it and fix when possible;\n- `advisory`: apply it as a design constraint;\n- `na`: ignore it.\n\nDo not proceed while `summary.fail` is greater than zero.\n\n## Phase 5: standards on demand\n\nQuery only the table needed for the current decision:\n\n- `GET \u002Fapi\u002Fstandards\u002Fmaterials[\u002F\u003Cname>]` for density, yield, and modulus;\n- `GET \u002Fapi\u002Fstandards\u002Ffits` for ISO 286 hole and shaft deviations;\n- `GET \u002Fapi\u002Fstandards\u002Fclearance_holes[\u002F\u003Cdesignation>]` for ISO 273 holes;\n- `GET \u002Fapi\u002Fstandards\u002Ftolerances_iso2768` for general tolerances;\n- `GET \u002Fapi\u002Fstandards\u002Ffasteners[\u002F\u003Cdesignation>]` for fastener geometry;\n- `GET \u002Fapi\u002Fstandards\u002Fsheet_metal_gauges` for gauge thickness;\n- `GET \u002Fapi\u002Fstandards\u002Fpreferred_numbers` for R-series dimensions.\n\nRecord units. The KB database convention is mm, MPa, and g\u002Fcm3.\n\n## Phase 6: final rule check\n\nAfter geometry is complete and before final save or export, POST a more\ncomplete final context to `\u002Fapi\u002Fcheck-context`. Resolve every `fail`; document\nall advisories in the session `issues` narrative.\n\n## Offline and error behavior\n\n- Unreachable server: record `KB offline - proceeding without pre-start\n  checks` and continue using verified engineering context.\n- Search `404`: continue with available knowledge.\n- Check-context `422`: retry once with fewer fields, then continue and record\n  the issue.\n- `5xx` or timeout: skip the failed phase and record it.\n\nThe KB accelerates the task; it is not a gatekeeper.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FErfouni\u002Fsolidworks-GPT-plugin\u002Fplugins\u002Fsolidworks-gpt-plugin\u002Fskills\u002Fsw-pre-start",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":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill sw-pre-start",{"tool":66,"command":67},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill sw-pre-start",{"tool":69,"command":70},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill sw-pre-start","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FErfouni\u002Fsolidworks-GPT-plugin\u002Fplugins\u002Fsolidworks-gpt-plugin\u002Fskills\u002Fsw-pre-start\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"agents\u002Fopenai.yaml","REFERENCE","参考文档",214,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FErfouni\u002Fsolidworks-GPT-plugin\u002Fplugins\u002Fsolidworks-gpt-plugin\u002Fskills\u002Fsw-pre-start\u002Fagents\u002Fopenai.yaml",[81,91,99,107,115,123],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":90},"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":90},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":90},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":90},"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":90},"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":90},"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",[],[]]