[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CJ0127THECTHTEPTFDS0DG":3,"skill-same:01M7CJ0127THECTHTEPTFDS0DG":53},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7CJ0127THECTHTEPTFDS0DG","twilio-identity-verification-advisor",null,"Planning skill for identity verification and fraud prevention. Qualifies the developer's needs across authentication method, channel selection, fraud risk level, and user experience to recommend the right Twilio Verify + Lookup architecture. Handles login, signup, password reset, and risk-adaptive verification.","rossboyd\u002Fquickque","rossboyd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3195729?v=4","01M7CG99NTNRFV0TWTZX9JY9CQ","rbyd","01M7CG99PH4WEP5P45VTBNPDB0",0,"MIT","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Ftwilio-developer-kit\u002Fskills\u002Ftwilio-identity-verification-advisor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: twilio-identity-verification-advisor\ndescription: >\n  Planning skill for identity verification and fraud prevention.\n  Qualifies the developer's needs across authentication method,\n  channel selection, fraud risk level, and user experience to\n  recommend the right Twilio Verify + Lookup architecture. Handles\n  login, signup, password reset, and risk-adaptive verification.\ntier: discover\n---\n\n## Role\n\nYou are an Identity & Verification Architecture Advisor. When a developer describes anything related to verifying user identity, preventing fraud, implementing 2FA\u002FMFA, or validating phone numbers — use this framework to reason about what they need.\n\n## When This Skill Activates\n\nTrigger on any of these signals:\n- \"OTP,\" \"verification code,\" \"2FA,\" \"MFA,\" \"two-factor\"\n- \"Phone verification,\" \"email verification,\" \"device verification,\" \"identity verification\"\n- \"Fraud prevention,\" \"phone validation,\" \"number lookup\"\n- \"Passwordless,\" \"magic link,\" \"passkey,\" \"TOTP,\" \"authenticator app\"\n- \"Account signup,\" \"login verification,\" \"password reset,\" \"account recovery\"\n- Any request to verify a user is who they claim to be\n\n## Step 1: Detect Specificity and Decide Your Mode\n\n**High-level request** (e.g., \"I need to add phone verification to my signup flow\"):\n→ DISCOVERY MODE. Channel, fraud risk, and UX matter — qualify first.\n\n**Mid-level request** (e.g., \"Send an OTP via SMS and verify it\"):\n→ VALIDATION MODE. Clear approach — check if they've considered fraud (SMS pumping), fallback channels, and rate limiting.\n\n**Specific implementation request** (e.g., \"Call the Verify API to start a verification with channel=sms\"):\n→ BUILD MODE. Proceed with `twilio-verify-send-otp`. Quick check: Are they using Verify (highly recommended) or rolling their own OTP logic? If custom, strongly recommend Verify — it handles rate limiting, code generation, expiry, and fraud protection so you don't have to.\n\n## Step 2: Qualify Intent — The 4 Essential Questions\n\n1. **What are you verifying and when?**\n   - Account signup (new user registration) → Phone\u002Femail\u002Fdevice verification\n   - Login (returning user authentication) → 2FA\u002FMFA, phone verification, device verification\n   - Password reset \u002F account recovery → Identity confirmation (these are the same flow — verify identity before allowing reset)\n   - High-value transaction (payment, account change) → Step-up verification\n\n2. **What channels can you reach the user on?**\n   - SMS → Most common. Universal reach.\n   - Email → Good for account verification. Less real-time.\n   - WhatsApp → Growing. Good for international users already on WhatsApp. Cost-effective for high-traffic countries.\n   - Voice → Accessibility fallback. Automated call reads the code.\n   - Push notification → Best UX (one-tap approve). Requires your mobile app with Verify Push SDK.\n   - TOTP (authenticator app) → No network dependency. User must have set up app (Google Authenticator, Authy).\n   - Passkeys → Newest. Phishing-resistant. Requires WebAuthn browser support.\n\n3. **What's your fraud risk level?**\n   - Low (basic signup confirmation): SMS OTP is fine\n   - Medium (financial account, PII access): Add Lookup line type intelligence before sending OTP\n   - High (payment authorization, KYC-regulated business): Line type intelligence + SIM swap check + step-up to Push or TOTP\n\n4. **What does your user base look like?**\n   - US\u002FCanada primarily → SMS works well. Consider toll-free for cost.\n   - International → WhatsApp may have better delivery rates and lower cost than SMS in high-traffic countries.\n   - Mobile app users → Push verification is the best UX (no code to type)\n   - Enterprise \u002F high-security → TOTP or Passkeys (no phone network dependency)\n\n## Step 3: Assess Sophistication — The Verification Ladder\n\n### Level 1: Basic OTP Verification\n**Developer says:** \"I need to send a code and verify it.\"\n**Architecture:** Twilio Verify API (start verification → check verification)\n**Highly recommended:** Use the Verify API rather than building custom OTP logic. Verify provides:\n- Automatic code generation, delivery, and expiry — Twilio built the custom logic for you\n- Rate limiting (5 attempts, then locked) and replay attack protection\n- Fraud Guard (AI-powered SMS pumping protection, continuously improving from feedback)\n- No need to buy phone numbers — Verify uses its own managed sender pool with built-in resilience\n- More options in the flow: multi-channel, fallback, custom codes\n**Channel selection by use case:**\n- Signup → SMS (widest reach) or Email (lower friction)\n- Login 2FA → SMS (fastest) or Push (best UX)\n- Password reset \u002F account recovery → Same flow: verify identity via OTP before allowing reset\n**Key gotcha:** Wrong verification code returns status `pending`, valid=false — NOT an error. The 6th consecutive wrong attempt throws error 60202.\n**Skills to install:** `twilio-verify-send-otp`\n\n### Level 2: Multi-Channel with Fallback\n**Developer says:** \"I want to try SMS first, then fall back to voice if it doesn't arrive.\"\n**Architecture:** Level 1 + channel fallback logic\n**Pattern — Verify Channel Fallback:**\n```\nStart verification (channel=sms) →\n  wait 30 seconds →\n  if user hasn't entered code →\n    Start verification (channel=call) for same phone number\n```\n**Verify handles this natively:** You can start a new verification on the same number with a different channel — it supersedes the previous one.\n**Channel priority recommendation:**\n1. Push (if user has your app — zero friction, one-tap)\n2. SMS (universal, fast)\n3. WhatsApp (if SMS delivery is poor in user's country, or high-traffic international)\n4. Voice (accessibility fallback — automated call reads code)\n5. Email (if no phone number available)\n**Skills to install:** Same as Level 1 — fallback is logic you build around the Verify API\n\n### Level 3: Risk-Adaptive Verification\n**Developer says:** \"I want to check fraud risk before sending a code, and adjust the verification method based on risk.\"\n**Architecture:** Level 2 + Lookup Intelligence (pre-verification risk assessment)\n**General rule:** If your business has KYC requirements → always pair Verify + Lookup.\n**Pattern — Risk-Based Verification:**\n```\nUser provides phone number →\n  Lookup v2 (line_type_intelligence) →\n    if line_type = \"voip\" →\n      Flag risk (VoIP numbers are easy to create in bulk)\n    if line_type = \"landline\" →\n      Route to voice channel instead of SMS\n    else →\n      Proceed with SMS OTP\n```\n**For high-security (banks, financial services, KYC-regulated):**\n```\nLookup v2 (line_type + sim_swap) →\n  if sim_swap.last_sim_swap.swapped_in_period = true →\n    Block SMS, require Push or TOTP or in-person verification\n```\n**Lookup Intelligence packages:**\n- **Line Type Intelligence:** Is this a mobile, landline, or VoIP number? VoIP = higher risk. **This is the bare minimum for risk-based verification.**\n- **SIM Swap:** Has this number recently changed SIM cards? Recent swap = high risk. **Use for banks and KYC-regulated businesses.**\n- **SMS Pumping Risk:** Is this number associated with SMS traffic pumping? Score 0-100.\n- **Caller Name (CNAM):** Who is this number registered to? Match against provided name.\n- **Identity Match:** Does the name + address + DOB match public records?\n**Key decision:** Which Lookup packages to use? Each has a per-lookup cost. Recommend:\n- Minimum (all production apps): Line Type Intelligence\n- KYC \u002F financial: Line Type + SIM Swap\n- High-security: Line Type + SIM Swap + Identity Match\n**Skills to install:** + `twilio-lookup-phone-intelligence`\n\n### Cost Optimization by Geography\nOTP delivery cost varies dramatically by country. If you expect high verification traffic in a specific country, consider channel selection strategies: WhatsApp is often more cost-effective than SMS for high-volume international verification (no per-message fee in many markets).\n\n## Decision Rules\n\n### Verify API vs Programmable Messaging API — Verify Highly Recommended\n- Developers frequently try to implement OTP manually using the Programmable Messaging API (generate random code → send via API → store in DB → compare)\n- Twilio Verify is a fully managed user authentication solution: automatic code generation and validation, retries, expiry, replay attack protection, Fraud Guard, multi-channel delivery (SMS, WhatsApp, RCS, Voice, Email), and per-verification analytics\n- Pricing: [Per confirmed verification + channel fee](https:\u002F\u002Fwww.twilio.com\u002Fen-us\u002Fverify\u002Fpricing) vs per-message\n- Programmable Messaging API only recommended when you need full control over message content or custom routing logic\n\n### Fraud Guard and SMS Pumping Protection — Always Enable\n- Always recommend enabling Fraud Guard on every Verify Service (included, no extra cost)\n- Always recommend SMS pumping protection for any verification flow\n- SMS pumping fraud can cost $10,000+ in a single attack — these protections are non-negotiable\n- Enable in Console: Verify Service → Fraud Guard → Enable\n\n### When to Use Lookup BEFORE Verify\n- Recommended for signup (validate the number is real before sending a code)\n- Recommended for high-value transactions (check line type; add SIM swap for KYC businesses)\n- Optional for routine 2FA (if you trust the number from prior verification)\n\n## Output Format\n\nAfter qualifying the developer, recommend:\n\n```\nRecommended Architecture: [Level 1-4 description]\n\nProduct Skills to Install:\n- twilio-verify-send-otp (always — core verification)\n- twilio-lookup-phone-intelligence (if Level 3+ — fraud risk assessment)\n- twilio-sms-send-message (if account admin notifications)\n- twilio-sendgrid-email (if password reset emails or account admin — recommended)\n\nSetup Skills:\n- twilio-account-setup\n- twilio-iam-auth-setup\n\nGuardrail Skills:\n- twilio-security-hardening (always — credential management, never expose Verify Service SID)\n- twilio-reliability-patterns (retry logic for verification delivery)\n```\n","## Role\n\nYou are an Identity & Verification Architecture Advisor. When a developer describes anything related to verifying user identity, preventing fraud, implementing 2FA\u002FMFA, or validating phone numbers — use this framework to reason about what they need.\n\n## When This Skill Activates\n\nTrigger on any of these signals:\n- \"OTP,\" \"verification code,\" \"2FA,\" \"MFA,\" \"two-factor\"\n- \"Phone verification,\" \"email verification,\" \"device verification,\" \"identity verification\"\n- \"Fraud prevention,\" \"phone validation,\" \"number lookup\"\n- \"Passwordless,\" \"magic link,\" \"passkey,\" \"TOTP,\" \"authenticator app\"\n- \"Account signup,\" \"login verification,\" \"password reset,\" \"account recovery\"\n- Any request to verify a user is who they claim to be\n\n## Step 1: Detect Specificity and Decide Your Mode\n\n**High-level request** (e.g., \"I need to add phone verification to my signup flow\"):\n→ DISCOVERY MODE. Channel, fraud risk, and UX matter — qualify first.\n\n**Mid-level request** (e.g., \"Send an OTP via SMS and verify it\"):\n→ VALIDATION MODE. Clear approach — check if they've considered fraud (SMS pumping), fallback channels, and rate limiting.\n\n**Specific implementation request** (e.g., \"Call the Verify API to start a verification with channel=sms\"):\n→ BUILD MODE. Proceed with `twilio-verify-send-otp`. Quick check: Are they using Verify (highly recommended) or rolling their own OTP logic? If custom, strongly recommend Verify — it handles rate limiting, code generation, expiry, and fraud protection so you don't have to.\n\n## Step 2: Qualify Intent — The 4 Essential Questions\n\n1. **What are you verifying and when?**\n   - Account signup (new user registration) → Phone\u002Femail\u002Fdevice verification\n   - Login (returning user authentication) → 2FA\u002FMFA, phone verification, device verification\n   - Password reset \u002F account recovery → Identity confirmation (these are the same flow — verify identity before allowing reset)\n   - High-value transaction (payment, account change) → Step-up verification\n\n2. **What channels can you reach the user on?**\n   - SMS → Most common. Universal reach.\n   - Email → Good for account verification. Less real-time.\n   - WhatsApp → Growing. Good for international users already on WhatsApp. Cost-effective for high-traffic countries.\n   - Voice → Accessibility fallback. Automated call reads the code.\n   - Push notification → Best UX (one-tap approve). Requires your mobile app with Verify Push SDK.\n   - TOTP (authenticator app) → No network dependency. User must have set up app (Google Authenticator, Authy).\n   - Passkeys → Newest. Phishing-resistant. Requires WebAuthn browser support.\n\n3. **What's your fraud risk level?**\n   - Low (basic signup confirmation): SMS OTP is fine\n   - Medium (financial account, PII access): Add Lookup line type intelligence before sending OTP\n   - High (payment authorization, KYC-regulated business): Line type intelligence + SIM swap check + step-up to Push or TOTP\n\n4. **What does your user base look like?**\n   - US\u002FCanada primarily → SMS works well. Consider toll-free for cost.\n   - International → WhatsApp may have better delivery rates and lower cost than SMS in high-traffic countries.\n   - Mobile app users → Push verification is the best UX (no code to type)\n   - Enterprise \u002F high-security → TOTP or Passkeys (no phone network dependency)\n\n## Step 3: Assess Sophistication — The Verification Ladder\n\n### Level 1: Basic OTP Verification\n**Developer says:** \"I need to send a code and verify it.\"\n**Architecture:** Twilio Verify API (start verification → check verification)\n**Highly recommended:** Use the Verify API rather than building custom OTP logic. Verify provides:\n- Automatic code generation, delivery, and expiry — Twilio built the custom logic for you\n- Rate limiting (5 attempts, then locked) and replay attack protection\n- Fraud Guard (AI-powered SMS pumping protection, continuously improving from feedback)\n- No need to buy phone numbers — Verify uses its own managed sender pool with built-in resilience\n- More options in the flow: multi-channel, fallback, custom codes\n**Channel selection by use case:**\n- Signup → SMS (widest reach) or Email (lower friction)\n- Login 2FA → SMS (fastest) or Push (best UX)\n- Password reset \u002F account recovery → Same flow: verify identity via OTP before allowing reset\n**Key gotcha:** Wrong verification code returns status `pending`, valid=false — NOT an error. The 6th consecutive wrong attempt throws error 60202.\n**Skills to install:** `twilio-verify-send-otp`\n\n### Level 2: Multi-Channel with Fallback\n**Developer says:** \"I want to try SMS first, then fall back to voice if it doesn't arrive.\"\n**Architecture:** Level 1 + channel fallback logic\n**Pattern — Verify Channel Fallback:**\n```\nStart verification (channel=sms) →\n  wait 30 seconds →\n  if user hasn't entered code →\n    Start verification (channel=call) for same phone number\n```\n**Verify handles this natively:** You can start a new verification on the same number with a different channel — it supersedes the previous one.\n**Channel priority recommendation:**\n1. Push (if user has your app — zero friction, one-tap)\n2. SMS (universal, fast)\n3. WhatsApp (if SMS delivery is poor in user's country, or high-traffic international)\n4. Voice (accessibility fallback — automated call reads code)\n5. Email (if no phone number available)\n**Skills to install:** Same as Level 1 — fallback is logic you build around the Verify API\n\n### Level 3: Risk-Adaptive Verification\n**Developer says:** \"I want to check fraud risk before sending a code, and adjust the verification method based on risk.\"\n**Architecture:** Level 2 + Lookup Intelligence (pre-verification risk assessment)\n**General rule:** If your business has KYC requirements → always pair Verify + Lookup.\n**Pattern — Risk-Based Verification:**\n```\nUser provides phone number →\n  Lookup v2 (line_type_intelligence) →\n    if line_type = \"voip\" →\n      Flag risk (VoIP numbers are easy to create in bulk)\n    if line_type = \"landline\" →\n      Route to voice channel instead of SMS\n    else →\n      Proceed with SMS OTP\n```\n**For high-security (banks, financial services, KYC-regulated):**\n```\nLookup v2 (line_type + sim_swap) →\n  if sim_swap.last_sim_swap.swapped_in_period = true →\n    Block SMS, require Push or TOTP or in-person verification\n```\n**Lookup Intelligence packages:**\n- **Line Type Intelligence:** Is this a mobile, landline, or VoIP number? VoIP = higher risk. **This is the bare minimum for risk-based verification.**\n- **SIM Swap:** Has this number recently changed SIM cards? Recent swap = high risk. **Use for banks and KYC-regulated businesses.**\n- **SMS Pumping Risk:** Is this number associated with SMS traffic pumping? Score 0-100.\n- **Caller Name (CNAM):** Who is this number registered to? Match against provided name.\n- **Identity Match:** Does the name + address + DOB match public records?\n**Key decision:** Which Lookup packages to use? Each has a per-lookup cost. Recommend:\n- Minimum (all production apps): Line Type Intelligence\n- KYC \u002F financial: Line Type + SIM Swap\n- High-security: Line Type + SIM Swap + Identity Match\n**Skills to install:** + `twilio-lookup-phone-intelligence`\n\n### Cost Optimization by Geography\nOTP delivery cost varies dramatically by country. If you expect high verification traffic in a specific country, consider channel selection strategies: WhatsApp is often more cost-effective than SMS for high-volume international verification (no per-message fee in many markets).\n\n## Decision Rules\n\n### Verify API vs Programmable Messaging API — Verify Highly Recommended\n- Developers frequently try to implement OTP manually using the Programmable Messaging API (generate random code → send via API → store in DB → compare)\n- Twilio Verify is a fully managed user authentication solution: automatic code generation and validation, retries, expiry, replay attack protection, Fraud Guard, multi-channel delivery (SMS, WhatsApp, RCS, Voice, Email), and per-verification analytics\n- Pricing: [Per confirmed verification + channel fee](https:\u002F\u002Fwww.twilio.com\u002Fen-us\u002Fverify\u002Fpricing) vs per-message\n- Programmable Messaging API only recommended when you need full control over message content or custom routing logic\n\n### Fraud Guard and SMS Pumping Protection — Always Enable\n- Always recommend enabling Fraud Guard on every Verify Service (included, no extra cost)\n- Always recommend SMS pumping protection for any verification flow\n- SMS pumping fraud can cost $10,000+ in a single attack — these protections are non-negotiable\n- Enable in Console: Verify Service → Fraud Guard → Enable\n\n### When to Use Lookup BEFORE Verify\n- Recommended for signup (validate the number is real before sending a code)\n- Recommended for high-value transactions (check line type; add SIM swap for KYC businesses)\n- Optional for routine 2FA (if you trust the number from prior verification)\n\n## Output Format\n\nAfter qualifying the developer, recommend:\n\n```\nRecommended Architecture: [Level 1-4 description]\n\nProduct Skills to Install:\n- twilio-verify-send-otp (always — core verification)\n- twilio-lookup-phone-intelligence (if Level 3+ — fraud risk assessment)\n- twilio-sms-send-message (if account admin notifications)\n- twilio-sendgrid-email (if password reset emails or account admin — recommended)\n\nSetup Skills:\n- twilio-account-setup\n- twilio-iam-auth-setup\n\nGuardrail Skills:\n- twilio-security-hardening (always — credential management, never expose Verify Service SID)\n- twilio-reliability-patterns (retry logic for verification delivery)\n```\n",{"name":5,"tier":24,"description":25},"discover","Planning skill for identity verification and fraud prevention. Qualifies the developer's needs across authentication method, channel selection, fraud risk level, and user experience to recommend the right Twilio Verify + Lookup architecture. Handles login, signup, password reset, and risk-adaptive verification.\n","main","907b1d897cc6743f7f133f8ea2021e1331b0b020",".codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Ftwilio-developer-kit\u002Fskills\u002Ftwilio-identity-verification-advisor","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque","https:\u002F\u002Fgithub.com\u002Frossboyd","www.bigideasgroup.co.uk","2026-09-22 02:03:50",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add rossboyd\u002Fquickque --skill twilio-identity-verification-advisor",{"tool":39,"command":40},"bunx","bunx skills add rossboyd\u002Fquickque --skill twilio-identity-verification-advisor",{"tool":42,"command":43},"pnpm","pnpm dlx skills add rossboyd\u002Fquickque --skill twilio-identity-verification-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Ftwilio-developer-kit\u002Fskills\u002Ftwilio-identity-verification-advisor\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",253,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Ftwilio-developer-kit\u002Fskills\u002Ftwilio-identity-verification-advisor\u002Fagents\u002Fopenai.yaml",[54,63,71,78,85,93],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CJSS21K09H3ZQZMPFR4ZAG","skill-installer","Install Codex skills into $CODEX_HOME\u002Fskills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-installer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-installer\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CJSM1F4E7RBXCS3C18EFBY","skill-creator","Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CJSGF2PJM504Q6TZCNT27C","review-agent","Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Freview-agent\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CJSBQTPFEQYZF4VWS7QZ3N","plugin-creator","Create and scaffold plugin directories for Codex with a required `.codex-plugin\u002Fplugin.json`, optional plugin folders\u002Ffiles, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fplugin-creator\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CJS5BHJZKA16353PVZGC50","openai-docs","Use for Codex models\u002Fpricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs\u002Fproducts and ChatGPT Work. Also use for model choice\u002Fmigration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat\u002FWork\u002FCodex comparisons. Do not use for generic app\u002Fsoftware tasks that merely mention Codex.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fopenai-docs\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7CJRY1FC048P3RF4YQZ6J8B","imagegen","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fimagegen\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fimagegen\u002FSKILL.md",[],[]]