[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVYB0ARY6AVH4TSDTYCF0E":3,"skill-same:01M6JVYB0ARY6AVH4TSDTYCF0E":79},{"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":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6JVYB0ARY6AVH4TSDTYCF0E","chunking-numeric-and-otp",null,"Use this skill when designing inputs or displays for numeric strings — phone numbers, OTP \u002F verification codes, credit card numbers, account IDs, license keys, currency, dates, social security numbers. Trigger when picking a format for displaying numbers, designing OTP entry UIs, or formatting identifiers in tables and receipts. Sub-aspect of `chunking`; read that first.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking-numeric-and-otp\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],"chunking numeric and otp","otp","chunking","formatting","when","dates","for","keys","strings","tables","codes","card","trigger","currency","security","social","phone","use","read","format","receipts","first","ids","license","verification","2026-11-10 10:12:30",false,"---\nname: chunking-numeric-and-otp\ndescription: 'Use this skill when designing inputs or displays for numeric strings — phone numbers, OTP \u002F verification codes, credit card numbers, account IDs, license keys, currency, dates, social security numbers. Trigger when picking a format for displaying numbers, designing OTP entry UIs, or formatting identifiers in tables and receipts. Sub-aspect of `chunking`; read that first.'\n---\n\n# Chunking applied to numeric strings\n\nNumbers are the canonical chunking case. A 10-digit phone number, a 16-digit credit card, a 6-digit OTP — without chunking, these are working-memory overloads. With chunking, they're manageable.\n\n## Standard chunkings\n\nConventions that have evolved across industries:\n\n| Type | Standard chunking | Example |\n|---|---|---|\n| US phone | 3-3-4 | 555-867-5309 |\n| International phone | varies; usually 2-3-3-2 or similar | +44 20 7946 0958 |\n| Credit card | 4-4-4-4 (most) or 4-6-5 (Amex) | 4242 4242 4242 4242 |\n| Social Security (US) | 3-2-4 | 123-45-6789 |\n| OTP \u002F verification | 3-3 (6-digit) or 4-4 (8-digit) | 123-456 |\n| Bank account (US) | varies; often grouped with type | 110000000 → routing display |\n| ISBN | 1-3-3-5-1 (ISBN-13) | 978-3-16-148410-0 |\n| IP address | 4 octets separated by dots | 192.168.1.1 |\n| Date (ISO) | 4-2-2 | 2026-05-02 |\n| Currency | 3-digit groups | $1,234,567.89 |\n\nWhen in doubt, follow the convention. Users have already learned it.\n\n## OTP \u002F verification code entry\n\nThe most common modern chunking case in product UI. A 6-digit code from email or SMS, entered into a verification field.\n\n### Single field vs. chunked fields\n\nSingle field:\n```html\n\u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"6\" pattern=\"\\d{6}\" \u002F>\n```\n\nChunked fields (one per digit):\n```html\n\u003Cdiv class=\"otp-input\" role=\"group\" aria-label=\"Verification code\">\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" autocomplete=\"one-time-code\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cspan class=\"separator\" aria-hidden>—\u003C\u002Fspan>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n\u003C\u002Fdiv>\n```\n\nThe chunked version:\n\n- Visually matches how the code is presented in email\u002FSMS.\n- Lets the user verify each digit's position mid-entry.\n- Auto-advances focus on each digit (with JS).\n- Supports paste-spread (paste into first input fills all).\n\nThe single-field version is simpler to implement and supports SMS-autofill on iOS via `autocomplete=\"one-time-code\"`. Modern apps often offer both: a single field on mobile (where autofill is critical) and chunked on desktop.\n\n### OTP UX details\n\n- **Auto-advance** focus to the next digit on input.\n- **Auto-back** focus to previous digit on backspace.\n- **Paste support**: pasting a 6-digit string into the first input should distribute across all six.\n- **`autocomplete=\"one-time-code\"`** on at least one input enables iOS Messages autofill.\n- **Numeric keyboard on mobile** via `inputmode=\"numeric\"`.\n- **Optional auto-submit** when the last digit is entered (debate: some users dislike auto-submit because it commits before they can verify).\n\n## Phone number entry\n\nPhone numbers vary widely by country. Patterns:\n\n- **US-only forms**: enforce 3-3-4 with format mask or chunked inputs.\n- **International forms**: use a country selector + a free-text number field; format on display rather than enforcing entry format.\n- **Dual-purpose** (international users + US-heavy): use [libphonenumber](https:\u002F\u002Fgithub.com\u002Fgoogle\u002Flibphonenumber) or similar to validate and format dynamically.\n\n```html\n\u003Clabel>\n  Phone\n  \u003Cdiv class=\"phone-input\">\n    \u003Cselect name=\"country-code\">\n      \u003Coption value=\"+1\">?? +1\u003C\u002Foption>\n      \u003Coption value=\"+44\">?? +44\u003C\u002Foption>\n      \u003C!-- ... -->\n    \u003C\u002Fselect>\n    \u003Cinput type=\"tel\" name=\"phone\" placeholder=\"555-867-5309\" \u002F>\n  \u003C\u002Fdiv>\n\u003C\u002Flabel>\n```\n\n## Credit card display\n\nIn production, never display full card numbers — show the last 4 digits chunked with masking:\n\n```\n**** **** **** 4242\n```\n\nFor entry, use 4-4-4-4 chunking with auto-advance, paste support, and card-type detection:\n\n```html\n\u003Cinput type=\"text\" inputmode=\"numeric\" autocomplete=\"cc-number\"\n       placeholder=\"1234 5678 9012 3456\" \u002F>\n```\n\nBuilt-in browsers and password managers handle most of this if you use the right `autocomplete` value.\n\n## Account IDs and identifiers\n\nFor internal IDs (account IDs, transaction IDs, session IDs):\n\n- **Display chunked** if the user might read or transcribe them.\n- **Display monospaced** so digits and letters align (`font-family: monospace; font-variant-numeric: tabular-nums;`).\n- **Provide one-click copy** so users don't have to manually select.\n\n```html\n\u003Cdiv class=\"id-display\">\n  \u003Cspan class=\"id-value\">ws_8f3c-7a92-1b04\u003C\u002Fspan>\n  \u003Cbutton onclick=\"copyToClipboard('ws_8f3c-7a92-1b04')\" aria-label=\"Copy\">?\u003C\u002Fbutton>\n\u003C\u002Fdiv>\n```\n\nThe chunking aids reading aloud (support calls) and verification.\n\n## Currency\n\nCurrency should always use locale-appropriate digit grouping:\n\n- US English: `$1,234,567.89` (3-digit groups, period decimal).\n- European: `€1.234.567,89` (period grouping, comma decimal).\n- Indian: `₹12,34,567.89` (mixed grouping: 2-2-3).\n\nUse `Intl.NumberFormat` to get this right per locale:\n\n```js\nnew Intl.NumberFormat('en-US', { style: 'currency', currency: 'USD' })\n  .format(1234567.89);\n\u002F\u002F \"$1,234,567.89\"\n```\n\nNumeric columns in tables should use `font-variant-numeric: tabular-nums` so digits align vertically.\n\n## Anti-patterns\n\n- **Continuous strings**: a 16-digit credit card with no chunking. Users can't verify.\n- **Inconsistent chunk sizes within a context**: phone numbers shown as 3-4-3 here and 5-2-3 there. Each format is a re-learn.\n- **Wrong locale grouping**: showing `1,234.56` to a German user (who reads it as 1,234.56 = roughly 1,234 plus 56\u002F100 instead of 1234.56).\n- **Missing `inputmode`**: a numeric field that opens the alphabet keyboard on mobile. Easy fix; commonly missed.\n- **OTP with no auto-advance \u002F paste support**: users tab manually between fields; if they paste, only the first field fills.\n- **Unmasked credit card display**: privacy and security violation. Always mask all but the last 4.\n\n## Heuristics\n\n1. **The \"read it aloud\" test.** Try reading the chunked number aloud. If it requires re-grouping mentally, the chunking is wrong.\n2. **The cross-locale check.** For currency and dates, test in at least 2–3 locales. Format mismatches are common.\n3. **The clipboard \u002F autofill check.** Does pasting the user's clipboard into your input work cleanly? Do password managers fill correctly?\n4. **The mobile keyboard check.** Numeric inputs should produce numeric keyboards on mobile (`inputmode=\"numeric\"`).\n\n## Related sub-skills\n\n- **`chunking`** (parent).\n- **`chunking-form-grouping`** — chunking at the form-section level.\n- **`legibility`** (perception) — tabular numerals for column alignment.\n- **`accessibility-perceivable`** (process) — number formatting affects screen-reader pronunciation.\n","# Chunking applied to numeric strings\n\nNumbers are the canonical chunking case. A 10-digit phone number, a 16-digit credit card, a 6-digit OTP — without chunking, these are working-memory overloads. With chunking, they're manageable.\n\n## Standard chunkings\n\nConventions that have evolved across industries:\n\n| Type | Standard chunking | Example |\n|---|---|---|\n| US phone | 3-3-4 | 555-867-5309 |\n| International phone | varies; usually 2-3-3-2 or similar | +44 20 7946 0958 |\n| Credit card | 4-4-4-4 (most) or 4-6-5 (Amex) | 4242 4242 4242 4242 |\n| Social Security (US) | 3-2-4 | 123-45-6789 |\n| OTP \u002F verification | 3-3 (6-digit) or 4-4 (8-digit) | 123-456 |\n| Bank account (US) | varies; often grouped with type | 110000000 → routing display |\n| ISBN | 1-3-3-5-1 (ISBN-13) | 978-3-16-148410-0 |\n| IP address | 4 octets separated by dots | 192.168.1.1 |\n| Date (ISO) | 4-2-2 | 2026-05-02 |\n| Currency | 3-digit groups | $1,234,567.89 |\n\nWhen in doubt, follow the convention. Users have already learned it.\n\n## OTP \u002F verification code entry\n\nThe most common modern chunking case in product UI. A 6-digit code from email or SMS, entered into a verification field.\n\n### Single field vs. chunked fields\n\nSingle field:\n```html\n\u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"6\" pattern=\"\\d{6}\" \u002F>\n```\n\nChunked fields (one per digit):\n```html\n\u003Cdiv class=\"otp-input\" role=\"group\" aria-label=\"Verification code\">\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" autocomplete=\"one-time-code\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cspan class=\"separator\" aria-hidden>—\u003C\u002Fspan>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n\u003C\u002Fdiv>\n```\n\nThe chunked version:\n\n- Visually matches how the code is presented in email\u002FSMS.\n- Lets the user verify each digit's position mid-entry.\n- Auto-advances focus on each digit (with JS).\n- Supports paste-spread (paste into first input fills all).\n\nThe single-field version is simpler to implement and supports SMS-autofill on iOS via `autocomplete=\"one-time-code\"`. Modern apps often offer both: a single field on mobile (where autofill is critical) and chunked on desktop.\n\n### OTP UX details\n\n- **Auto-advance** focus to the next digit on input.\n- **Auto-back** focus to previous digit on backspace.\n- **Paste support**: pasting a 6-digit string into the first input should distribute across all six.\n- **`autocomplete=\"one-time-code\"`** on at least one input enables iOS Messages autofill.\n- **Numeric keyboard on mobile** via `inputmode=\"numeric\"`.\n- **Optional auto-submit** when the last digit is entered (debate: some users dislike auto-submit because it commits before they can verify).\n\n## Phone number entry\n\nPhone numbers vary widely by country. Patterns:\n\n- **US-only forms**: enforce 3-3-4 with format mask or chunked inputs.\n- **International forms**: use a country selector + a free-text number field; format on display rather than enforcing entry format.\n- **Dual-purpose** (international users + US-heavy): use [libphonenumber](https:\u002F\u002Fgithub.com\u002Fgoogle\u002Flibphonenumber) or similar to validate and format dynamically.\n\n```html\n\u003Clabel>\n  Phone\n  \u003Cdiv class=\"phone-input\">\n    \u003Cselect name=\"country-code\">\n      \u003Coption value=\"+1\">?? +1\u003C\u002Foption>\n      \u003Coption value=\"+44\">?? +44\u003C\u002Foption>\n      \u003C!-- ... -->\n    \u003C\u002Fselect>\n    \u003Cinput type=\"tel\" name=\"phone\" placeholder=\"555-867-5309\" \u002F>\n  \u003C\u002Fdiv>\n\u003C\u002Flabel>\n```\n\n## Credit card display\n\nIn production, never display full card numbers — show the last 4 digits chunked with masking:\n\n```\n**** **** **** 4242\n```\n\nFor entry, use 4-4-4-4 chunking with auto-advance, paste support, and card-type detection:\n\n```html\n\u003Cinput type=\"text\" inputmode=\"numeric\" autocomplete=\"cc-number\"\n       placeholder=\"1234 5678 9012 3456\" \u002F>\n```\n\nBuilt-in browsers and password managers handle most of this if you use the right `autocomplete` value.\n\n## Account IDs and identifiers\n\nFor internal IDs (account IDs, transaction IDs, session IDs):\n\n- **Display chunked** if the user might read or transcribe them.\n- **Display monospaced** so digits and letters align (`font-family: monospace; font-variant-numeric: tabular-nums;`).\n- **Provide one-click copy** so users don't have to manually select.\n\n```html\n\u003Cdiv class=\"id-display\">\n  \u003Cspan class=\"id-value\">ws_8f3c-7a92-1b04\u003C\u002Fspan>\n  \u003Cbutton onclick=\"copyToClipboard('ws_8f3c-7a92-1b04')\" aria-label=\"Copy\">?\u003C\u002Fbutton>\n\u003C\u002Fdiv>\n```\n\nThe chunking aids reading aloud (support calls) and verification.\n\n## Currency\n\nCurrency should always use locale-appropriate digit grouping:\n\n- US English: `$1,234,567.89` (3-digit groups, period decimal).\n- European: `€1.234.567,89` (period grouping, comma decimal).\n- Indian: `₹12,34,567.89` (mixed grouping: 2-2-3).\n\nUse `Intl.NumberFormat` to get this right per locale:\n\n```js\nnew Intl.NumberFormat('en-US', { style: 'currency', currency: 'USD' })\n  .format(1234567.89);\n\u002F\u002F \"$1,234,567.89\"\n```\n\nNumeric columns in tables should use `font-variant-numeric: tabular-nums` so digits align vertically.\n\n## Anti-patterns\n\n- **Continuous strings**: a 16-digit credit card with no chunking. Users can't verify.\n- **Inconsistent chunk sizes within a context**: phone numbers shown as 3-4-3 here and 5-2-3 there. Each format is a re-learn.\n- **Wrong locale grouping**: showing `1,234.56` to a German user (who reads it as 1,234.56 = roughly 1,234 plus 56\u002F100 instead of 1234.56).\n- **Missing `inputmode`**: a numeric field that opens the alphabet keyboard on mobile. Easy fix; commonly missed.\n- **OTP with no auto-advance \u002F paste support**: users tab manually between fields; if they paste, only the first field fills.\n- **Unmasked credit card display**: privacy and security violation. Always mask all but the last 4.\n\n## Heuristics\n\n1. **The \"read it aloud\" test.** Try reading the chunked number aloud. If it requires re-grouping mentally, the chunking is wrong.\n2. **The cross-locale check.** For currency and dates, test in at least 2–3 locales. Format mismatches are common.\n3. **The clipboard \u002F autofill check.** Does pasting the user's clipboard into your input work cleanly? Do password managers fill correctly?\n4. **The mobile keyboard check.** Numeric inputs should produce numeric keyboards on mobile (`inputmode=\"numeric\"`).\n\n## Related sub-skills\n\n- **`chunking`** (parent).\n- **`chunking-form-grouping`** — chunking at the form-section level.\n- **`legibility`** (perception) — tabular numerals for column alignment.\n- **`accessibility-perceivable`** (process) — number formatting affects screen-reader pronunciation.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking-numeric-and-otp",474,"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-11 14:40:14",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill chunking-numeric-and-otp",{"tool":65,"command":66},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill chunking-numeric-and-otp",{"tool":68,"command":69},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill chunking-numeric-and-otp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking-numeric-and-otp\u002FSKILL.md",true,[73],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fnumeric-format-conventions.md","REFERENCE","参考文档",3272,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking-numeric-and-otp\u002Freferences\u002Fnumeric-format-conventions.md",[80,88,95,102,128,153],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"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.","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":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":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":87},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":87},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":44},"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",[],[109,110,111,112,113,114,115,116,117,118,119,23,120,121,122,123,124,125,126,127],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":44},"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",[],[135,136,137,123,138,139,140,141,142,143,144,145,146,147,114,148,149,150,151,152],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":170,"publishedAt":44},"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",[159,164,167],{"categoryNo":160,"categoryName":161,"taxonomyType":162,"taxonomyTypeDesc":163},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":165,"categoryName":166,"taxonomyType":162,"taxonomyTypeDesc":163},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":168,"categoryName":169,"taxonomyType":162,"taxonomyTypeDesc":163},"01JBSEEDCAT000000000000010","后端与接口",[155,171,172,173,174,175,176,149,177,115,178,34,179,180,23,181,182,183,184,185],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","MCP","song","image","mcp server","schedule","api","publish"]