[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MD8WRQWM3FJTTXQP1TAF85":3,"skill-same:01M6MD8WRQWM3FJTTXQP1TAF85":91},{"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":18,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6MD8WRQWM3FJTTXQP1TAF85","fishbone-analysis",null,"Build an Ishikawa diagram, cause and effect analysis, or 6M fishbone to brainstorm and categorise all possible causes before narrowing to root cause with 5-Why. Covers Man, Machine, Method, Material, Measurement, and Environment (Mother Nature). Essential for 8D D4 brainstorming sessions and CAPA root cause investigations.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fproblem-solving\u002Ffishbone-analysis\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"analysis","fishbone analysis","medical","2026","automotive","investigations","root cause","cause and effect","for","measurement","electronics","machine","problem","material","sessions","iso","essential","man","problem-solving","general","environment","effect","brainstorm","why","diagram","2026-11-10 10:12:30",false,"---\nname: fishbone-analysis\ndescription: >-\n  Build an Ishikawa diagram, cause and effect analysis, or 6M fishbone to brainstorm and\n  categorise all possible causes before narrowing to root cause with 5-Why. Covers Man,\n  Machine, Method, Material, Measurement, and Environment (Mother Nature). Essential for\n  8D D4 brainstorming sessions and CAPA root cause investigations.\nlicense: MIT\nmetadata:\n  author: RBraga01\n  version: \"1.1\"\n  iso-9001: \"10.2\"\n  iatf-16949: \"10.2.3\"\n  domain: quality-engineering\n  subdomain: problem-solving\n  industries: automotive,electronics,aerospace,medical,general\n  status: approved\n  created: \"2026-06-01\"\n  last_updated: \"2026-06-04\"\n  updated_by: migmcc\n  reviewed_by: RBraga01\n  standard_edition: \"ISO 9001:2015\"\n---\n\n# Fishbone (Ishikawa) Analysis\n\n## When to use\n\nUse fishbone analysis to brainstorm all possible causes of a quality problem **before** running 5-Why. It prevents tunnel vision and ensures no cause category is overlooked. Particularly valuable for complex defects with multiple potential contributing factors.\n\nTypical use: 8D D4 brainstorming session, CAPA root cause investigation, initial problem analysis.\n\n## Prerequisites\n\n- Problem clearly defined with Is\u002FIs-Not or 5W2H\n- Cross-functional team (quality, production, engineering at minimum)\n- Access to the process, machine, or product where defect occurred\n\n## Required Fishbone Checklist\n\n☐ Problem statement defined and agreed before starting — no cause language in the problem statement\n☐ All 6M categories addressed — at least one entry per M, or documented justification if a category is not applicable\n☐ Brainstorming completed before any evaluation or elimination — do not evaluate while generating\n☐ Every cause classified as Confirmed, Probable, or Unlikely using objective evidence — not opinion alone\n☐ Confirmed = supported by data or physical evidence; Probable = logical, consistent with Is\u002FIs-Not, not yet confirmed; Unlikely = contradicted by data\n☐ Confirmed and Probable causes cross-checked against existing PFMEA failure cause entries before proceeding to 5-Why\n☐ Each Confirmed or Probable cause carries forward to its own 5-Why chain\n☐ After root cause confirmed: horizontal deployment check — could the same cause exist in similar parts, processes, or product families?\n\n---\n\n## The 6M Framework\n\nThe six main \"bones\" of the fish. **All six must be addressed.** If a category genuinely does not apply, document: \"No causes identified in this category after structured team review — not applicable because [reason].\"\n\n### 1. Man (Human Factors)\n\nQuestions to ask:\n- Was the task performed by a trained, qualified operator?\n- Is competence documented and current?\n- Was the operator following the correct work instruction?\n- Could fatigue, shift change, or distraction contribute?\n- Is the task ergonomically difficult or error-prone?\n- Is the same defect found on all shifts or only one? (single-shift → operator-specific)\n\n### 2. Machine (Equipment)\n\nQuestions to ask:\n- Is the machine calibrated? When was it last calibrated? Is it within interval?\n- Has preventive maintenance been performed on schedule?\n- Are there any known deviations (vibration, wear, temperature drift)?\n- What is the machine capability (Cp, Cpk)? Is it capable for this feature?\n- Is tooling worn or damaged?\n- Is the jig or fixture functioning correctly?\n\n### 3. Method (Process)\n\nQuestions to ask:\n- Is there a documented work instruction for this operation?\n- Is the work instruction current and at the workstation?\n- Are process parameters (temperature, pressure, speed, torque) specified and controlled?\n- Is there a control plan entry for this process step?\n- Is the process sequence correct?\n- Is the method different between shifts or operators?\n\n### 4. Material (Input Material)\n\nQuestions to ask:\n- Does the defect correlate with a specific incoming batch or supplier lot?\n- Has the material specification been met (certificate of conformance, incoming inspection)?\n- Has the material been stored correctly (temperature, humidity, FIFO)?\n- Is the material traceable to its origin?\n- Has the supplier changed anything recently (sub-supplier, process, location)?\n\n### 5. Measurement (Measurement System)\n\nQuestions to ask:\n- Is the measurement system capable (MSA \u002F Gauge R&R performed)?\n- Is the gauge calibrated and within its calibration interval?\n- Is the measurement method standardised (same fixture, same operator technique)?\n- Could measurement error mask the defect (false acceptable)?\n- Are measurement results repeatable between operators?\n\n### 6. Mother Nature \u002F Environment\n\nQuestions to ask:\n- Does the defect correlate with ambient temperature or humidity?\n- Are there vibration or contamination sources nearby?\n- Is lighting adequate for visual inspection?\n- Are there seasonal patterns?\n- Does the cleanroom or ESD environment meet requirements?\n\n---\n\n## Workflow\n\n### Step 1 — Draw the diagram\n\nWrite the problem (effect) at the head (right side). Draw the spine. Add six main bones labelled with the 6M categories.\n\n### Step 2 — Brainstorm with the team\n\nFor each M category: \"What in [M] could cause [the problem]?\"\n\nCapture all ideas without judgment — quantity first, evaluation second. **Do not evaluate or discard during brainstorming.** Allocate 30–60 minutes minimum. Time pressure is the most common reason causes are missed.\n\nAdd each cause as a sub-bone to the relevant M category. Sub-bones can branch further (cause of a cause).\n\n### Step 3 — Evaluate and prioritise\n\nMark each cause as:\n- **Confirmed** (supported by data or direct physical evidence — not opinion)\n- **Probable** (logical, consistent with the Is\u002FIs-Not pattern, but not yet confirmed by data)\n- **Unlikely** (contradicted by data or the Is\u002FIs-Not pattern)\n\nDiscard Unlikely causes. Investigate Confirmed and Probable causes. A cause cannot be classified as Confirmed without objective evidence (measurement data, physical demonstration, reproduction test, or direct record review).\n\n### Step 4 — PFMEA cross-check\n\nBefore proceeding to 5-Why, cross-check Confirmed and Probable causes against the existing PFMEA:\n\n- Is this failure cause already documented in the PFMEA? If yes, was its detection or prevention control supposed to prevent this defect?\n- If the PFMEA did not capture this cause, flag it — the PFMEA must be updated after the root cause is confirmed.\n\n### Step 5 — Connect to 5-Why\n\nFor each Confirmed or Probable cause, run a [5-Why chain](..\u002F5why-root-cause\u002F) to reach the systemic root cause.\n\nThe fishbone identifies candidate causes. The 5-Why validates and deepens them.\n\nAfter root cause is confirmed: assess whether the same cause could exist in similar parts, processes, or product families. Document horizontal deployment actions if applicable.\n\n---\n\n## Output format\n\nDocument the fishbone as a table (easier to include in reports than a diagram):\n\n| M Category | Possible Cause | Evidence \u002F Status | Proceed to 5-Why? |\n|------------|----------------|-------------------|-------------------|\n| Man | Untrained operator | Training record missing for operator 12 | Yes |\n| Machine | Jig worn | Measured wear 0.3mm — limit 0.1mm | Yes |\n| Method | No contingency instruction | Work instruction reviewed — confirmed absent | Yes |\n| Material | Batch variation | No batch correlation found | No |\n| Measurement | Gauge repeatability | GR&R = 8% — acceptable | No |\n| Environment | Temperature | Controlled at 22°C ± 2°C — stable | No |\n\nAll 6M categories must appear in the table. If a category has no entries after structured brainstorming, document: \"No causes identified in this category after structured team review.\"\n\n---\n\n## Common mistakes\n\n- **Brainstorming under time pressure** — causes are missed; allocate 30–60 minutes minimum\n- **Stopping at first-level causes** — \"machine not calibrated\" is a cause, but add sub-bone: why was it not calibrated?\n- **Not using data to confirm\u002Fdiscard** — every cause must be validated against objective evidence, not just listed\n- **Using fishbone as the root cause** — fishbone finds candidate causes; 5-Why finds root cause\n- **Skipping categories** — if a category is left blank without justification, the analysis is incomplete and may miss the real cause\n- **Classifying causes as Confirmed based on team opinion** — Confirmed requires evidence; without it, classify as Probable and plan verification\n\n---\n\n## Output Format\n\nAt the start of each use, ask the user:\n\n> \"How would you like to receive the output?\n> **A** — Structured Markdown (formatted tables and sections, ready to copy)\n> **B** — Plain tables (simplified structure for Excel or Word)\n> **C** — Narrative report (flowing text for a formal document or email)\n>\n> Default: A.\"\n\nAdapt all output sections to the chosen format. If the platform or session context already defines a format preference, skip this question.\n\n## Changelog\n\n| Version | Date | Author | Change |\n|---------|------|--------|--------|\n| 1.0 | 2026-06-01 | @RBraga01 | Initial release |\n| 1.1 | 2026-06-04 | @migmcc | Polished 6M categories, added validation criteria and 5-Why integration |\n","# Fishbone (Ishikawa) Analysis\n\n## When to use\n\nUse fishbone analysis to brainstorm all possible causes of a quality problem **before** running 5-Why. It prevents tunnel vision and ensures no cause category is overlooked. Particularly valuable for complex defects with multiple potential contributing factors.\n\nTypical use: 8D D4 brainstorming session, CAPA root cause investigation, initial problem analysis.\n\n## Prerequisites\n\n- Problem clearly defined with Is\u002FIs-Not or 5W2H\n- Cross-functional team (quality, production, engineering at minimum)\n- Access to the process, machine, or product where defect occurred\n\n## Required Fishbone Checklist\n\n☐ Problem statement defined and agreed before starting — no cause language in the problem statement\n☐ All 6M categories addressed — at least one entry per M, or documented justification if a category is not applicable\n☐ Brainstorming completed before any evaluation or elimination — do not evaluate while generating\n☐ Every cause classified as Confirmed, Probable, or Unlikely using objective evidence — not opinion alone\n☐ Confirmed = supported by data or physical evidence; Probable = logical, consistent with Is\u002FIs-Not, not yet confirmed; Unlikely = contradicted by data\n☐ Confirmed and Probable causes cross-checked against existing PFMEA failure cause entries before proceeding to 5-Why\n☐ Each Confirmed or Probable cause carries forward to its own 5-Why chain\n☐ After root cause confirmed: horizontal deployment check — could the same cause exist in similar parts, processes, or product families?\n\n---\n\n## The 6M Framework\n\nThe six main \"bones\" of the fish. **All six must be addressed.** If a category genuinely does not apply, document: \"No causes identified in this category after structured team review — not applicable because [reason].\"\n\n### 1. Man (Human Factors)\n\nQuestions to ask:\n- Was the task performed by a trained, qualified operator?\n- Is competence documented and current?\n- Was the operator following the correct work instruction?\n- Could fatigue, shift change, or distraction contribute?\n- Is the task ergonomically difficult or error-prone?\n- Is the same defect found on all shifts or only one? (single-shift → operator-specific)\n\n### 2. Machine (Equipment)\n\nQuestions to ask:\n- Is the machine calibrated? When was it last calibrated? Is it within interval?\n- Has preventive maintenance been performed on schedule?\n- Are there any known deviations (vibration, wear, temperature drift)?\n- What is the machine capability (Cp, Cpk)? Is it capable for this feature?\n- Is tooling worn or damaged?\n- Is the jig or fixture functioning correctly?\n\n### 3. Method (Process)\n\nQuestions to ask:\n- Is there a documented work instruction for this operation?\n- Is the work instruction current and at the workstation?\n- Are process parameters (temperature, pressure, speed, torque) specified and controlled?\n- Is there a control plan entry for this process step?\n- Is the process sequence correct?\n- Is the method different between shifts or operators?\n\n### 4. Material (Input Material)\n\nQuestions to ask:\n- Does the defect correlate with a specific incoming batch or supplier lot?\n- Has the material specification been met (certificate of conformance, incoming inspection)?\n- Has the material been stored correctly (temperature, humidity, FIFO)?\n- Is the material traceable to its origin?\n- Has the supplier changed anything recently (sub-supplier, process, location)?\n\n### 5. Measurement (Measurement System)\n\nQuestions to ask:\n- Is the measurement system capable (MSA \u002F Gauge R&R performed)?\n- Is the gauge calibrated and within its calibration interval?\n- Is the measurement method standardised (same fixture, same operator technique)?\n- Could measurement error mask the defect (false acceptable)?\n- Are measurement results repeatable between operators?\n\n### 6. Mother Nature \u002F Environment\n\nQuestions to ask:\n- Does the defect correlate with ambient temperature or humidity?\n- Are there vibration or contamination sources nearby?\n- Is lighting adequate for visual inspection?\n- Are there seasonal patterns?\n- Does the cleanroom or ESD environment meet requirements?\n\n---\n\n## Workflow\n\n### Step 1 — Draw the diagram\n\nWrite the problem (effect) at the head (right side). Draw the spine. Add six main bones labelled with the 6M categories.\n\n### Step 2 — Brainstorm with the team\n\nFor each M category: \"What in [M] could cause [the problem]?\"\n\nCapture all ideas without judgment — quantity first, evaluation second. **Do not evaluate or discard during brainstorming.** Allocate 30–60 minutes minimum. Time pressure is the most common reason causes are missed.\n\nAdd each cause as a sub-bone to the relevant M category. Sub-bones can branch further (cause of a cause).\n\n### Step 3 — Evaluate and prioritise\n\nMark each cause as:\n- **Confirmed** (supported by data or direct physical evidence — not opinion)\n- **Probable** (logical, consistent with the Is\u002FIs-Not pattern, but not yet confirmed by data)\n- **Unlikely** (contradicted by data or the Is\u002FIs-Not pattern)\n\nDiscard Unlikely causes. Investigate Confirmed and Probable causes. A cause cannot be classified as Confirmed without objective evidence (measurement data, physical demonstration, reproduction test, or direct record review).\n\n### Step 4 — PFMEA cross-check\n\nBefore proceeding to 5-Why, cross-check Confirmed and Probable causes against the existing PFMEA:\n\n- Is this failure cause already documented in the PFMEA? If yes, was its detection or prevention control supposed to prevent this defect?\n- If the PFMEA did not capture this cause, flag it — the PFMEA must be updated after the root cause is confirmed.\n\n### Step 5 — Connect to 5-Why\n\nFor each Confirmed or Probable cause, run a [5-Why chain](..\u002F5why-root-cause\u002F) to reach the systemic root cause.\n\nThe fishbone identifies candidate causes. The 5-Why validates and deepens them.\n\nAfter root cause is confirmed: assess whether the same cause could exist in similar parts, processes, or product families. Document horizontal deployment actions if applicable.\n\n---\n\n## Output format\n\nDocument the fishbone as a table (easier to include in reports than a diagram):\n\n| M Category | Possible Cause | Evidence \u002F Status | Proceed to 5-Why? |\n|------------|----------------|-------------------|-------------------|\n| Man | Untrained operator | Training record missing for operator 12 | Yes |\n| Machine | Jig worn | Measured wear 0.3mm — limit 0.1mm | Yes |\n| Method | No contingency instruction | Work instruction reviewed — confirmed absent | Yes |\n| Material | Batch variation | No batch correlation found | No |\n| Measurement | Gauge repeatability | GR&R = 8% — acceptable | No |\n| Environment | Temperature | Controlled at 22°C ± 2°C — stable | No |\n\nAll 6M categories must appear in the table. If a category has no entries after structured brainstorming, document: \"No causes identified in this category after structured team review.\"\n\n---\n\n## Common mistakes\n\n- **Brainstorming under time pressure** — causes are missed; allocate 30–60 minutes minimum\n- **Stopping at first-level causes** — \"machine not calibrated\" is a cause, but add sub-bone: why was it not calibrated?\n- **Not using data to confirm\u002Fdiscard** — every cause must be validated against objective evidence, not just listed\n- **Using fishbone as the root cause** — fishbone finds candidate causes; 5-Why finds root cause\n- **Skipping categories** — if a category is left blank without justification, the analysis is incomplete and may miss the real cause\n- **Classifying causes as Confirmed based on team opinion** — Confirmed requires evidence; without it, classify as Probable and plan verification\n\n---\n\n## Output Format\n\nAt the start of each use, ask the user:\n\n> \"How would you like to receive the output?\n> **A** — Structured Markdown (formatted tables and sections, ready to copy)\n> **B** — Plain tables (simplified structure for Excel or Word)\n> **C** — Narrative report (flowing text for a formal document or email)\n>\n> Default: A.\"\n\nAdapt all output sections to the chosen format. If the platform or session context already defines a format preference, skip this question.\n\n## Changelog\n\n| Version | Date | Author | Change |\n|---------|------|--------|--------|\n| 1.0 | 2026-06-01 | @RBraga01 | Initial release |\n| 1.1 | 2026-06-04 | @migmcc | Polished 6M categories, added validation criteria and 5-Why integration |\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":50,"domain":51,"status":52,"created":53,"version":54,"iso-9001":55,"subdomain":37,"iatf-16949":56,"industries":57,"updated_by":58,"reviewed_by":50,"last_updated":59,"standard_edition":60},"RBraga01","quality-engineering","approved","2026-06-01","1.1","10.2","10.2.3","automotive,electronics,aerospace,medical,general","migmcc","2026-06-04","ISO 9001:2015","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fproblem-solving\u002Ffishbone-analysis",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":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fishbone-analysis",{"tool":77,"command":78},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fishbone-analysis",{"tool":80,"command":81},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fishbone-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fproblem-solving\u002Ffishbone-analysis\u002FSKILL.md",true,[85],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002F6m-category-guide.md","REFERENCE","参考文档",18580,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fproblem-solving\u002Ffishbone-analysis\u002Freferences\u002F6m-category-guide.md",[92,101,109,117,125,133],{"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":15,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":100},"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.","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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":100},"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":100},"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":100},"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":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":100},"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":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":100},"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",[],[]]