[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76VHBA2A1WQB74PAP7E7WXB":3,"skill-same:01M76VHBA2A1WQB74PAP7E7WXB":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M76VHBA2A1WQB74PAP7E7WXB","yeet",null,"Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","lzy18001500226\u002FMoSim","lzy18001500226","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F152623587?v=4","01M71ZMEX36NK05B642131DEEK","01M71ZMEXSMX72KPVNJ572G0CM",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FSkills\u002Fopenai-skills\u002Fskills\u002F.curated\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FSkills\u002Fopenai-skills\u002Fskills\u002F.curated\u002Fyeet\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"yeet\"\ndescription: \"Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).\"\n---\n\n## Prerequisites\n\n- Require GitHub CLI `gh`. Check `gh --version`. If missing, ask the user to install `gh` and stop.\n- Require authenticated `gh` session. Run `gh auth status`. If not authenticated, ask the user to run `gh auth login` (and re-run `gh auth status`) before continuing.\n\n## Naming conventions\n\n- Branch: `{description}` when starting from main\u002Fmaster\u002Fdefault.\n- Commit: `{description}` (terse).\n- PR title: `{description}` summarizing the full diff.\n\n## PR template discovery\n\nBefore creating the PR, resolve the repository root and look for the active GitHub PR template from there:\n\n```shell\nrepo_root=\"$(git rev-parse --show-toplevel)\"\n```\n\nTemplate candidates, in order:\n\n- `.github\u002Fpull_request_template.md`\n- `.github\u002FPULL_REQUEST_TEMPLATE.md`\n- One `*.md` file under `.github\u002Fpull_request_template\u002F`\n- One `*.md` file under `.github\u002FPULL_REQUEST_TEMPLATE\u002F`\n\nUse paths as emitted from the repository root, such as `.github\u002Fpull_request_template.md`, not `.\u002F.github\u002Fpull_request_template.md`.\n\nIf exactly one template is found, read it before composing the final PR body and pass it to `gh pr create` with `--template \"$template\"`.\n\nIf multiple template files are found, stop before PR creation and ask which template to use. If no template exists, use the fallback body shape in this skill.\n\n## Workflow\n\n- If on main\u002Fmaster\u002Fdefault, create a branch: `git checkout -b \"{description}\"`\n- Otherwise stay on the current branch.\n- Confirm status, then stage everything: `git status -sb` then `git add -A`.\n- Commit tersely with the description: `git commit -m \"{description}\"`\n- Run checks if not already. If checks fail due to missing deps\u002Ftools, install dependencies and rerun once.\n- Push with tracking: `git push -u origin $(git branch --show-current)`\n- If git push fails due to workflow auth errors, pull from master and retry the push.\n- Discover and read the repository PR template, if any.\n- Check whether the current branch already has a PR: `gh pr view \"$(git branch --show-current)\" --json number,isDraft,url`\n- If a PR already exists, update that PR in place. Do not create another PR, and do not change whether the existing PR is draft or ready for review.\n- If no PR exists, open a new draft PR:\n  - With one template: `GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --template \"$template\" --head \"$(git branch --show-current)\"`\n  - Without a template: `GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --head \"$(git branch --show-current)\"`\n- Edit the PR title and body so they reflect the actual net change in the diff.\n- Write the PR description to a temp file with real newlines and pass it via `--body-file` or `gh pr edit --body-file` to avoid `\\n`-escaped markdown.\n\n## Determining the PR\n\nWhen updating a PR created earlier in the flow, infer the PR from the current branch when possible:\n\n```shell\ngit branch --show-current\ngh pr view \"$(git branch --show-current)\" --json number --jq '.number'\n```\n\nIf this finds an existing PR, preserve its current review state. Never convert an existing ready-for-review PR back to draft as part of `yeet`; only new PRs created by this flow should start as draft.\n\n## PR Title\n\nFormat: `\u003Ctype>(\u003Cscope>): \u003Csubject>`\n\n`\u003Cscope>` is optional. A scope consist of a noun describing a section of the codebase (component, service or subsytem).\n\n### Example\n\n```\nfeat: add hat wobble\n^--^  ^------------^\n|     |\n|     +-> Summary in present tense.\n|\n+-------> Type: chore, docs, feat, fix, refactor, style, or test.\n```\n\nMore Examples:\n\n- `feat`: (new feature for the user, not a new feature for build script)\n- `fix`: (bug fix for the user, not a fix to a build script)\n- `docs`: (changes to the documentation)\n- `style`: (formatting, missing semi colons, etc; no production code change)\n- `refactor`: (refactoring production code, eg. renaming a variable)\n- `test`: (adding missing tests, refactoring tests; no production code change)\n- `chore`: (updating grunt tasks etc; no production code change)\n\n\n## PR Body Contents\n\nWhen invoked, use `gh` to edit the pull request body and title to reflect the contents of the specified PR. Make sure to check the existing pull request body to see if there is key information that should be preserved. For example, NEVER remove an image in the existing pull request body, as the author may have no way to recover it if you remove it.\n\nWhen a repository PR template exists, adapt the final PR body to that template. Preserve meaningful headings, required checklists, and repo-specific prompts, but replace placeholder text with net-diff-specific content or `N\u002FA` where the template asks for it. Do not discard template sections just because the fallback shape below is shorter.\n\nIt is critically important to explain _why_ the change is being made. If the current conversation in which this skill is invoked has discussed the motivation, be sure to capture this in the pull request body.\n\nThe body should also explain _what_ changed, but this should appear after the _why_.\n\nLimit discussion to the _net change_ of the commit. It is generally frowned upon to discuss changes that were attempted but later undone in the course of the development of the pull request. When rewriting the pull request body, you may need to eliminate details such as these when they are no longer appropriate \u002F of interest to future readers.\n\nAvoid references to absolute paths on my local disk. When talking about a path that is within the repository, simply use the repo-relative path.\n\nDefault to omitting `Verification`. Add it only when you have behavioral evidence worth preserving for reviewers: a reproduced bug, a before\u002Fafter check, a targeted test that exercises the changed behavior, or a manual scenario with input and observed outcome. Do not use it for generic commands or automation results such as package tests, type checks, linters, formatters, pre-commit\u002Fpre-push hooks, or CI status.\n\nIf the repository template requires a validation or verification section, keep that section and avoid generic filler: include meaningful commands\u002Fresults, a targeted manual scenario, or `Not run` with a reason.\n\nUse professional Markdown:\n\n- Put code, paths, commands, flags, and identifiers in backticks.\n- Use fenced code blocks for shell transcripts or multi-line examples.\n- Use GitHub permalinks when citing existing code relevant to the change.\n- Reference relevant issues or related PRs, but do not reference the PR in its own body.\n\n### Suggested PR Body Shape\n\nUse this as a fallback when the repository does not have a PR template:\n\n```markdown\n## Why\n\nDescribe the user-facing or maintainer-facing problem, including cause and effect where useful.\n\n## What Changed\n\nDescribe the net implementation change in concise prose.\n```\n","## Prerequisites\n\n- Require GitHub CLI `gh`. Check `gh --version`. If missing, ask the user to install `gh` and stop.\n- Require authenticated `gh` session. Run `gh auth status`. If not authenticated, ask the user to run `gh auth login` (and re-run `gh auth status`) before continuing.\n\n## Naming conventions\n\n- Branch: `{description}` when starting from main\u002Fmaster\u002Fdefault.\n- Commit: `{description}` (terse).\n- PR title: `{description}` summarizing the full diff.\n\n## PR template discovery\n\nBefore creating the PR, resolve the repository root and look for the active GitHub PR template from there:\n\n```shell\nrepo_root=\"$(git rev-parse --show-toplevel)\"\n```\n\nTemplate candidates, in order:\n\n- `.github\u002Fpull_request_template.md`\n- `.github\u002FPULL_REQUEST_TEMPLATE.md`\n- One `*.md` file under `.github\u002Fpull_request_template\u002F`\n- One `*.md` file under `.github\u002FPULL_REQUEST_TEMPLATE\u002F`\n\nUse paths as emitted from the repository root, such as `.github\u002Fpull_request_template.md`, not `.\u002F.github\u002Fpull_request_template.md`.\n\nIf exactly one template is found, read it before composing the final PR body and pass it to `gh pr create` with `--template \"$template\"`.\n\nIf multiple template files are found, stop before PR creation and ask which template to use. If no template exists, use the fallback body shape in this skill.\n\n## Workflow\n\n- If on main\u002Fmaster\u002Fdefault, create a branch: `git checkout -b \"{description}\"`\n- Otherwise stay on the current branch.\n- Confirm status, then stage everything: `git status -sb` then `git add -A`.\n- Commit tersely with the description: `git commit -m \"{description}\"`\n- Run checks if not already. If checks fail due to missing deps\u002Ftools, install dependencies and rerun once.\n- Push with tracking: `git push -u origin $(git branch --show-current)`\n- If git push fails due to workflow auth errors, pull from master and retry the push.\n- Discover and read the repository PR template, if any.\n- Check whether the current branch already has a PR: `gh pr view \"$(git branch --show-current)\" --json number,isDraft,url`\n- If a PR already exists, update that PR in place. Do not create another PR, and do not change whether the existing PR is draft or ready for review.\n- If no PR exists, open a new draft PR:\n  - With one template: `GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --template \"$template\" --head \"$(git branch --show-current)\"`\n  - Without a template: `GH_PROMPT_DISABLED=1 GIT_TERMINAL_PROMPT=0 gh pr create --draft --fill --head \"$(git branch --show-current)\"`\n- Edit the PR title and body so they reflect the actual net change in the diff.\n- Write the PR description to a temp file with real newlines and pass it via `--body-file` or `gh pr edit --body-file` to avoid `\\n`-escaped markdown.\n\n## Determining the PR\n\nWhen updating a PR created earlier in the flow, infer the PR from the current branch when possible:\n\n```shell\ngit branch --show-current\ngh pr view \"$(git branch --show-current)\" --json number --jq '.number'\n```\n\nIf this finds an existing PR, preserve its current review state. Never convert an existing ready-for-review PR back to draft as part of `yeet`; only new PRs created by this flow should start as draft.\n\n## PR Title\n\nFormat: `\u003Ctype>(\u003Cscope>): \u003Csubject>`\n\n`\u003Cscope>` is optional. A scope consist of a noun describing a section of the codebase (component, service or subsytem).\n\n### Example\n\n```\nfeat: add hat wobble\n^--^  ^------------^\n|     |\n|     +-> Summary in present tense.\n|\n+-------> Type: chore, docs, feat, fix, refactor, style, or test.\n```\n\nMore Examples:\n\n- `feat`: (new feature for the user, not a new feature for build script)\n- `fix`: (bug fix for the user, not a fix to a build script)\n- `docs`: (changes to the documentation)\n- `style`: (formatting, missing semi colons, etc; no production code change)\n- `refactor`: (refactoring production code, eg. renaming a variable)\n- `test`: (adding missing tests, refactoring tests; no production code change)\n- `chore`: (updating grunt tasks etc; no production code change)\n\n\n## PR Body Contents\n\nWhen invoked, use `gh` to edit the pull request body and title to reflect the contents of the specified PR. Make sure to check the existing pull request body to see if there is key information that should be preserved. For example, NEVER remove an image in the existing pull request body, as the author may have no way to recover it if you remove it.\n\nWhen a repository PR template exists, adapt the final PR body to that template. Preserve meaningful headings, required checklists, and repo-specific prompts, but replace placeholder text with net-diff-specific content or `N\u002FA` where the template asks for it. Do not discard template sections just because the fallback shape below is shorter.\n\nIt is critically important to explain _why_ the change is being made. If the current conversation in which this skill is invoked has discussed the motivation, be sure to capture this in the pull request body.\n\nThe body should also explain _what_ changed, but this should appear after the _why_.\n\nLimit discussion to the _net change_ of the commit. It is generally frowned upon to discuss changes that were attempted but later undone in the course of the development of the pull request. When rewriting the pull request body, you may need to eliminate details such as these when they are no longer appropriate \u002F of interest to future readers.\n\nAvoid references to absolute paths on my local disk. When talking about a path that is within the repository, simply use the repo-relative path.\n\nDefault to omitting `Verification`. Add it only when you have behavioral evidence worth preserving for reviewers: a reproduced bug, a before\u002Fafter check, a targeted test that exercises the changed behavior, or a manual scenario with input and observed outcome. Do not use it for generic commands or automation results such as package tests, type checks, linters, formatters, pre-commit\u002Fpre-push hooks, or CI status.\n\nIf the repository template requires a validation or verification section, keep that section and avoid generic filler: include meaningful commands\u002Fresults, a targeted manual scenario, or `Not run` with a reason.\n\nUse professional Markdown:\n\n- Put code, paths, commands, flags, and identifiers in backticks.\n- Use fenced code blocks for shell transcripts or multi-line examples.\n- Use GitHub permalinks when citing existing code relevant to the change.\n- Reference relevant issues or related PRs, but do not reference the PR in its own body.\n\n### Suggested PR Body Shape\n\nUse this as a fallback when the repository does not have a PR template:\n\n```markdown\n## Why\n\nDescribe the user-facing or maintainer-facing problem, including cause and effect where useful.\n\n## What Changed\n\nDescribe the net implementation change in concise prose.\n```\n",{"name":5,"description":7},"main","e0ec177d00f087cb04e90206b2f7d3aa2f5a1350","References\u002FAgent\u002FSkills\u002Fopenai-skills\u002Fskills\u002F.curated\u002Fyeet","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim","https:\u002F\u002Fgithub.com\u002Flzy18001500226","2026-08-31 23:29:00",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add lzy18001500226\u002FMoSim --skill yeet",{"tool":36,"command":37},"bunx","bunx skills add lzy18001500226\u002FMoSim --skill yeet",{"tool":39,"command":40},"pnpm","pnpm dlx skills add lzy18001500226\u002FMoSim --skill yeet","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FSkills\u002Fopenai-skills\u002Fskills\u002F.curated\u002Fyeet\u002FSKILL.md",true,[44,50,56,60],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",273,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FSkills\u002Fopenai-skills\u002Fskills\u002F.curated\u002Fyeet\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Fyeet-small.svg","ASSET","资产文件",967,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FSkills\u002Fopenai-skills\u002Fskills\u002F.curated\u002Fyeet\u002Fassets\u002Fyeet-small.svg",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"assets\u002Fyeet.png",1262,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FSkills\u002Fopenai-skills\u002Fskills\u002F.curated\u002Fyeet\u002Fassets\u002Fyeet.png",{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",10776,[66,75,83,91,99,107],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":74},"01M78RK6JGRPTD3TDSMTQWDQ9P","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).","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":74},"01M78RK29KVRDQXSMVZX1GQTJN","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 Codex's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":74},"01M78RJPF3210Y5DA9VJ6JMMG6","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\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":74},"01M78RJH7X67C5AY8ZVS7RQNWJ","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\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":74},"01M78RBBAYMJ6T3ZMAYHCFM6G7","skill-creator-cc","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M76VV9V2R9FZTVGMJZV7Y996","prd-writing-guide","Write complete, unambiguous PRDs that development teams can implement without guesswork. Includes requirement discovery framework, structured documentation methodology, completeness checklists, and common pitfall avoidance. Use when: writing new PRDs, reviewing PRD drafts, validating requirement completeness, preparing for engineering handoff. Triggers: 'write PRD', '写PRD', '产品需求文档', '需求文档', '需求规格', '需求评审', '完善需求', 'create requirements doc', 'product requirements', 'feature spec', 'requirements document'. Anti-triggers: 'technical design doc', 'architecture design', 'implementation plan', 'API design', '架构设计', '技术方案', '实现方案', '接口设计'.","MIT","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FSKILL.md",[],[]]