[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MDA31G42YYATBA63RCMY1Z":3,"skill-same:01M6MDA31G42YYATBA63RCMY1Z":87},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6MDA31G42YYATBA63RCMY1Z","supplier-scar",null,"Supplier Corrective Action Request (SCAR) — escalate a supplier non-conformance to a formal corrective action request, define response requirements, evaluate the supplier's 8D response, and verify effectiveness. Use when an NCR escalates to a SCAR, when a supplier delivers repeated non-conformances, or when a field failure is traced to a supplier. Covers ISO 9001 §8.4 and IATF 16949 §8.4.1.","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\u002Fsupplier-quality\u002Fsupplier-scar\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"supplier scar","escalate","2026","automotive","when","request","evaluate","conformance","action","corrective action","electronics","engineering","medical","iso","define","requirements","general","use","quality","aerospace","verify","2026-11-10 10:12:30",false,"---\nname: supplier-scar\ndescription: >-\n  Supplier Corrective Action Request (SCAR) — escalate a supplier non-conformance to a formal\n  corrective action request, define response requirements, evaluate the supplier's 8D response,\n  and verify effectiveness. Use when an NCR escalates to a SCAR, when a supplier delivers\n  repeated non-conformances, or when a field failure is traced to a supplier. Covers ISO 9001 §8.4\n  and IATF 16949 §8.4.1.\nlicense: MIT\nmetadata:\n  author: RBraga01\n  version: \"1.1\"\n  iso-9001: \"8.4, 10.2\"\n  iatf-16949: \"8.4.1, 10.2.3\"\n  domain: quality-engineering\n  subdomain: supplier-quality\n  industries: automotive,electronics,aerospace,medical,general\n  status: approved\n  created: \"2026-06-06\"\n  last_updated: \"2026-06-06\"\n  updated_by: migmcc\n  reviewed_by: RBraga01\n  standard_edition: \"ISO 9001:2015 §8.4 \u002F IATF 16949:2016 §8.4.1\"\n---\n\n# Supplier Corrective Action Request (SCAR)\n\n## When to use\n\nUse this skill when:\n- A supplier NCR requires a formal corrective action (beyond simple return\u002Freplacement)\n- A supplier has delivered the same non-conformance twice or more\n- A non-conformance has caused a production line stoppage, customer complaint, or field failure\n- A supplier's quality performance score falls below the defined threshold\n- An OEM customer issues a concern that is traced to a sub-supplier\n- Preparing a SCAR, evaluating a supplier's 8D response, or conducting an effectiveness review\n\n## Prerequisites\n\n- Non-conformance documented (NCR or equivalent) with: part number, description, quantity, measured evidence\n- Supplier code, contact name, and corrective action coordinator identified\n- SCAR response timeline agreed (typically 24h for D3, 30 days for full 8D)\n- Historical data: previous SCARs, PPM trend, quality score for this supplier\n\n## Workflow\n\n### Step 1 — Escalation criteria: when does an NCR become a SCAR?\n\nIssue a SCAR when any of the following conditions are met:\n\n| Trigger | Description |\n|---------|-------------|\n| Severity — Critical | Non-conformance affects safety, regulatory compliance, or field function |\n| Severity — Customer impact | Non-conformance reached the end customer or caused a production line stop |\n| Recurrence | Same defect or same part rejected for the second time within 12 months |\n| Volume | Rejection of an entire lot or >5% of a delivery |\n| Systemic risk | Evidence that the supplier's process or system is inadequate (missing controls, no inspection, operator error on SC characteristic) |\n| Customer escalation | An OEM customer has issued a concern traceable to this supplier |\n\nDo NOT issue a SCAR for every NCR — use NCR + return for minor first-occurrence issues and reserve SCAR for systemic or high-risk situations.\n\n---\n\n### Step 2 — Write the SCAR\n\nThe SCAR document must contain:\n\n**Header:**\n- SCAR number (unique, traceable)\n- Date issued\n- Supplier name, supplier code, contact person\n- Issued by (supplier quality engineer name)\n\n**Non-conformance description:**\n- Part number and revision\n- Delivery reference (PO number, lot number, delivery note)\n- Quantity delivered \u002F quantity non-conforming \u002F % affected\n- Defect description in objective-evidence language (measured values vs. specification — not opinions)\n- Customer impact (if applicable): production stop, customer complaint, field return\n- Reference to the NCR (attach or link)\n\n**Response requirements:**\nSpecify exactly what the supplier must provide and by when:\n\n| Deliverable | Typical deadline |\n|-------------|-----------------|\n| D3 Immediate Containment Action (ICA) | 24–48 hours |\n| D4 Root Cause (occurrence AND escape) | 7–14 days |\n| D5–D6 Permanent Corrective Actions with evidence | 30 days |\n| D7 Systemic prevention (PFMEA, CP, WI updates) | 30 days |\n| Full 8D report | 30 days |\n\nAlways require TWO root causes: why the defect was produced (occurrence) AND why it was not detected (escape).\n\n**Containment verification:**\nState that the supplier must confirm:\n- All suspect stock at their facility has been identified and quarantined\n- All stock in transit has been recalled or placed on hold\n- All stock at your facility has been segregated (include quantity)\n- A containment verification plan is in place before any further shipments are accepted\n\n---\n\n### Step 3 — Evaluate the supplier's 8D response\n\nUse the 8D Evaluator methodology (skill: `8d-problem-solving`) to review the supplier's response. Focus on the most common SCAR-specific failures:\n\n**D3 — Containment:**\n- Is the containment in PAST TENSE? (If it says \"we will inspect going forward\" — reject)\n- Does it cover all locations (supplier, transit, your facility, customer)?\n- Is there a verification result (quantity sorted, quantity rejected, quantity cleared)?\n\n**D4 — Root cause:**\n- Are BOTH causes identified: occurrence (why produced) AND escape (why not caught)?\n- Is the root cause supported by evidence, or is it opinion?\n- Reject: \"human error\", \"operator oversight\", \"customer changed specs\" — always ask why it was possible\n- Verify: if the supplier claims \"operator error\", ask why the error was not detected by the control plan\n\n**D5 — Permanent corrective action:**\n- Does the PCA directly address the confirmed root cause?\n- Is \"retrain the operator\" the only action? If so, reject — training is not a systemic fix\n- Is there a poka-yoke or process change that makes the defect impossible or immediately detectable?\n\n**D7 — Systemic prevention:**\n- Has the PFMEA been updated to reflect the failure mode and new controls?\n- Has the Action Priority (AP) been revised in the PFMEA after verified corrective action? The revised AP must be lower than the original or documented with justification — AP revision is only valid after D6 effectiveness is confirmed, not at planning stage.\n- Has the Control Plan been updated?\n- Have Work Instructions been updated?\n- Has horizontal deployment been considered (same process at other lines\u002Fplants)?\n\n**D6 — Verification:**\n- Is there production data showing the PCA is effective?\n- What quantity was run? Over what period?\n- What is the measured improvement (before\u002Fafter comparison)?\n\n---\n\n### Step 4 — Issue a SCAR response rejection\n\nIf the supplier's 8D response does not meet the gate criteria, reject it formally:\n\n**Rejection notice must specify:**\n- Which discipline(s) failed and why (specific, not generic)\n- What is required in the revised response\n- Revised deadline for resubmission\n\nDo not accept a response that:\n- Has no evidence of D3 completion (only a plan)\n- States \"human error\" as the final root cause without systemic analysis\n- Lists only training as the PCA\n- Has no PFMEA or CP update in D7\n- Shows no production data in D6\n\n---\n\n### Step 5 — Effectiveness verification\n\n30–90 days after PCA implementation, verify that the corrective action is effective:\n\n**Methods:**\n- Monitor incoming quality data: zero recurrence of the same defect in the next X deliveries\n- Review updated PFMEA and Control Plan (request current revision, verify D4 failure mode is addressed)\n- On-site verification: audit the specific process step where the defect occurred (use VDA 6.3 P6 questions for that step)\n- Request production data showing Cpk improvement on the relevant characteristic\n\n**Close the SCAR when:**\n- Zero recurrence of the same non-conformance for the agreed monitoring period (typically 3–6 months)\n- Updated PFMEA, CP, and WI documents received and verified\n- Effectiveness data reviewed and accepted\n\n**If recurrence occurs during monitoring:**\n- Escalate to supplier management (not just quality coordinator)\n- Consider: production stop, new supplier qualification, customer notification\n- Issue a new SCAR referencing the previous one as evidence of systemic failure\n\n---\n\n### Step 6 — Supplier performance tracking\n\nLink every SCAR to the supplier's quality performance record:\n- PPM trend (Parts Per Million non-conforming)\n- SCAR open count and average response time\n- Closure rate (closed on time vs. overdue)\n- Recurrence rate (same defect within 12 months of a previous SCAR)\n\nSuppliers with repeated SCARs or recurrences should be placed on:\n- **Controlled shipping** — every delivery inspected before acceptance (in automotive: CS1 = supplier-managed 100% sort; CS2 = customer-managed sort at supplier's cost)\n- **Supplier improvement plan** — formal APQP-style corrective programme\n- **Qualification review** — potential re-qualification or replacement\n\n**Warranty cost recovery \u002F debit note risk:** In automotive OEM supply chains, SCARs that result in field failures or warranty claims can trigger financial recovery. The OEM issues a warranty debit note to the Tier 1, who cascades it to the responsible sub-supplier via SCAR. Each SCAR must therefore document whether the non-conformance caused any field or warranty cost — this determines whether cost recovery applies. A SCAR without this assessment is incomplete for OEM reporting purposes. If warranty cost recovery is raised, escalate immediately to commercial and legal before responding to the OEM.\n\n---\n\n## Validation criteria\n\nA SCAR is closed when:\n- Full 8D submitted with both root causes confirmed (occurrence AND escape)\n- Permanent corrective action verified with production data (D6)\n- PFMEA, Control Plan, and Work Instructions updated and received (D7)\n- No recurrence of the same non-conformance during the agreed monitoring period\n- Closure signed off by Supplier Quality Engineer and documented in the supplier record\n\n## Common mistakes\n\n- Issuing a SCAR for every NCR — dilutes the severity signal; suppliers stop taking SCARs seriously\n- Accepting a D3 response that is a plan (\"we will inspect\") rather than a completed action\n- Closing the SCAR when the 8D is submitted rather than when effectiveness is verified\n- Accepting \"human error\" or \"operator training\" without requiring a systemic root cause\n- Not updating the supplier performance record — next engineer doesn't know the history\n- Allowing the SCAR to stay open indefinitely with no escalation — sets the precedent that deadlines are negotiable\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-06 | @RBraga01 | Initial release |\n| 1.1 | 2026-06-06 | @migmcc | Added AP revision check in D7 evaluation; added warranty cost recovery \u002F debit note risk in Step 6; added CS1\u002FCS2 controlled shipping reference |\n","# Supplier Corrective Action Request (SCAR)\n\n## When to use\n\nUse this skill when:\n- A supplier NCR requires a formal corrective action (beyond simple return\u002Freplacement)\n- A supplier has delivered the same non-conformance twice or more\n- A non-conformance has caused a production line stoppage, customer complaint, or field failure\n- A supplier's quality performance score falls below the defined threshold\n- An OEM customer issues a concern that is traced to a sub-supplier\n- Preparing a SCAR, evaluating a supplier's 8D response, or conducting an effectiveness review\n\n## Prerequisites\n\n- Non-conformance documented (NCR or equivalent) with: part number, description, quantity, measured evidence\n- Supplier code, contact name, and corrective action coordinator identified\n- SCAR response timeline agreed (typically 24h for D3, 30 days for full 8D)\n- Historical data: previous SCARs, PPM trend, quality score for this supplier\n\n## Workflow\n\n### Step 1 — Escalation criteria: when does an NCR become a SCAR?\n\nIssue a SCAR when any of the following conditions are met:\n\n| Trigger | Description |\n|---------|-------------|\n| Severity — Critical | Non-conformance affects safety, regulatory compliance, or field function |\n| Severity — Customer impact | Non-conformance reached the end customer or caused a production line stop |\n| Recurrence | Same defect or same part rejected for the second time within 12 months |\n| Volume | Rejection of an entire lot or >5% of a delivery |\n| Systemic risk | Evidence that the supplier's process or system is inadequate (missing controls, no inspection, operator error on SC characteristic) |\n| Customer escalation | An OEM customer has issued a concern traceable to this supplier |\n\nDo NOT issue a SCAR for every NCR — use NCR + return for minor first-occurrence issues and reserve SCAR for systemic or high-risk situations.\n\n---\n\n### Step 2 — Write the SCAR\n\nThe SCAR document must contain:\n\n**Header:**\n- SCAR number (unique, traceable)\n- Date issued\n- Supplier name, supplier code, contact person\n- Issued by (supplier quality engineer name)\n\n**Non-conformance description:**\n- Part number and revision\n- Delivery reference (PO number, lot number, delivery note)\n- Quantity delivered \u002F quantity non-conforming \u002F % affected\n- Defect description in objective-evidence language (measured values vs. specification — not opinions)\n- Customer impact (if applicable): production stop, customer complaint, field return\n- Reference to the NCR (attach or link)\n\n**Response requirements:**\nSpecify exactly what the supplier must provide and by when:\n\n| Deliverable | Typical deadline |\n|-------------|-----------------|\n| D3 Immediate Containment Action (ICA) | 24–48 hours |\n| D4 Root Cause (occurrence AND escape) | 7–14 days |\n| D5–D6 Permanent Corrective Actions with evidence | 30 days |\n| D7 Systemic prevention (PFMEA, CP, WI updates) | 30 days |\n| Full 8D report | 30 days |\n\nAlways require TWO root causes: why the defect was produced (occurrence) AND why it was not detected (escape).\n\n**Containment verification:**\nState that the supplier must confirm:\n- All suspect stock at their facility has been identified and quarantined\n- All stock in transit has been recalled or placed on hold\n- All stock at your facility has been segregated (include quantity)\n- A containment verification plan is in place before any further shipments are accepted\n\n---\n\n### Step 3 — Evaluate the supplier's 8D response\n\nUse the 8D Evaluator methodology (skill: `8d-problem-solving`) to review the supplier's response. Focus on the most common SCAR-specific failures:\n\n**D3 — Containment:**\n- Is the containment in PAST TENSE? (If it says \"we will inspect going forward\" — reject)\n- Does it cover all locations (supplier, transit, your facility, customer)?\n- Is there a verification result (quantity sorted, quantity rejected, quantity cleared)?\n\n**D4 — Root cause:**\n- Are BOTH causes identified: occurrence (why produced) AND escape (why not caught)?\n- Is the root cause supported by evidence, or is it opinion?\n- Reject: \"human error\", \"operator oversight\", \"customer changed specs\" — always ask why it was possible\n- Verify: if the supplier claims \"operator error\", ask why the error was not detected by the control plan\n\n**D5 — Permanent corrective action:**\n- Does the PCA directly address the confirmed root cause?\n- Is \"retrain the operator\" the only action? If so, reject — training is not a systemic fix\n- Is there a poka-yoke or process change that makes the defect impossible or immediately detectable?\n\n**D7 — Systemic prevention:**\n- Has the PFMEA been updated to reflect the failure mode and new controls?\n- Has the Action Priority (AP) been revised in the PFMEA after verified corrective action? The revised AP must be lower than the original or documented with justification — AP revision is only valid after D6 effectiveness is confirmed, not at planning stage.\n- Has the Control Plan been updated?\n- Have Work Instructions been updated?\n- Has horizontal deployment been considered (same process at other lines\u002Fplants)?\n\n**D6 — Verification:**\n- Is there production data showing the PCA is effective?\n- What quantity was run? Over what period?\n- What is the measured improvement (before\u002Fafter comparison)?\n\n---\n\n### Step 4 — Issue a SCAR response rejection\n\nIf the supplier's 8D response does not meet the gate criteria, reject it formally:\n\n**Rejection notice must specify:**\n- Which discipline(s) failed and why (specific, not generic)\n- What is required in the revised response\n- Revised deadline for resubmission\n\nDo not accept a response that:\n- Has no evidence of D3 completion (only a plan)\n- States \"human error\" as the final root cause without systemic analysis\n- Lists only training as the PCA\n- Has no PFMEA or CP update in D7\n- Shows no production data in D6\n\n---\n\n### Step 5 — Effectiveness verification\n\n30–90 days after PCA implementation, verify that the corrective action is effective:\n\n**Methods:**\n- Monitor incoming quality data: zero recurrence of the same defect in the next X deliveries\n- Review updated PFMEA and Control Plan (request current revision, verify D4 failure mode is addressed)\n- On-site verification: audit the specific process step where the defect occurred (use VDA 6.3 P6 questions for that step)\n- Request production data showing Cpk improvement on the relevant characteristic\n\n**Close the SCAR when:**\n- Zero recurrence of the same non-conformance for the agreed monitoring period (typically 3–6 months)\n- Updated PFMEA, CP, and WI documents received and verified\n- Effectiveness data reviewed and accepted\n\n**If recurrence occurs during monitoring:**\n- Escalate to supplier management (not just quality coordinator)\n- Consider: production stop, new supplier qualification, customer notification\n- Issue a new SCAR referencing the previous one as evidence of systemic failure\n\n---\n\n### Step 6 — Supplier performance tracking\n\nLink every SCAR to the supplier's quality performance record:\n- PPM trend (Parts Per Million non-conforming)\n- SCAR open count and average response time\n- Closure rate (closed on time vs. overdue)\n- Recurrence rate (same defect within 12 months of a previous SCAR)\n\nSuppliers with repeated SCARs or recurrences should be placed on:\n- **Controlled shipping** — every delivery inspected before acceptance (in automotive: CS1 = supplier-managed 100% sort; CS2 = customer-managed sort at supplier's cost)\n- **Supplier improvement plan** — formal APQP-style corrective programme\n- **Qualification review** — potential re-qualification or replacement\n\n**Warranty cost recovery \u002F debit note risk:** In automotive OEM supply chains, SCARs that result in field failures or warranty claims can trigger financial recovery. The OEM issues a warranty debit note to the Tier 1, who cascades it to the responsible sub-supplier via SCAR. Each SCAR must therefore document whether the non-conformance caused any field or warranty cost — this determines whether cost recovery applies. A SCAR without this assessment is incomplete for OEM reporting purposes. If warranty cost recovery is raised, escalate immediately to commercial and legal before responding to the OEM.\n\n---\n\n## Validation criteria\n\nA SCAR is closed when:\n- Full 8D submitted with both root causes confirmed (occurrence AND escape)\n- Permanent corrective action verified with production data (D6)\n- PFMEA, Control Plan, and Work Instructions updated and received (D7)\n- No recurrence of the same non-conformance during the agreed monitoring period\n- Closure signed off by Supplier Quality Engineer and documented in the supplier record\n\n## Common mistakes\n\n- Issuing a SCAR for every NCR — dilutes the severity signal; suppliers stop taking SCARs seriously\n- Accepting a D3 response that is a plan (\"we will inspect\") rather than a completed action\n- Closing the SCAR when the 8D is submitted rather than when effectiveness is verified\n- Accepting \"human error\" or \"operator training\" without requiring a systemic root cause\n- Not updating the supplier performance record — next engineer doesn't know the history\n- Allowing the SCAR to stay open indefinitely with no escalation — sets the precedent that deadlines are negotiable\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-06 | @RBraga01 | Initial release |\n| 1.1 | 2026-06-06 | @migmcc | Added AP revision check in D7 evaluation; added warranty cost recovery \u002F debit note risk in Step 6; added CS1\u002FCS2 controlled shipping reference |\n",{"name":5,"license":15,"metadata":45,"description":7},{"author":46,"domain":47,"status":48,"created":49,"version":50,"iso-9001":51,"subdomain":52,"iatf-16949":53,"industries":54,"updated_by":55,"reviewed_by":46,"last_updated":49,"standard_edition":56},"RBraga01","quality-engineering","approved","2026-06-06","1.1","8.4, 10.2","supplier-quality","8.4.1, 10.2.3","automotive,electronics,aerospace,medical,general","migmcc","ISO 9001:2015 §8.4 \u002F IATF 16949:2016 §8.4.1","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fsupplier-quality\u002Fsupplier-scar",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":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill supplier-scar",{"tool":73,"command":74},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill supplier-scar",{"tool":76,"command":77},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill supplier-scar","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fsupplier-quality\u002Fsupplier-scar\u002FSKILL.md",true,[81],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fscar-template.md","REFERENCE","参考文档",24481,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fsupplier-quality\u002Fsupplier-scar\u002Freferences\u002Fscar-template.md",[88,97,105,113,121,129],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":96},"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":96},"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":96},"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":96},"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":96},"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":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":96},"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",[],[]]