[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7X4GWS92DTB5H480S35DM":3,"skill-same:01M6H7X4GWS92DTB5H480S35DM":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":23,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6H7X4GWS92DTB5H480S35DM","codex-plan",null,"Codex skill expansion plan and gap analysis.","0xharryriddle\u002Fcodex-field-kit","0xharryriddle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100945007?v=4","01M6H686JV0QKZYP2RWG6B2B8T","harryriddle","01M6H686PVZ8JGKWEG7B3GM5PD",3,"MIT","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-prompts\u002Fcodex-plan\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35],"codex","plan","codex plan","planning","analysis","prompt","prompts","codex skill","gap","gap analysis","kit","expansion","2026-11-10 10:12:30",false,"---\nname: codex-plan\ndescription: \"Codex skill expansion plan and gap analysis.\"\nmetadata:\n  hermes:\n    tags: [codex-prompt, planning]\n    source: codex-field-kit\u002Fprompts\n---\n\n# Codex Plan\n\n# Codex Skill Expansion Plan\n\nDate: 2026-01-19\nGoal: Fill meaningful gaps in the current skill library with high-impact skills for DevOps\u002Fautomation, planning\u002Farchitecture, and code generation\u002Frefactoring. Focus on complementary capabilities.\n\n## Gap Analysis Summary\n\nKey gaps identified relative to current skills:\n- Git\u002FGitHub workflow automation (PRs, issues, releases, branch management)\n- CI\u002FCD pipeline creation and troubleshooting\n- Testing automation & quality gates (unit\u002Fintegration\u002Fe2e\u002Flint)\n- Database migrations and schema management\n- Environment\u002Fsecrets management across local\u002FCI\u002Fdeploy\n- Code review, static analysis, and security scanning\n- Documentation generation and maintenance\n- Debugging\u002Fprofiling tools beyond UI\u002Fbrowser automation\n- API development\u002Ftesting workflows\n- Deployment\u002Finfrastructure scaffolding and verification\n- AI\u002FML workflow helpers (RAG, embeddings, prompt evaluation)\n\n## Proposed New Skills (9)\n\n### 1) gh-workflow-automation\n- Problem it solves: Automates GitHub PR\u002Fissue\u002Frelease workflows missing from the current library.\n- Core functionality:\n  - Create\u002Fupdate PRs, add labels\u002Freviewers, manage milestones.\n  - Generate release notes and draft releases from merged PRs.\n  - Sync issues with local branch names and link PRs to issues.\n  - Triage stale PRs\u002Fissues with rules (age, labels, checks).\n- Integration type: MCP-integrated or hybrid (gh CLI + GitHub API).\n- Implementation complexity: Medium — gh CLI and API orchestration + auth handling.\n- Dependencies: gh CLI, GitHub API token or gh auth.\n- Example use cases:\n  - “Create a PR from current branch, add reviewers and labels.”\n  - “Generate draft release notes for v1.4.0.”\n  - “Close stale issues older than 90 days without activity.”\n\n### 2) ci-cd-pipeline-builder\n- Problem it solves: Builds or fixes CI\u002FCD pipelines across common providers.\n- Core functionality:\n  - Scaffold CI configs (GitHub Actions, GitLab CI, CircleCI).\n  - Add job matrices, caching, secrets, and artifact uploads.\n  - Diagnose failing CI runs from logs and propose fixes.\n  - Add deployment stages (preview\u002Fprod) with approvals.\n- Integration type: Hybrid (local files + provider docs or APIs).\n- Implementation complexity: High — multi-provider templates and troubleshooting logic.\n- Dependencies: CI config templates, provider docs, optional provider APIs.\n- Example use cases:\n  - “Add a lint+test matrix for Node 18\u002F20.”\n  - “Fix failing GitHub Actions job from recent run.”\n  - “Add deploy-to-staging step after tests pass.”\n\n### 3) test-qa-orchestrator\n- Problem it solves: Standardizes test setup, execution, and reporting across stacks.\n- Core functionality:\n  - Detect test frameworks and generate test scripts.\n  - Add coverage thresholds and reports (lcov\u002Fjunit).\n  - Wire tests into CI and pre-commit hooks.\n  - Create smoke tests for critical paths.\n- Integration type: Standalone or hybrid.\n- Implementation complexity: Medium — framework detection + scripted updates.\n- Dependencies: Project test runner(s) (pytest\u002Fjest\u002Fgo test\u002Fetc.).\n- Example use cases:\n  - “Add Jest coverage thresholds and CI reporting.”\n  - “Create a smoke test for the login flow.”\n  - “Wire pytest into GitHub Actions with artifacts.”\n\n### 4) db-migrations-schema\n- Problem it solves: Adds migrations and schema management workflows.\n- Core functionality:\n  - Detect ORM\u002FDB tool (Prisma, Alembic, Flyway, Liquibase).\n  - Generate migration and apply\u002Frollback plans.\n  - Validate schema drift and environment differences.\n  - Document schema changes with changelogs.\n- Integration type: Hybrid.\n- Implementation complexity: Medium — DB tool detection + command orchestration.\n- Dependencies: DB CLI tools, database access or local schema files.\n- Example use cases:\n  - “Create a migration to add a users.last_login column.”\n  - “Compare prod vs staging schema and report drift.”\n  - “Generate schema changelog for release notes.”\n\n### 5) secrets-env-manager\n- Problem it solves: Centralizes environment variable and secret management.\n- Core functionality:\n  - Inventory env vars from code\u002Fconfig and generate .env.example.\n  - Add validation and safe defaults for missing env vars.\n  - Integrate with secret managers (1Password, Vault, AWS SSM).\n  - Redact secrets from logs and test outputs.\n- Integration type: Hybrid or MCP-integrated.\n- Implementation complexity: High — secure handling and provider integrations.\n- Dependencies: Secret manager APIs\u002FCLIs (optional), dotenv parsers.\n- Example use cases:\n  - “Create .env.example and validate required vars.”\n  - “Sync staging secrets from Vault.”\n  - “Audit repo for leaked secrets and rotate.”\n\n### 6) code-review-static-analysis\n- Problem it solves: Automates code review checks and static analysis.\n- Core functionality:\n  - Run linters\u002Fformatters and collect reports.\n  - Run static analyzers (Semgrep, ESLint, Pylint, golangci-lint).\n  - Summarize key findings with severity and fixes.\n  - Auto-generate review checklist tailored to repo.\n- Integration type: Standalone or hybrid.\n- Implementation complexity: Medium — tool integration and report parsing.\n- Dependencies: Linter\u002Fanalyzer CLIs and configs.\n- Example use cases:\n  - “Run semgrep and report high-severity findings.”\n  - “Generate a review checklist for this repo.”\n  - “Auto-fix lint errors and open a PR.”\n\n### 7) api-dev-test-kit\n- Problem it solves: Speeds API development, validation, and testing.\n- Core functionality:\n  - Generate OpenAPI specs from routes or code annotations.\n  - Create API tests (Postman\u002Fnewman, REST Assured, pytest).\n  - Mock APIs and generate fixtures.\n  - Validate backwards compatibility between versions.\n- Integration type: Hybrid.\n- Implementation complexity: Medium — spec tooling integration.\n- Dependencies: OpenAPI tools, test frameworks, mock servers.\n- Example use cases:\n  - “Create OpenAPI spec for existing Express routes.”\n  - “Generate contract tests from OpenAPI.”\n  - “Mock a payment API for local dev.”\n\n### 8) deploy-infra-scout\n- Problem it solves: Scaffolds and verifies deployments and infra configs.\n- Core functionality:\n  - Detect deployment targets (Vercel, Netlify, Docker, K8s).\n  - Generate deploy config and environment checks.\n  - Add health checks and rollback recommendations.\n  - Validate infra drift and required permissions.\n- Integration type: Hybrid.\n- Implementation complexity: High — provider-specific templates and checks.\n- Dependencies: Docker\u002FK8s CLIs, cloud provider CLIs, IaC tools.\n- Example use cases:\n  - “Create Dockerfile + healthcheck for Node app.”\n  - “Generate Kubernetes manifest for app + DB.”\n  - “Audit Vercel project config and env vars.”\n\n### 9) rag-ml-workbench\n- Problem it solves: Adds AI\u002FML workflow helpers (RAG, embeddings, prompt eval).\n- Core functionality:\n  - Scaffold RAG pipeline (ingest, chunk, embed, retrieve).\n  - Set up vector DB integrations (Pinecone, Weaviate, pgvector).\n  - Evaluate prompts with test sets and regression metrics.\n  - Generate safety checks and prompt templates.\n- Integration type: Hybrid or MCP-integrated.\n- Implementation complexity: High — model\u002Fprovider-specific tooling.\n- Dependencies: Vector DB SDKs, embedding APIs, eval tools.\n- Example use cases:\n  - “Set up a pgvector-based RAG pipeline.”\n  - “Create prompt regression tests for chat agent.”\n  - “Benchmark retrieval strategies on sample corpus.”\n\n## Prioritization\n\nRecommended initial build order based on impact and effort:\n1. gh-workflow-automation\n2. ci-cd-pipeline-builder\n3. test-qa-orchestrator\n4. code-review-static-analysis\n5. secrets-env-manager\n6. db-migrations-schema\n7. api-dev-test-kit\n8. deploy-infra-scout\n9. rag-ml-workbench\n\n## Implementation Notes\n\n- Favor composable, modular skills that can chain (e.g., test-qa-orchestrator + ci-cd-pipeline-builder).\n- Provide consistent CLI entry points and predictable output schemas.\n- Add a short “detect” phase to each skill to reduce manual configuration.\n- Include “dry-run” modes for destructive operations.\n- Use deterministic command execution and file edits for reproducibility.\n\n","# Codex Plan\n\n# Codex Skill Expansion Plan\n\nDate: 2026-01-19\nGoal: Fill meaningful gaps in the current skill library with high-impact skills for DevOps\u002Fautomation, planning\u002Farchitecture, and code generation\u002Frefactoring. Focus on complementary capabilities.\n\n## Gap Analysis Summary\n\nKey gaps identified relative to current skills:\n- Git\u002FGitHub workflow automation (PRs, issues, releases, branch management)\n- CI\u002FCD pipeline creation and troubleshooting\n- Testing automation & quality gates (unit\u002Fintegration\u002Fe2e\u002Flint)\n- Database migrations and schema management\n- Environment\u002Fsecrets management across local\u002FCI\u002Fdeploy\n- Code review, static analysis, and security scanning\n- Documentation generation and maintenance\n- Debugging\u002Fprofiling tools beyond UI\u002Fbrowser automation\n- API development\u002Ftesting workflows\n- Deployment\u002Finfrastructure scaffolding and verification\n- AI\u002FML workflow helpers (RAG, embeddings, prompt evaluation)\n\n## Proposed New Skills (9)\n\n### 1) gh-workflow-automation\n- Problem it solves: Automates GitHub PR\u002Fissue\u002Frelease workflows missing from the current library.\n- Core functionality:\n  - Create\u002Fupdate PRs, add labels\u002Freviewers, manage milestones.\n  - Generate release notes and draft releases from merged PRs.\n  - Sync issues with local branch names and link PRs to issues.\n  - Triage stale PRs\u002Fissues with rules (age, labels, checks).\n- Integration type: MCP-integrated or hybrid (gh CLI + GitHub API).\n- Implementation complexity: Medium — gh CLI and API orchestration + auth handling.\n- Dependencies: gh CLI, GitHub API token or gh auth.\n- Example use cases:\n  - “Create a PR from current branch, add reviewers and labels.”\n  - “Generate draft release notes for v1.4.0.”\n  - “Close stale issues older than 90 days without activity.”\n\n### 2) ci-cd-pipeline-builder\n- Problem it solves: Builds or fixes CI\u002FCD pipelines across common providers.\n- Core functionality:\n  - Scaffold CI configs (GitHub Actions, GitLab CI, CircleCI).\n  - Add job matrices, caching, secrets, and artifact uploads.\n  - Diagnose failing CI runs from logs and propose fixes.\n  - Add deployment stages (preview\u002Fprod) with approvals.\n- Integration type: Hybrid (local files + provider docs or APIs).\n- Implementation complexity: High — multi-provider templates and troubleshooting logic.\n- Dependencies: CI config templates, provider docs, optional provider APIs.\n- Example use cases:\n  - “Add a lint+test matrix for Node 18\u002F20.”\n  - “Fix failing GitHub Actions job from recent run.”\n  - “Add deploy-to-staging step after tests pass.”\n\n### 3) test-qa-orchestrator\n- Problem it solves: Standardizes test setup, execution, and reporting across stacks.\n- Core functionality:\n  - Detect test frameworks and generate test scripts.\n  - Add coverage thresholds and reports (lcov\u002Fjunit).\n  - Wire tests into CI and pre-commit hooks.\n  - Create smoke tests for critical paths.\n- Integration type: Standalone or hybrid.\n- Implementation complexity: Medium — framework detection + scripted updates.\n- Dependencies: Project test runner(s) (pytest\u002Fjest\u002Fgo test\u002Fetc.).\n- Example use cases:\n  - “Add Jest coverage thresholds and CI reporting.”\n  - “Create a smoke test for the login flow.”\n  - “Wire pytest into GitHub Actions with artifacts.”\n\n### 4) db-migrations-schema\n- Problem it solves: Adds migrations and schema management workflows.\n- Core functionality:\n  - Detect ORM\u002FDB tool (Prisma, Alembic, Flyway, Liquibase).\n  - Generate migration and apply\u002Frollback plans.\n  - Validate schema drift and environment differences.\n  - Document schema changes with changelogs.\n- Integration type: Hybrid.\n- Implementation complexity: Medium — DB tool detection + command orchestration.\n- Dependencies: DB CLI tools, database access or local schema files.\n- Example use cases:\n  - “Create a migration to add a users.last_login column.”\n  - “Compare prod vs staging schema and report drift.”\n  - “Generate schema changelog for release notes.”\n\n### 5) secrets-env-manager\n- Problem it solves: Centralizes environment variable and secret management.\n- Core functionality:\n  - Inventory env vars from code\u002Fconfig and generate .env.example.\n  - Add validation and safe defaults for missing env vars.\n  - Integrate with secret managers (1Password, Vault, AWS SSM).\n  - Redact secrets from logs and test outputs.\n- Integration type: Hybrid or MCP-integrated.\n- Implementation complexity: High — secure handling and provider integrations.\n- Dependencies: Secret manager APIs\u002FCLIs (optional), dotenv parsers.\n- Example use cases:\n  - “Create .env.example and validate required vars.”\n  - “Sync staging secrets from Vault.”\n  - “Audit repo for leaked secrets and rotate.”\n\n### 6) code-review-static-analysis\n- Problem it solves: Automates code review checks and static analysis.\n- Core functionality:\n  - Run linters\u002Fformatters and collect reports.\n  - Run static analyzers (Semgrep, ESLint, Pylint, golangci-lint).\n  - Summarize key findings with severity and fixes.\n  - Auto-generate review checklist tailored to repo.\n- Integration type: Standalone or hybrid.\n- Implementation complexity: Medium — tool integration and report parsing.\n- Dependencies: Linter\u002Fanalyzer CLIs and configs.\n- Example use cases:\n  - “Run semgrep and report high-severity findings.”\n  - “Generate a review checklist for this repo.”\n  - “Auto-fix lint errors and open a PR.”\n\n### 7) api-dev-test-kit\n- Problem it solves: Speeds API development, validation, and testing.\n- Core functionality:\n  - Generate OpenAPI specs from routes or code annotations.\n  - Create API tests (Postman\u002Fnewman, REST Assured, pytest).\n  - Mock APIs and generate fixtures.\n  - Validate backwards compatibility between versions.\n- Integration type: Hybrid.\n- Implementation complexity: Medium — spec tooling integration.\n- Dependencies: OpenAPI tools, test frameworks, mock servers.\n- Example use cases:\n  - “Create OpenAPI spec for existing Express routes.”\n  - “Generate contract tests from OpenAPI.”\n  - “Mock a payment API for local dev.”\n\n### 8) deploy-infra-scout\n- Problem it solves: Scaffolds and verifies deployments and infra configs.\n- Core functionality:\n  - Detect deployment targets (Vercel, Netlify, Docker, K8s).\n  - Generate deploy config and environment checks.\n  - Add health checks and rollback recommendations.\n  - Validate infra drift and required permissions.\n- Integration type: Hybrid.\n- Implementation complexity: High — provider-specific templates and checks.\n- Dependencies: Docker\u002FK8s CLIs, cloud provider CLIs, IaC tools.\n- Example use cases:\n  - “Create Dockerfile + healthcheck for Node app.”\n  - “Generate Kubernetes manifest for app + DB.”\n  - “Audit Vercel project config and env vars.”\n\n### 9) rag-ml-workbench\n- Problem it solves: Adds AI\u002FML workflow helpers (RAG, embeddings, prompt eval).\n- Core functionality:\n  - Scaffold RAG pipeline (ingest, chunk, embed, retrieve).\n  - Set up vector DB integrations (Pinecone, Weaviate, pgvector).\n  - Evaluate prompts with test sets and regression metrics.\n  - Generate safety checks and prompt templates.\n- Integration type: Hybrid or MCP-integrated.\n- Implementation complexity: High — model\u002Fprovider-specific tooling.\n- Dependencies: Vector DB SDKs, embedding APIs, eval tools.\n- Example use cases:\n  - “Set up a pgvector-based RAG pipeline.”\n  - “Create prompt regression tests for chat agent.”\n  - “Benchmark retrieval strategies on sample corpus.”\n\n## Prioritization\n\nRecommended initial build order based on impact and effort:\n1. gh-workflow-automation\n2. ci-cd-pipeline-builder\n3. test-qa-orchestrator\n4. code-review-static-analysis\n5. secrets-env-manager\n6. db-migrations-schema\n7. api-dev-test-kit\n8. deploy-infra-scout\n9. rag-ml-workbench\n\n## Implementation Notes\n\n- Favor composable, modular skills that can chain (e.g., test-qa-orchestrator + ci-cd-pipeline-builder).\n- Provide consistent CLI entry points and predictable output schemas.\n- Add a short “detect” phase to each skill to reduce manual configuration.\n- Include “dry-run” modes for destructive operations.\n- Use deterministic command execution and file edits for reproducibility.\n\n",{"name":5,"metadata":41,"description":7},{"hermes":42},{"tags":43,"source":45},[44,27],"codex-prompt","codex-field-kit\u002Fprompts","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-prompts\u002Fcodex-plan",0,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit","https:\u002F\u002Fgithub.com\u002F0xharryriddle","https:\u002F\u002Fharryriddle.vercel.app","2026-04-11 11:49:51",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill codex-plan",{"tool":60,"command":61},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill codex-plan",{"tool":63,"command":64},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill codex-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-prompts\u002Fcodex-plan\u002FSKILL.md",true,[],[69,99,118,128,153,179],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":78,"publishedAt":36},"01M6H7ZKE6MR33HC84QZ1TA6MV","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\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98],"react best practices","react","vercel react best practices","best practices","vercel","tasks","data fetching","triggers","pages","next","performance optimization","refactoring","Next.js","Optimization","code","guidelines","react components","components","performance","writing",{"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":36},"01M6H7ZGC2WK8SEKYHWDNTMDA9","swarm-planner","[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fswarm-planner\u002FSKILL.md",[],[106,107,108,109,110,111,112,113,114,115,116,117],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","for","multi","implementation",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":36},"01M6H7ZD93853RZCYQWH1D38TM","super-swarm-spark","Only to be triggered by explicit super-swarm-spark commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fsuper-swarm-spark\u002FSKILL.md",[],[125,106,126,111,127],"super swarm spark","spark","commands",{"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":36},"01M6H7Z987QBY49JCCPT953EAZ","role-creator","Create and install Codex custom agent roles in ~\u002F.codex\u002Fconfig.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Frole-creator\u002FSKILL.md",[],[135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,24,152],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"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":160,"publishedAt":36},"01M6H7Z5TRPMDQ7YSZQXPN1G60","read-github","Read and search GitHub repository documentation via gitmcp.io MCP service.\n\n**WHEN TO USE:**\n- User provides a GitHub URL\n- User mentions a specific repo in owner\u002Frepo format\n- User asks \"what does this repo do?\", \"read the docs for X repo\", or similar\n- User wants to search code or docs within a repo","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fread-github\u002FSKILL.md",[159],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[161,162,163,93,164,165,166,167,115,168,169,170,171,172,173,174,175,176,177,178],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","use","user","repo","format","repository",{"skillNo":180,"name":108,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":36},"01M6H7Z215CTKYJ4Y1X6EQWN6M","Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: \"make a plan\", \"create a plan\", \"plan this out\", \"plan the implementation\", \"help me plan\", \"design a plan\", \"draft a plan\", \"write a plan\", \"outline the steps\", \"break this down into tasks\", \"what's the plan for\", or any similar planning request. Also triggers on explicit \"\u002Fplanner\" or \"\u002Fplan\" commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fplanner\u002FSKILL.md",[],[108,185,115,186,187,188,86,113,127,189,190,174,191,192,25,193,27,150,84,194],"outline","atomic","with","sprints","draft","me","write","phased implementation","help","design"]