[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MD88PCXKBWR82EAR1VQR3E":3,"skill-same:01M6MD88PCXKBWR82EAR1VQR3E":89},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6MD88PCXKBWR82EAR1VQR3E","ppap",null,"Production Part Approval Process (PPAP) — verify PPAP submission level, audit all 18 elements, check completeness for customer approval, prepare PSW. Use when a supplier needs to submit parts for approval, when reviewing a PPAP package, or when determining which PPAP level is required. Covers AIAG PPAP 4th edition with Ford, BMW, VW, and Stellantis OEM-specific requirements.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fplanning\u002Fppap\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"medical","2026","automotive","when","submission","for","which","with","electronics","completeness","submit","customer","elements","requirements","general","check completeness","use","oem","check","verify","audit","package","planning","2026-11-10 10:12:30",false,"---\nname: ppap\ndescription: >-\n  Production Part Approval Process (PPAP) — verify PPAP submission level, audit all 18 elements,\n  check completeness for customer approval, prepare PSW. Use when a supplier needs to submit parts\n  for approval, when reviewing a PPAP package, or when determining which PPAP level is required.\n  Covers AIAG PPAP 4th edition with Ford, BMW, VW, and Stellantis OEM-specific requirements.\nlicense: MIT\nmetadata:\n  author: RBraga01\n  version: \"1.1\"\n  iso-9001: \"8.4\"\n  iatf-16949: \"8.3.4, 8.4.1\"\n  aiag-reference: \"AIAG PPAP 4th Edition\"\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: \"AIAG PPAP 4th Edition (2006)\"\n---\n\n# Production Part Approval Process (PPAP)\n\n## When to use\n\nUse this skill when:\n- A supplier must submit parts for customer approval before Start of Production (SOP)\n- A design change, process change, or engineering change requires re-submission\n- An OEM or Tier 1 customer requests a PPAP at a specific level\n- Reviewing or auditing an incoming PPAP package from a supplier\n- Determining what PPAP level is required for a given change\n\n## Prerequisites\n\n- Part number, revision level, and customer drawing\n- Bill of Materials (BOM) if applicable\n- Production process flow and manufacturing location confirmed\n- Customer's PPAP level requirement (Level 1–5) or change category known\n\n## Workflow\n\n### Step 1 — Determine the PPAP Level\n\n| Level | What must be submitted |\n|-------|----------------------|\n| 1 | Part Submission Warrant (PSW) only — no supporting documents unless requested |\n| 2 | PSW + designated samples + limited supporting data |\n| 3 | PSW + product samples + complete supporting data (default for new parts) |\n| 4 | PSW + other requirements as defined by the customer |\n| 5 | PSW + parts and complete supporting data — reviewed at the supplier's manufacturing location |\n\n**Default:** Level 3 for new parts or significant changes. Always confirm with the customer before submitting.\n\n### Step 2 — Identify the change category\n\nPPAP re-submission is required for:\n- New part or product\n- Engineering change (design revision)\n- Change of supplier (sub-supplier, raw material)\n- Change of manufacturing location, process, or tooling\n- Change that affects fit, form, or function\n- Corrective action following a field failure or customer complaint\n- Production interruption >12 months\n\n### Step 3 — Prepare all 18 PPAP elements\n\n**Production trial run minimum:** Unless otherwise specified in writing by the authorised customer representative, the production trial run must consist of a **minimum of 300 consecutive parts** produced at the production rate, using production tooling, production process, production operators, and production tooling (AIAG PPAP 4th ed §4.0). This run generates the PPAP samples (Element 14), dimensional results (Element 9), and capability data (Element 11). A run shorter than 300 consecutive parts requires explicit written customer authorisation before PSW can be signed.\n\nVerify each element against the level requirement. For Level 3 (default):\n\n**Element 1 — Design Records**\n- Customer drawing (latest revision, stamped\u002Fapproved)\n- Math data if applicable (3D model)\n- All referenced specifications\n\n**Element 2 — Engineering Change Documents**\n- Approved change documentation (ECN, SREA, or equivalent)\n- Required only if an authorized engineering change is in process\n\n**Element 3 — Customer Engineering Approval**\n- Written approval from customer engineering (if design is customer-owned)\n- Engineering sign-off or deviation\u002Fwaiver reference number\n\n**Element 4 — DFMEA**\n- Customer-approved Design FMEA (if design is supplier-responsible)\n- Review all H-AP items for completion before submission\n\n**Element 5 — Process Flow Diagram**\n- Sequence of all operations from incoming material to shipment\n- Includes: incoming inspection, all process steps, sub-supplier operations, final inspection, packaging\n\n**Element 6 — PFMEA**\n- Process FMEA aligned to the Process Flow\n- All H-AP items must have completed actions before PPAP\n- Reviewed and signed off by responsible engineer\n\n**Element 7 — Control Plan**\n- Covers all phases: Prototype, Pre-launch, and Production\n- Linked to PFMEA failure modes and controls\n- Includes: characteristics, measurement method, sample size\u002Ffrequency, reaction plan\n\n**Element 8 — Measurement System Analysis (MSA)**\n- Gauge R&R study for each measurement system used on special and significant characteristics\n- Acceptance criteria: %GRR \u003C 10% preferred, \u003C30% conditional\n- Number of distinct categories (ndc) ≥ 5\n\n**Element 9 — Dimensional Results**\n- Balloon drawing with all dimensions\u002Ftolerances numbered\n- Measurement results for each ballooned characteristic\n- Minimum 5 parts per cavity\u002Fspindle; identify each part\n- All results must be within specification (100% conforming for PPAP)\n\n**Element 10 — Material Performance Test Results**\n- Functional and durability test results per customer\u002Fengineering specification\n- Test reports from customer-approved laboratories\n- All tests passed with certificate of conformance\n\n**Element 11 — Initial Process Studies (Statistical)**\n- Capability studies for all special characteristics (Sc, CC, SC)\n- Minimum Cpk ≥ 1.67 preferred; ≥ 1.33 minimum acceptable\n- If Cpk \u003C 1.33: customer-approved control plan with 100% inspection required\n\n**Element 12 — Qualified Laboratory Documentation**\n- Test reports must be from accredited laboratories (ISO\u002FIEC 17025 preferred)\n- In-house labs: scope of accreditation must cover the tests performed\n\n**Element 13 — Appearance Approval Report (AAR)**\n- Required only for appearance-critical parts\n- Customer sign-off on colour, grain, gloss, and appearance attributes\n\n**Element 14 — Sample Production Parts**\n- Minimum 1 sample part per cavity\u002Fspindle\u002Fdie\n- From the submission run (not prototype or off-tool samples unless Level 1 or 2)\n- Labelled with part number, revision, and date\n\n**Element 15 — Master Sample**\n- One signed-off sample retained at the supplier as a reference standard\n- Signed by supplier and customer (if required)\n\n**Element 16 — Checking Aids**\n- Gauges, fixtures, and check tools used for dimensional verification\n- Calibration records for all checking aids\n- MSA results for all variable gauges on special characteristics\n\n**Element 17 — Customer-Specific Requirements**\n- OEM-specific PPAP requirements (see OEM section below)\n- CSR compliance checklist if required\n\n**Element 18 — Part Submission Warrant (PSW)**\n- One PSW per part number per submission\n- Must be signed by the authorised quality manager\n- Submission reason, specification level, and change description completed\n\n### Step 4 — OEM-specific requirements\n\n**Ford:**\n- Ford-specific PSW form (not generic AIAG form)\n- SREA (Supplier Request for Engineering Approval) for design changes\n- ISIR (Initial Sample Inspection Report) may be required\n- Ford CSR compliance statement on PSW\n\n**BMW:**\n- Form 1410 (Erstmusterprüfbericht \u002F Initial Sample Inspection Report)\n- VDA 6.3 process audit may be required before PPAP\n- G8D report if PPAP follows a concern\n\n**Volkswagen \u002F Audi:**\n- PPF (Produktionsprozess und Produktfreigabe) — VW's PPAP equivalent\n- QMSS portal submission required\n- Audit of production process mandatory for new parts\n\n**Stellantis:**\n- STELLANTIS PPAP requirements per CSR (Customer Specific Requirements)\n- Supplier Quality Assurance (SQA) portal submission\n- PFMEA must follow AIAG-VDA 2019 format\n\n### Step 5 — PSW Completion and Submission\n\nComplete the PSW accurately:\n- Submission reason must match the change category\n- Specification level (Level 1–5) confirmed with customer\n- All 18 elements checked as complete (or N\u002FA with justification)\n- Signed by Quality Manager (not just coordinator)\n- Submit through the customer's designated portal or APQP contact\n\n## Validation criteria\n\nBefore submitting PPAP:\n- All dimensional results 100% within specification\n- Cpk ≥ 1.67 for all special characteristics (or documented deviation with customer approval)\n- %GRR \u003C 30% for all measurement systems on special characteristics\n- All H-AP items in PFMEA have completed actions\n- Control Plan covers all special and significant characteristics\n- Test reports from accredited labs with pass status\n- PSW signed by Quality Manager\n\n## Common mistakes\n\n- Submitting with any out-of-specification dimensional result (automatic rejection)\n- Using prototype or pre-production samples for PPAP (must be from production tooling)\n- Production trial run shorter than 300 consecutive parts without written customer authorisation — automatic rejection at many OEMs\n- Cpk calculated on insufficient data (minimum 100 pieces for capability study)\n- MSA not performed for all gauges used on special characteristics\n- PFMEA not updated after process changes made during PPAP run\n- PSW signed by someone without authority (Quality Manager signature required)\n- Submitting Level 3 without retaining a master sample\n- Generic AIAG PSW form submitted to Ford (requires Ford-specific form)\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 300-part production trial run minimum (AIAG PPAP 4th ed §4.0); added to Common Mistakes |\n","# Production Part Approval Process (PPAP)\n\n## When to use\n\nUse this skill when:\n- A supplier must submit parts for customer approval before Start of Production (SOP)\n- A design change, process change, or engineering change requires re-submission\n- An OEM or Tier 1 customer requests a PPAP at a specific level\n- Reviewing or auditing an incoming PPAP package from a supplier\n- Determining what PPAP level is required for a given change\n\n## Prerequisites\n\n- Part number, revision level, and customer drawing\n- Bill of Materials (BOM) if applicable\n- Production process flow and manufacturing location confirmed\n- Customer's PPAP level requirement (Level 1–5) or change category known\n\n## Workflow\n\n### Step 1 — Determine the PPAP Level\n\n| Level | What must be submitted |\n|-------|----------------------|\n| 1 | Part Submission Warrant (PSW) only — no supporting documents unless requested |\n| 2 | PSW + designated samples + limited supporting data |\n| 3 | PSW + product samples + complete supporting data (default for new parts) |\n| 4 | PSW + other requirements as defined by the customer |\n| 5 | PSW + parts and complete supporting data — reviewed at the supplier's manufacturing location |\n\n**Default:** Level 3 for new parts or significant changes. Always confirm with the customer before submitting.\n\n### Step 2 — Identify the change category\n\nPPAP re-submission is required for:\n- New part or product\n- Engineering change (design revision)\n- Change of supplier (sub-supplier, raw material)\n- Change of manufacturing location, process, or tooling\n- Change that affects fit, form, or function\n- Corrective action following a field failure or customer complaint\n- Production interruption >12 months\n\n### Step 3 — Prepare all 18 PPAP elements\n\n**Production trial run minimum:** Unless otherwise specified in writing by the authorised customer representative, the production trial run must consist of a **minimum of 300 consecutive parts** produced at the production rate, using production tooling, production process, production operators, and production tooling (AIAG PPAP 4th ed §4.0). This run generates the PPAP samples (Element 14), dimensional results (Element 9), and capability data (Element 11). A run shorter than 300 consecutive parts requires explicit written customer authorisation before PSW can be signed.\n\nVerify each element against the level requirement. For Level 3 (default):\n\n**Element 1 — Design Records**\n- Customer drawing (latest revision, stamped\u002Fapproved)\n- Math data if applicable (3D model)\n- All referenced specifications\n\n**Element 2 — Engineering Change Documents**\n- Approved change documentation (ECN, SREA, or equivalent)\n- Required only if an authorized engineering change is in process\n\n**Element 3 — Customer Engineering Approval**\n- Written approval from customer engineering (if design is customer-owned)\n- Engineering sign-off or deviation\u002Fwaiver reference number\n\n**Element 4 — DFMEA**\n- Customer-approved Design FMEA (if design is supplier-responsible)\n- Review all H-AP items for completion before submission\n\n**Element 5 — Process Flow Diagram**\n- Sequence of all operations from incoming material to shipment\n- Includes: incoming inspection, all process steps, sub-supplier operations, final inspection, packaging\n\n**Element 6 — PFMEA**\n- Process FMEA aligned to the Process Flow\n- All H-AP items must have completed actions before PPAP\n- Reviewed and signed off by responsible engineer\n\n**Element 7 — Control Plan**\n- Covers all phases: Prototype, Pre-launch, and Production\n- Linked to PFMEA failure modes and controls\n- Includes: characteristics, measurement method, sample size\u002Ffrequency, reaction plan\n\n**Element 8 — Measurement System Analysis (MSA)**\n- Gauge R&R study for each measurement system used on special and significant characteristics\n- Acceptance criteria: %GRR \u003C 10% preferred, \u003C30% conditional\n- Number of distinct categories (ndc) ≥ 5\n\n**Element 9 — Dimensional Results**\n- Balloon drawing with all dimensions\u002Ftolerances numbered\n- Measurement results for each ballooned characteristic\n- Minimum 5 parts per cavity\u002Fspindle; identify each part\n- All results must be within specification (100% conforming for PPAP)\n\n**Element 10 — Material Performance Test Results**\n- Functional and durability test results per customer\u002Fengineering specification\n- Test reports from customer-approved laboratories\n- All tests passed with certificate of conformance\n\n**Element 11 — Initial Process Studies (Statistical)**\n- Capability studies for all special characteristics (Sc, CC, SC)\n- Minimum Cpk ≥ 1.67 preferred; ≥ 1.33 minimum acceptable\n- If Cpk \u003C 1.33: customer-approved control plan with 100% inspection required\n\n**Element 12 — Qualified Laboratory Documentation**\n- Test reports must be from accredited laboratories (ISO\u002FIEC 17025 preferred)\n- In-house labs: scope of accreditation must cover the tests performed\n\n**Element 13 — Appearance Approval Report (AAR)**\n- Required only for appearance-critical parts\n- Customer sign-off on colour, grain, gloss, and appearance attributes\n\n**Element 14 — Sample Production Parts**\n- Minimum 1 sample part per cavity\u002Fspindle\u002Fdie\n- From the submission run (not prototype or off-tool samples unless Level 1 or 2)\n- Labelled with part number, revision, and date\n\n**Element 15 — Master Sample**\n- One signed-off sample retained at the supplier as a reference standard\n- Signed by supplier and customer (if required)\n\n**Element 16 — Checking Aids**\n- Gauges, fixtures, and check tools used for dimensional verification\n- Calibration records for all checking aids\n- MSA results for all variable gauges on special characteristics\n\n**Element 17 — Customer-Specific Requirements**\n- OEM-specific PPAP requirements (see OEM section below)\n- CSR compliance checklist if required\n\n**Element 18 — Part Submission Warrant (PSW)**\n- One PSW per part number per submission\n- Must be signed by the authorised quality manager\n- Submission reason, specification level, and change description completed\n\n### Step 4 — OEM-specific requirements\n\n**Ford:**\n- Ford-specific PSW form (not generic AIAG form)\n- SREA (Supplier Request for Engineering Approval) for design changes\n- ISIR (Initial Sample Inspection Report) may be required\n- Ford CSR compliance statement on PSW\n\n**BMW:**\n- Form 1410 (Erstmusterprüfbericht \u002F Initial Sample Inspection Report)\n- VDA 6.3 process audit may be required before PPAP\n- G8D report if PPAP follows a concern\n\n**Volkswagen \u002F Audi:**\n- PPF (Produktionsprozess und Produktfreigabe) — VW's PPAP equivalent\n- QMSS portal submission required\n- Audit of production process mandatory for new parts\n\n**Stellantis:**\n- STELLANTIS PPAP requirements per CSR (Customer Specific Requirements)\n- Supplier Quality Assurance (SQA) portal submission\n- PFMEA must follow AIAG-VDA 2019 format\n\n### Step 5 — PSW Completion and Submission\n\nComplete the PSW accurately:\n- Submission reason must match the change category\n- Specification level (Level 1–5) confirmed with customer\n- All 18 elements checked as complete (or N\u002FA with justification)\n- Signed by Quality Manager (not just coordinator)\n- Submit through the customer's designated portal or APQP contact\n\n## Validation criteria\n\nBefore submitting PPAP:\n- All dimensional results 100% within specification\n- Cpk ≥ 1.67 for all special characteristics (or documented deviation with customer approval)\n- %GRR \u003C 30% for all measurement systems on special characteristics\n- All H-AP items in PFMEA have completed actions\n- Control Plan covers all special and significant characteristics\n- Test reports from accredited labs with pass status\n- PSW signed by Quality Manager\n\n## Common mistakes\n\n- Submitting with any out-of-specification dimensional result (automatic rejection)\n- Using prototype or pre-production samples for PPAP (must be from production tooling)\n- Production trial run shorter than 300 consecutive parts without written customer authorisation — automatic rejection at many OEMs\n- Cpk calculated on insufficient data (minimum 100 pieces for capability study)\n- MSA not performed for all gauges used on special characteristics\n- PFMEA not updated after process changes made during PPAP run\n- PSW signed by someone without authority (Quality Manager signature required)\n- Submitting Level 3 without retaining a master sample\n- Generic AIAG PSW form submitted to Ford (requires Ford-specific form)\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 300-part production trial run minimum (AIAG PPAP 4th ed §4.0); added to Common Mistakes |\n",{"name":5,"license":15,"metadata":47,"description":7},{"author":48,"domain":49,"status":50,"created":51,"version":52,"iso-9001":53,"subdomain":41,"iatf-16949":54,"industries":55,"updated_by":56,"reviewed_by":48,"last_updated":51,"aiag-reference":57,"standard_edition":58},"RBraga01","quality-engineering","approved","2026-06-06","1.1","8.4","8.3.4, 8.4.1","automotive,electronics,aerospace,medical,general","migmcc","AIAG PPAP 4th Edition","AIAG PPAP 4th Edition (2006)","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fplanning\u002Fppap",483,"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-13 02:16:32",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ppap",{"tool":75,"command":76},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ppap",{"tool":78,"command":79},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ppap","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fplanning\u002Fppap\u002FSKILL.md",true,[83],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002F18-elements-checklist.md","REFERENCE","参考文档",27385,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002FQuality-Engineering-Skills\u002Fskills\u002Fplanning\u002Fppap\u002Freferences\u002F18-elements-checklist.md",[90,99,106,113,139,163],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":98},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":94,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":98},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":98},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\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":94,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":42},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[120,121,122,123,124,125,126,127,128,129,130,22,131,132,133,134,135,136,137,138],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":42},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[146,147,148,134,26,149,150,151,152,153,154,155,156,157,125,158,159,160,161,162],"deja reflect","reflect","review","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":180,"publishedAt":42},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[169,174,177],{"categoryNo":170,"categoryName":171,"taxonomyType":172,"taxonomyTypeDesc":173},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":175,"categoryName":176,"taxonomyType":172,"taxonomyTypeDesc":173},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":178,"categoryName":179,"taxonomyType":172,"taxonomyTypeDesc":173},"01JBSEEDCAT000000000000010","后端与接口",[165,181,182,183,184,185,186,159,187,126,188,189,190,191,22,192,193,194,195,196],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]