[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MD836JHH4F7GS63MJXA7HX":3,"skill-same:01M6MD836JHH4F7GS63MJXA7HX":98},{"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":26,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":68,"commitSha":69,"skillDirectory":70,"forksCount":71,"repositoryHtmlUrl":72,"repositoryHomepageUrl":73,"ownerHtmlUrl":74,"ownerBlogUrl":75,"ownerDescription":76,"updatedAt":77,"install":78,"resources":91},"01M6MD836JHH4F7GS63MJXA7HX","dvp-test-plan",null,"Design Verification Plan and Report (DVP&R) — build or review a test plan that links each DFMEA failure mode to a specific test, pass\u002Ffail criterion, sample size, and timing. Use when creating a DVP for a new design, reviewing a supplier's DVP for completeness, or auditing whether all design risks are covered by validation testing. Covers IATF 16949 §8.3.4.3 and AIAG APQP Phase 2.","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\u002Fplanning\u002Fdvp-test-plan\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"test","test plan","plan","dvp test plan","completeness","new","2026","automotive","when","phase","apqp","for","mode","links","electronics","timing","testing","medical","sample","general","use","verification","planning","review","design","2026-11-10 10:12:30",false,"---\nname: dvp-test-plan\ndescription: >-\n  Design Verification Plan and Report (DVP&R) — build or review a test plan that links each DFMEA\n  failure mode to a specific test, pass\u002Ffail criterion, sample size, and timing. Use when creating\n  a DVP for a new design, reviewing a supplier's DVP for completeness, or auditing whether all\n  design risks are covered by validation testing. Covers IATF 16949 §8.3.4.3 and AIAG APQP Phase 2.\nlicense: MIT\nmetadata:\n  author: RBraga01\n  version: \"1.1\"\n  iso-9001: \"8.3.4\"\n  iatf-16949: \"8.3.4.3\"\n  domain: quality-engineering\n  subdomain: planning\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: \"IATF 16949:2016 §8.3.4.3 \u002F AIAG APQP 2nd Edition\"\n---\n\n# Design Verification Plan and Report (DVP&R)\n\n## When to use\n\nUse this skill when:\n- Creating a DVP for a new part design during APQP Phase 2\n- Reviewing a supplier's DVP for completeness and DFMEA alignment\n- Determining which tests are required for a specific failure mode or design characteristic\n- Tracking test completion and recording results (the \"R\" in DVP&R)\n- Assessing whether a design change requires additional validation testing\n\n## Prerequisites\n\n- DFMEA with all failure modes identified and AP ratings assigned\n- Engineering drawing with all characteristics defined\n- Customer design specifications and performance requirements\n- List of applicable standards and test methods (customer spec, ISO, SAE, etc.)\n\n## Workflow\n\n### Step 1 — Understand the DVP structure\n\nThe DVP&R is a table with one row per test. Each test must address at least one failure mode or design characteristic from the DFMEA.\n\n**The linkage rule:** Every H-AP (High Action Priority) failure mode in the DFMEA must have at least one corresponding test in the DVP. If a failure mode has no test, document why (e.g., analysis-only justification with sign-off).\n\n### Step 2 — Build each DVP row\n\n| Column | What to enter |\n|--------|--------------|\n| Test number | Sequential reference (e.g., DVP-001) |\n| DFMEA reference | Failure mode number(s) this test addresses |\n| Test name \u002F description | Specific name of the test (not \"durability test\" — use \"salt spray 240h per ASTM B117\") |\n| Test specification | Standard or specification number with version (e.g., ASTM B117-19, SAE J2530, customer spec DS-XYZ) |\n| Pass\u002Ffail criteria | Exact acceptance criteria (e.g., \"no rust after 240h\", \"burst pressure > 150 bar\", \"dimension within ±0.05 mm\") |\n| Sample size | Number of parts to test |\n| Who performs | Internal lab, external accredited lab, customer lab |\n| Phase | P = Prototype, PL = Pre-launch, PR = Production |\n| Planned date | Date test is scheduled to complete |\n| Actual date | Date test was completed |\n| Result | Pass \u002F Fail \u002F In progress |\n| Report reference | Lab report number or document reference |\n| Comments | Failures, deviations, re-test requirements |\n\n### Step 3 — Determine required tests\n\nFor each DFMEA failure mode, identify the test category:\n\n**Functional \u002F performance tests:**\n- Tests that verify the product performs its intended function\n- Examples: burst pressure, tensile strength, electrical resistance, flow rate\n- Must demonstrate the product meets its design intent specifications\n\n**Environmental \u002F durability tests:**\n- Tests that simulate the product's operating environment over its design life\n- Examples: thermal cycling, salt spray, vibration, UV exposure, humidity\n- Duration and cycles must represent the design life or accelerated equivalent\n\n**Safety \u002F regulatory tests:**\n- Tests required by law, regulation, or homologation\n- Examples: ECE R10 (EMC), FMVSS standards, ECE R94\u002FR95 (crash), REACH, RoHS\n- Must be performed by accredited lab; results must accompany PPAP\n\n**Dimensional \u002F material tests:**\n- Verification that design dimensions and material properties are achieved\n- Examples: 3D scan, CMM, tensile test, hardness test, chemical composition\n- Must reference the specific drawing characteristic or material specification\n\n**Reliability \u002F life tests:**\n- Tests that verify the product meets its reliability target (e.g., B10 life)\n- Examples: fatigue testing, accelerated aging, wear testing\n- Test plan must include correlation between accelerated test and field life\n\n### Step 4 — Populate timing per APQP phase\n\n| Phase | Tests due |\n|-------|-----------|\n| Prototype (P) | Tests on design concept — functional, dimensional, preliminary environmental |\n| Pre-launch (PL) | Tests on tooled parts — full environmental, durability, all safety\u002Fregulatory |\n| Production (PR) | Confirmation tests on production parts — dimensional, safety, any tests with production-specific requirements |\n\nNot all tests need to run in all phases. Focus safety and regulatory tests on Pre-launch or Production parts.\n\n### Step 5 — Track completion (the \"R\" in DVP&R)\n\nUpdate the DVP after each test:\n- Record actual completion date\n- Record Pass\u002FFail result\n- For any Fail: log a DFMEA action (or open an 8D if failure escapes to customer)\n- Re-test after corrective action — reference the re-test as a new row with the original DVP number + suffix (e.g., DVP-012-R1)\n\nAt PPAP submission: all DVP tests must show \"Pass\" or have a documented customer-approved deviation. If a test is still in progress at PPAP submission (e.g., a long-duration life test), a formal customer deviation request must be submitted with: the test in progress, the expected completion date, the interim risk assessment, and the customer's written acceptance. The PPAP approval will be conditional until the test completes with a Pass result.\n\n**Engineering changes:** If the DFMEA is updated during the design phase and adds new H-AP failure modes, the DVP must be updated to cover them before the next gate review. A DVP revision that is behind the current DFMEA revision is a gap — the DVP&R revision must match or exceed the DFMEA revision at PPAP submission.\n\n### Step 6 — Audit an existing DVP\n\nWhen reviewing a supplier's or internal DVP, check:\n\n- [ ] Every H-AP DFMEA failure mode has at least one corresponding test\n- [ ] Test specifications reference a specific standard or document (not \"internal test\")\n- [ ] Pass\u002Ffail criteria are objective and measurable (not \"acceptable appearance\")\n- [ ] Sample sizes are adequate (not \"1 sample\" for durability\u002Flife tests)\n- [ ] Safety and regulatory tests are assigned to an accredited external lab\n- [ ] All results show \"Pass\" (or documented deviations with customer approval)\n- [ ] Failed tests have a corresponding DFMEA update or corrective action reference\n- [ ] DVP revision is aligned with the current DFMEA revision\n\n## Validation criteria\n\nA complete DVP&R for PPAP submission must:\n- Reference every H-AP failure mode from the DFMEA\n- Have specific, standard-referenced test methods (not \"per engineering judgement\")\n- Show Pass results for all tests (or customer-approved deviations)\n- Have accredited lab reports for all safety\u002Fregulatory tests\n- Be signed off by design engineering and quality\n\n## Common mistakes\n\n- DVP created with generic tests not linked to specific DFMEA failure modes\n- Pass\u002Ffail criteria defined as \"meets spec\" without stating what the spec is\n- All tests assigned to internal lab when regulatory tests require external accreditation\n- DVP not updated when DFMEA adds new H-AP failure modes during design reviews\n- Re-tests after failures not documented — original Fail result erased\n- Sample size of 1 for durability or life tests (statistically meaningless)\n- DVP not updated to \"Report\" status at PPAP — submitted as plan, not results\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 guidance for tests in-progress at PPAP submission (customer deviation process); added DVP revision synchronisation with DFMEA requirement |\n","# Design Verification Plan and Report (DVP&R)\n\n## When to use\n\nUse this skill when:\n- Creating a DVP for a new part design during APQP Phase 2\n- Reviewing a supplier's DVP for completeness and DFMEA alignment\n- Determining which tests are required for a specific failure mode or design characteristic\n- Tracking test completion and recording results (the \"R\" in DVP&R)\n- Assessing whether a design change requires additional validation testing\n\n## Prerequisites\n\n- DFMEA with all failure modes identified and AP ratings assigned\n- Engineering drawing with all characteristics defined\n- Customer design specifications and performance requirements\n- List of applicable standards and test methods (customer spec, ISO, SAE, etc.)\n\n## Workflow\n\n### Step 1 — Understand the DVP structure\n\nThe DVP&R is a table with one row per test. Each test must address at least one failure mode or design characteristic from the DFMEA.\n\n**The linkage rule:** Every H-AP (High Action Priority) failure mode in the DFMEA must have at least one corresponding test in the DVP. If a failure mode has no test, document why (e.g., analysis-only justification with sign-off).\n\n### Step 2 — Build each DVP row\n\n| Column | What to enter |\n|--------|--------------|\n| Test number | Sequential reference (e.g., DVP-001) |\n| DFMEA reference | Failure mode number(s) this test addresses |\n| Test name \u002F description | Specific name of the test (not \"durability test\" — use \"salt spray 240h per ASTM B117\") |\n| Test specification | Standard or specification number with version (e.g., ASTM B117-19, SAE J2530, customer spec DS-XYZ) |\n| Pass\u002Ffail criteria | Exact acceptance criteria (e.g., \"no rust after 240h\", \"burst pressure > 150 bar\", \"dimension within ±0.05 mm\") |\n| Sample size | Number of parts to test |\n| Who performs | Internal lab, external accredited lab, customer lab |\n| Phase | P = Prototype, PL = Pre-launch, PR = Production |\n| Planned date | Date test is scheduled to complete |\n| Actual date | Date test was completed |\n| Result | Pass \u002F Fail \u002F In progress |\n| Report reference | Lab report number or document reference |\n| Comments | Failures, deviations, re-test requirements |\n\n### Step 3 — Determine required tests\n\nFor each DFMEA failure mode, identify the test category:\n\n**Functional \u002F performance tests:**\n- Tests that verify the product performs its intended function\n- Examples: burst pressure, tensile strength, electrical resistance, flow rate\n- Must demonstrate the product meets its design intent specifications\n\n**Environmental \u002F durability tests:**\n- Tests that simulate the product's operating environment over its design life\n- Examples: thermal cycling, salt spray, vibration, UV exposure, humidity\n- Duration and cycles must represent the design life or accelerated equivalent\n\n**Safety \u002F regulatory tests:**\n- Tests required by law, regulation, or homologation\n- Examples: ECE R10 (EMC), FMVSS standards, ECE R94\u002FR95 (crash), REACH, RoHS\n- Must be performed by accredited lab; results must accompany PPAP\n\n**Dimensional \u002F material tests:**\n- Verification that design dimensions and material properties are achieved\n- Examples: 3D scan, CMM, tensile test, hardness test, chemical composition\n- Must reference the specific drawing characteristic or material specification\n\n**Reliability \u002F life tests:**\n- Tests that verify the product meets its reliability target (e.g., B10 life)\n- Examples: fatigue testing, accelerated aging, wear testing\n- Test plan must include correlation between accelerated test and field life\n\n### Step 4 — Populate timing per APQP phase\n\n| Phase | Tests due |\n|-------|-----------|\n| Prototype (P) | Tests on design concept — functional, dimensional, preliminary environmental |\n| Pre-launch (PL) | Tests on tooled parts — full environmental, durability, all safety\u002Fregulatory |\n| Production (PR) | Confirmation tests on production parts — dimensional, safety, any tests with production-specific requirements |\n\nNot all tests need to run in all phases. Focus safety and regulatory tests on Pre-launch or Production parts.\n\n### Step 5 — Track completion (the \"R\" in DVP&R)\n\nUpdate the DVP after each test:\n- Record actual completion date\n- Record Pass\u002FFail result\n- For any Fail: log a DFMEA action (or open an 8D if failure escapes to customer)\n- Re-test after corrective action — reference the re-test as a new row with the original DVP number + suffix (e.g., DVP-012-R1)\n\nAt PPAP submission: all DVP tests must show \"Pass\" or have a documented customer-approved deviation. If a test is still in progress at PPAP submission (e.g., a long-duration life test), a formal customer deviation request must be submitted with: the test in progress, the expected completion date, the interim risk assessment, and the customer's written acceptance. The PPAP approval will be conditional until the test completes with a Pass result.\n\n**Engineering changes:** If the DFMEA is updated during the design phase and adds new H-AP failure modes, the DVP must be updated to cover them before the next gate review. A DVP revision that is behind the current DFMEA revision is a gap — the DVP&R revision must match or exceed the DFMEA revision at PPAP submission.\n\n### Step 6 — Audit an existing DVP\n\nWhen reviewing a supplier's or internal DVP, check:\n\n- [ ] Every H-AP DFMEA failure mode has at least one corresponding test\n- [ ] Test specifications reference a specific standard or document (not \"internal test\")\n- [ ] Pass\u002Ffail criteria are objective and measurable (not \"acceptable appearance\")\n- [ ] Sample sizes are adequate (not \"1 sample\" for durability\u002Flife tests)\n- [ ] Safety and regulatory tests are assigned to an accredited external lab\n- [ ] All results show \"Pass\" (or documented deviations with customer approval)\n- [ ] Failed tests have a corresponding DFMEA update or corrective action reference\n- [ ] DVP revision is aligned with the current DFMEA revision\n\n## Validation criteria\n\nA complete DVP&R for PPAP submission must:\n- Reference every H-AP failure mode from the DFMEA\n- Have specific, standard-referenced test methods (not \"per engineering judgement\")\n- Show Pass results for all tests (or customer-approved deviations)\n- Have accredited lab reports for all safety\u002Fregulatory tests\n- Be signed off by design engineering and quality\n\n## Common mistakes\n\n- DVP created with generic tests not linked to specific DFMEA failure modes\n- Pass\u002Ffail criteria defined as \"meets spec\" without stating what the spec is\n- All tests assigned to internal lab when regulatory tests require external accreditation\n- DVP not updated when DFMEA adds new H-AP failure modes during design reviews\n- Re-tests after failures not documented — original Fail result erased\n- Sample size of 1 for durability or life tests (statistically meaningless)\n- DVP not updated to \"Report\" status at PPAP — submitted as plan, not results\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 guidance for tests in-progress at PPAP submission (customer deviation process); added DVP revision synchronisation with DFMEA requirement |\n",{"name":5,"license":15,"metadata":57,"description":7},{"author":58,"domain":59,"status":60,"created":61,"version":62,"iso-9001":63,"subdomain":49,"iatf-16949":64,"industries":65,"updated_by":66,"reviewed_by":58,"last_updated":61,"standard_edition":67},"RBraga01","quality-engineering","approved","2026-06-06","1.1","8.3.4","8.3.4.3","automotive,electronics,aerospace,medical,general","migmcc","IATF 16949:2016 §8.3.4.3 \u002F AIAG APQP 2nd Edition","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fplanning\u002Fdvp-test-plan",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":79,"prompt":89,"zipAvailable":90},[80,83,86],{"tool":81,"command":82},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dvp-test-plan",{"tool":84,"command":85},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dvp-test-plan",{"tool":87,"command":88},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill dvp-test-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fplanning\u002Fdvp-test-plan\u002FSKILL.md",true,[92],{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fdvp-template.md","REFERENCE","参考文档",25437,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fplanning\u002Fdvp-test-plan\u002Freferences\u002Fdvp-template.md",[99,108,116,124,132,140],{"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":15,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":107},"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":107},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":107},"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":107},"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":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":107},"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":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":107},"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",[],[]]