[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79NH2ENMAXKNS6HSF5BK0C8":3,"skill-same:01M79NH2ENMAXKNS6HSF5BK0C8":68},{"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":32,"updatedAt":33,"install":34,"resources":47},"01M79NH2ENMAXKNS6HSF5BK0C8","expo-cicd-workflows",null,"Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI\u002FCD or workflows in an Expo or EAS context, mentions .eas\u002Fworkflows\u002F, or wants help with EAS build pipelines or deployment automation.","MeghVyas3132\u002FClaude-Code-Skills","MeghVyas3132","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F213562095?v=4","01M79MBRQ3EM1GSWXK3QVWPYK6","Megh Vyas","01M79MBRQRZNC3QS0FS1KC6Z09",0,"MIT","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fexpo\u002Fexpo-cicd-workflows\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: expo-cicd-workflows\ndescription: Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI\u002FCD or workflows in an Expo or EAS context, mentions .eas\u002Fworkflows\u002F, or wants help with EAS build pipelines or deployment automation.\nversion: 1.0.0\nlicense: MIT License\n---\n\n# EAS Workflows Skill\n\nHelp developers write and edit EAS CI\u002FCD workflow YAML files.\n\n## Reference Documentation\n\nFetch these resources before generating or validating workflow files. First resolve this skill's directory, then use the fetch script in its `scripts\u002F` directory. It is implemented using Node.js and caches responses using ETags for efficiency:\n\n```bash\n# Fetch resources\nnode \u003Cskill-dir>\u002Fscripts\u002Ffetch.js \u003Curl>\n```\n\n1. **JSON Schema** — https:\u002F\u002Fapi.expo.dev\u002Fv2\u002Fworkflows\u002Fschema\n   - It is NECESSARY to fetch this schema\n   - Source of truth for validation\n   - All job types and their required\u002Foptional parameters\n   - Trigger types and configurations\n   - Runner types, VM images, and all enums\n\n2. **Syntax Documentation** — https:\u002F\u002Fraw.githubusercontent.com\u002Fexpo\u002Fexpo\u002Frefs\u002Fheads\u002Fmain\u002Fdocs\u002Fpages\u002Feas\u002Fworkflows\u002Fsyntax.mdx\n   - Overview of workflow YAML syntax\n   - Examples and English explanations\n   - Expression syntax and contexts\n\n3. **Pre-packaged Jobs** — https:\u002F\u002Fraw.githubusercontent.com\u002Fexpo\u002Fexpo\u002Frefs\u002Fheads\u002Fmain\u002Fdocs\u002Fpages\u002Feas\u002Fworkflows\u002Fpre-packaged-jobs.mdx\n   - Documentation for supported pre-packaged job types\n   - Job-specific parameters and outputs\n\nDo not rely on memorized values; these resources evolve as new features are added.\n\n## Workflow File Location\n\nWorkflows live in `.eas\u002Fworkflows\u002F*.yml` (or `.yaml`).\n\n## Top-Level Structure\n\nA workflow file has these top-level keys:\n\n- `name` — Display name for the workflow\n- `on` — Triggers that start the workflow (at least one required)\n- `jobs` — Job definitions (required)\n- `defaults` — Shared defaults for all jobs\n- `concurrency` — Control parallel workflow runs\n\nConsult the schema for the full specification of each section.\n\n## Expressions\n\nUse `${{ }}` syntax for dynamic values. The schema defines available contexts:\n\n- `github.*` — GitHub repository and event information\n- `inputs.*` — Values from `workflow_dispatch` inputs\n- `needs.*` — Outputs and status from dependent jobs\n- `jobs.*` — Job outputs (alternative syntax)\n- `steps.*` — Step outputs within custom jobs\n- `workflow.*` — Workflow metadata\n\n## Generating Workflows\n\nWhen generating or editing workflows:\n\n1. Fetch the schema to get current job types, parameters, and allowed values\n2. Validate that required fields are present for each job type\n3. Verify job references in `needs` and `after` exist in the workflow\n4. Check that expressions reference valid contexts and outputs\n5. Ensure `if` conditions respect the schema's length constraints\n\n## Validation\n\nAfter generating or editing a workflow file, validate it against the schema:\n\n```sh\n# Install dependencies if missing\n[ -d \"\u003Cskill-dir>\u002Fscripts\u002Fnode_modules\" ] || npm install --prefix \u003Cskill-dir>\u002Fscripts\n\nnode \u003Cskill-dir>\u002Fscripts\u002Fvalidate.js \u003Cworkflow.yml> [workflow2.yml ...]\n```\n\nThe validator fetches the latest schema and checks the YAML structure. Fix any reported errors before considering the workflow complete.\n\n## Answering Questions\n\nWhen users ask about available options (job types, triggers, runner types, etc.), fetch the schema and derive the answer from it rather than relying on potentially outdated information.\n","# EAS Workflows Skill\n\nHelp developers write and edit EAS CI\u002FCD workflow YAML files.\n\n## Reference Documentation\n\nFetch these resources before generating or validating workflow files. First resolve this skill's directory, then use the fetch script in its `scripts\u002F` directory. It is implemented using Node.js and caches responses using ETags for efficiency:\n\n```bash\n# Fetch resources\nnode \u003Cskill-dir>\u002Fscripts\u002Ffetch.js \u003Curl>\n```\n\n1. **JSON Schema** — https:\u002F\u002Fapi.expo.dev\u002Fv2\u002Fworkflows\u002Fschema\n   - It is NECESSARY to fetch this schema\n   - Source of truth for validation\n   - All job types and their required\u002Foptional parameters\n   - Trigger types and configurations\n   - Runner types, VM images, and all enums\n\n2. **Syntax Documentation** — https:\u002F\u002Fraw.githubusercontent.com\u002Fexpo\u002Fexpo\u002Frefs\u002Fheads\u002Fmain\u002Fdocs\u002Fpages\u002Feas\u002Fworkflows\u002Fsyntax.mdx\n   - Overview of workflow YAML syntax\n   - Examples and English explanations\n   - Expression syntax and contexts\n\n3. **Pre-packaged Jobs** — https:\u002F\u002Fraw.githubusercontent.com\u002Fexpo\u002Fexpo\u002Frefs\u002Fheads\u002Fmain\u002Fdocs\u002Fpages\u002Feas\u002Fworkflows\u002Fpre-packaged-jobs.mdx\n   - Documentation for supported pre-packaged job types\n   - Job-specific parameters and outputs\n\nDo not rely on memorized values; these resources evolve as new features are added.\n\n## Workflow File Location\n\nWorkflows live in `.eas\u002Fworkflows\u002F*.yml` (or `.yaml`).\n\n## Top-Level Structure\n\nA workflow file has these top-level keys:\n\n- `name` — Display name for the workflow\n- `on` — Triggers that start the workflow (at least one required)\n- `jobs` — Job definitions (required)\n- `defaults` — Shared defaults for all jobs\n- `concurrency` — Control parallel workflow runs\n\nConsult the schema for the full specification of each section.\n\n## Expressions\n\nUse `${{ }}` syntax for dynamic values. The schema defines available contexts:\n\n- `github.*` — GitHub repository and event information\n- `inputs.*` — Values from `workflow_dispatch` inputs\n- `needs.*` — Outputs and status from dependent jobs\n- `jobs.*` — Job outputs (alternative syntax)\n- `steps.*` — Step outputs within custom jobs\n- `workflow.*` — Workflow metadata\n\n## Generating Workflows\n\nWhen generating or editing workflows:\n\n1. Fetch the schema to get current job types, parameters, and allowed values\n2. Validate that required fields are present for each job type\n3. Verify job references in `needs` and `after` exist in the workflow\n4. Check that expressions reference valid contexts and outputs\n5. Ensure `if` conditions respect the schema's length constraints\n\n## Validation\n\nAfter generating or editing a workflow file, validate it against the schema:\n\n```sh\n# Install dependencies if missing\n[ -d \"\u003Cskill-dir>\u002Fscripts\u002Fnode_modules\" ] || npm install --prefix \u003Cskill-dir>\u002Fscripts\n\nnode \u003Cskill-dir>\u002Fscripts\u002Fvalidate.js \u003Cworkflow.yml> [workflow2.yml ...]\n```\n\nThe validator fetches the latest schema and checks the YAML structure. Fix any reported errors before considering the workflow complete.\n\n## Answering Questions\n\nWhen users ask about available options (job types, triggers, runner types, etc.), fetch the schema and derive the answer from it rather than relying on potentially outdated information.\n",{"name":5,"license":24,"version":25,"description":7},"MIT License","1.0.0","main","12a76cdd6f897f0872b282adeec07c7a07cf6bcc","_other-tools\u002Fcodex\u002Fexpo\u002Fexpo-cicd-workflows","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills","https:\u002F\u002Fgithub.com\u002FMeghVyas3132","https:\u002F\u002Fmegh.tech","Entrepreneur \u002F Platform Engineer \u002F DevOps \u002F Backend developer \u002F System Architect \u002F Salesforce admin-dev \u002F AI Engineer \u002F Junior SRE","2026-07-25 05:29:37",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add MeghVyas3132\u002FClaude-Code-Skills --skill expo-cicd-workflows",{"tool":40,"command":41},"bunx","bunx skills add MeghVyas3132\u002FClaude-Code-Skills --skill expo-cicd-workflows",{"tool":43,"command":44},"pnpm","pnpm dlx skills add MeghVyas3132\u002FClaude-Code-Skills --skill expo-cicd-workflows","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fexpo\u002Fexpo-cicd-workflows\u002FSKILL.md",true,[48,54,60,64],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",344,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fexpo\u002Fexpo-cicd-workflows\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"scripts\u002Ffetch.js","SCRIPT","脚本",2979,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fexpo\u002Fexpo-cicd-workflows\u002Fscripts\u002Ffetch.js",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"scripts\u002Fpackage.json",204,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fexpo\u002Fexpo-cicd-workflows\u002Fscripts\u002Fpackage.json",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"scripts\u002Fvalidate.js",2159,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fexpo\u002Fexpo-cicd-workflows\u002Fscripts\u002Fvalidate.js",[69,78,85,92,99,106],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79QXVKBA07BMENY2S4C9B0D","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fskill-creator\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},"01M79QXPTA7529Z7QX9TYC9X8M","skill-audit","Pre-install security scanner for AI agent skills. 7.5% of 14,706 skills are malicious. Audit before you trust.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fskill-audit\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":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79QWZ2BB5GTX3PCHEEDG3A2","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Freact-best-practices\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M79QWAADBR52R570H6N25F47","impeccable","Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fimpeccable\u002FSKILL.md",[],[],{"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":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M79QTGQJGPXPJDB09WBZHRND","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fcomposition-patterns\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":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M79QT5TCZBBKP5ECWE0QD9PT","bumblebee","Run Bumblebee supply-chain inventory and exposure scans on macOS\u002FLinux to detect compromised packages, extensions, and MCP host configs.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fbumblebee\u002FSKILL.md",[],[]]