[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CHAC21ZVG2HRVGJ0H0JC4B":3,"skill-same:01M7CHAC21ZVG2HRVGJ0H0JC4B":125},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7CHAC21ZVG2HRVGJ0H0JC4B","notion-spec-to-implementation",null,"Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs\u002Ffeature specs and creating Notion plans + tasks from them.","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\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: notion-spec-to-implementation\ndescription: Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs\u002Ffeature specs and creating Notion plans + tasks from them.\nmetadata:\n  short-description: Turn Notion specs into implementation plans, tasks, and progress tracking\n---\n\n# Spec to Implementation\n\nConvert a Notion spec into linked implementation plans, tasks, and ongoing status updates.\n\n## Quick start\n1) Locate the spec with `Notion:search`, then fetch it with `Notion:fetch`.\n2) Parse requirements and ambiguities using `reference\u002Fspec-parsing.md`.\n3) Create a plan page with `Notion:notion-create-pages` (pick a template: quick vs. full).\n4) Find the task database, confirm schema, then create tasks with `Notion:notion-create-pages`.\n5) Link spec ↔ plan ↔ tasks; keep status current with `Notion:notion-update-page`.\n\n## Tool-call guardrails\n- Notion tool availability can vary by workspace. If a Notion MCP call returns `Tool \u003Cname> not found`, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; use `Notion:search` and `Notion:fetch` where sufficient.\n- Use one literal search query per `Notion:search` call and include `filters: {}` when no narrower filter is needed. Run separate searches for alternate phrasings instead of putting `or` in a single query string.\n- Only send Notion page, database, or data-source URLs\u002FIDs to `Notion:fetch`; external connected-source search results are not fetch targets.\n- Create plans and task pages with explicit `parent` and `pages` fields. For task databases, fetch first and use the returned `collection:\u002F\u002F...` data source ID.\n- To append an implementation section to a spec, fetch the current section text first, then use `Notion:notion-update-page` with `command: \"update_content\"`, `properties: {}`, and exact `old_str` \u002F `new_str` content. For property-only edits, use `command: \"update_properties\"` with `content_updates: []`; the current deployed schema expects both top-level fields even when one is unused.\n\n## Workflow\n\n### 0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:\n1. Enable the bundled Notion app for this plugin or session.\n2. Complete the Notion auth flow if prompted.\n3. Start a new session if the tools still do not appear.\n\nAfter the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.\n\n### 1) Locate and read the spec\n- Search first (`Notion:search`); if multiple hits, ask the user which to use.\n- Fetch the page (`Notion:fetch`) and scan for requirements, acceptance criteria, constraints, and priorities. See `reference\u002Fspec-parsing.md` for extraction patterns.\n- Capture gaps\u002Fassumptions in a clarifications block before proceeding.\n\n### 2) Choose plan depth\n- Simple change → use `reference\u002Fquick-implementation-plan.md`.\n- Multi-phase feature\u002Fmigration → use `reference\u002Fstandard-implementation-plan.md`.\n- Create the plan via `Notion:notion-create-pages`, include: overview, linked spec, requirements summary, phases, dependencies\u002Frisks, and success criteria. Link back to the spec.\n\n### 3) Create tasks\n- Find the task database (`Notion:search` → `Notion:fetch` to confirm the data source and required properties). Patterns in `reference\u002Ftask-creation.md`.\n- Size tasks to 1–2 days. Use `reference\u002Ftask-creation-template.md` for content (context, objective, acceptance criteria, dependencies, resources).\n- Set properties: title\u002Faction verb, status, priority, relations to spec + plan, due date\u002Fstory points\u002Fassignee if provided.\n- Create pages with `Notion:notion-create-pages` using the database’s `data_source_id`.\n\n### 4) Link artifacts\n- Plan links to spec; tasks link to both plan and spec.\n- Optionally update the spec with a short “Implementation” section pointing to the plan and tasks using `Notion:notion-update-page`.\n\n### 5) Track progress\n- Use the cadence in `reference\u002Fprogress-tracking.md`.\n- Post updates with `reference\u002Fprogress-update-template.md`; close phases with `reference\u002Fmilestone-summary-template.md`.\n- Keep checklists and status fields in plan\u002Ftasks in sync; note blockers and decisions.\n\n## References and examples\n- `reference\u002F` — parsing patterns, plan\u002Ftask templates, progress cadence (e.g., `spec-parsing.md`, `standard-implementation-plan.md`, `task-creation.md`, `progress-tracking.md`).\n- `examples\u002F` — end-to-end walkthroughs (e.g., `ui-component.md`, `api-feature.md`, `database-migration.md`).\n","# Spec to Implementation\n\nConvert a Notion spec into linked implementation plans, tasks, and ongoing status updates.\n\n## Quick start\n1) Locate the spec with `Notion:search`, then fetch it with `Notion:fetch`.\n2) Parse requirements and ambiguities using `reference\u002Fspec-parsing.md`.\n3) Create a plan page with `Notion:notion-create-pages` (pick a template: quick vs. full).\n4) Find the task database, confirm schema, then create tasks with `Notion:notion-create-pages`.\n5) Link spec ↔ plan ↔ tasks; keep status current with `Notion:notion-update-page`.\n\n## Tool-call guardrails\n- Notion tool availability can vary by workspace. If a Notion MCP call returns `Tool \u003Cname> not found`, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; use `Notion:search` and `Notion:fetch` where sufficient.\n- Use one literal search query per `Notion:search` call and include `filters: {}` when no narrower filter is needed. Run separate searches for alternate phrasings instead of putting `or` in a single query string.\n- Only send Notion page, database, or data-source URLs\u002FIDs to `Notion:fetch`; external connected-source search results are not fetch targets.\n- Create plans and task pages with explicit `parent` and `pages` fields. For task databases, fetch first and use the returned `collection:\u002F\u002F...` data source ID.\n- To append an implementation section to a spec, fetch the current section text first, then use `Notion:notion-update-page` with `command: \"update_content\"`, `properties: {}`, and exact `old_str` \u002F `new_str` content. For property-only edits, use `command: \"update_properties\"` with `content_updates: []`; the current deployed schema expects both top-level fields even when one is unused.\n\n## Workflow\n\n### 0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:\n1. Enable the bundled Notion app for this plugin or session.\n2. Complete the Notion auth flow if prompted.\n3. Start a new session if the tools still do not appear.\n\nAfter the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.\n\n### 1) Locate and read the spec\n- Search first (`Notion:search`); if multiple hits, ask the user which to use.\n- Fetch the page (`Notion:fetch`) and scan for requirements, acceptance criteria, constraints, and priorities. See `reference\u002Fspec-parsing.md` for extraction patterns.\n- Capture gaps\u002Fassumptions in a clarifications block before proceeding.\n\n### 2) Choose plan depth\n- Simple change → use `reference\u002Fquick-implementation-plan.md`.\n- Multi-phase feature\u002Fmigration → use `reference\u002Fstandard-implementation-plan.md`.\n- Create the plan via `Notion:notion-create-pages`, include: overview, linked spec, requirements summary, phases, dependencies\u002Frisks, and success criteria. Link back to the spec.\n\n### 3) Create tasks\n- Find the task database (`Notion:search` → `Notion:fetch` to confirm the data source and required properties). Patterns in `reference\u002Ftask-creation.md`.\n- Size tasks to 1–2 days. Use `reference\u002Ftask-creation-template.md` for content (context, objective, acceptance criteria, dependencies, resources).\n- Set properties: title\u002Faction verb, status, priority, relations to spec + plan, due date\u002Fstory points\u002Fassignee if provided.\n- Create pages with `Notion:notion-create-pages` using the database’s `data_source_id`.\n\n### 4) Link artifacts\n- Plan links to spec; tasks link to both plan and spec.\n- Optionally update the spec with a short “Implementation” section pointing to the plan and tasks using `Notion:notion-update-page`.\n\n### 5) Track progress\n- Use the cadence in `reference\u002Fprogress-tracking.md`.\n- Post updates with `reference\u002Fprogress-update-template.md`; close phases with `reference\u002Fmilestone-summary-template.md`.\n- Keep checklists and status fields in plan\u002Ftasks in sync; note blockers and decisions.\n\n## References and examples\n- `reference\u002F` — parsing patterns, plan\u002Ftask templates, progress cadence (e.g., `spec-parsing.md`, `standard-implementation-plan.md`, `task-creation.md`, `progress-tracking.md`).\n- `examples\u002F` — end-to-end walkthroughs (e.g., `ui-component.md`, `api-feature.md`, `database-migration.md`).\n",{"name":5,"metadata":25,"description":7},{"short-description":26},"Turn Notion specs into implementation plans, tasks, and progress tracking","main","907b1d897cc6743f7f133f8ea2021e1331b0b020",".codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation","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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add rossboyd\u002Fquickque --skill notion-spec-to-implementation",{"tool":40,"command":41},"bunx","bunx skills add rossboyd\u002Fquickque --skill notion-spec-to-implementation",{"tool":43,"command":44},"pnpm","pnpm dlx skills add rossboyd\u002Fquickque --skill notion-spec-to-implementation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002FSKILL.md",true,[48,54,60,64,68,72,76,80,84,88,93,97,101,105,109,113,117,121],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",339,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"assets\u002Fnotion-small.svg","ASSET","资产文件",1561,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Fassets\u002Fnotion-small.svg",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"assets\u002Fnotion.png",8526,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Fassets\u002Fnotion.png",{"path":65,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":66,"sourceHtmlUrl":67},"evaluations\u002Fbasic-spec-implementation.json",2358,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Fevaluations\u002Fbasic-spec-implementation.json",{"path":69,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":70,"sourceHtmlUrl":71},"evaluations\u002FREADME.md",4441,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Fevaluations\u002FREADME.md",{"path":73,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":74,"sourceHtmlUrl":75},"evaluations\u002Fspec-to-tasks.json",2504,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Fevaluations\u002Fspec-to-tasks.json",{"path":77,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":78,"sourceHtmlUrl":79},"examples\u002Fapi-feature.md",14073,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Fexamples\u002Fapi-feature.md",{"path":81,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":82,"sourceHtmlUrl":83},"examples\u002Fdatabase-migration.md",2639,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Fexamples\u002Fdatabase-migration.md",{"path":85,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":86,"sourceHtmlUrl":87},"examples\u002Fui-component.md",2150,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Fexamples\u002Fui-component.md",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",1057,{"path":94,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":95,"sourceHtmlUrl":96},"reference\u002Fmilestone-summary-template.md",455,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Fmilestone-summary-template.md",{"path":98,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":99,"sourceHtmlUrl":100},"reference\u002Fprogress-tracking.md",9018,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Fprogress-tracking.md",{"path":102,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":103,"sourceHtmlUrl":104},"reference\u002Fprogress-update-template.md",419,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Fprogress-update-template.md",{"path":106,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":107,"sourceHtmlUrl":108},"reference\u002Fquick-implementation-plan.md",479,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Fquick-implementation-plan.md",{"path":110,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":111,"sourceHtmlUrl":112},"reference\u002Fspec-parsing.md",7057,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Fspec-parsing.md",{"path":114,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":115,"sourceHtmlUrl":116},"reference\u002Fstandard-implementation-plan.md",3285,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Fstandard-implementation-plan.md",{"path":118,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":119,"sourceHtmlUrl":120},"reference\u002Ftask-creation-template.md",596,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Ftask-creation-template.md",{"path":122,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":123,"sourceHtmlUrl":124},"reference\u002Ftask-creation.md",8025,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Ftask-creation.md",[126,135,143,150,157,165],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":130,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":20},"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":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":130,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":20},"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":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":20},"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":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":20},"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":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":130,"licenseFileUrl":161,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":20},"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":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":130,"licenseFileUrl":169,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":20},"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",[],[]]