[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79GK59DTMT87RWEXWDF5EN4":3,"skill-same:01M79GK59DTMT87RWEXWDF5EN4":52},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M79GK59DTMT87RWEXWDF5EN4","user-story",null,"Convert the current context, task, bug, or feature request into a detailed User Story following a structured format that includes: As a [role], I want [goal] so that [benefit], detailed acceptance criteria, links to all GitHub work (issues, PRs, commits), citations for every external reference, and a dedicated \"Reasoning & Reproducibility for LLMs\" section. Use when the user says \"turn this into a user story\", \"write a user story for...\", \"\u002Fuser-story\", \"grok-task-v3-user-story\", or needs traceable product requirements.","zfifteen\u002Fskills-catalog","zfifteen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221906715?v=4","01M79CQFXDZM5J5CJTCECPFA66","Dionisio Alberto Lopez III","01M79CQFY4C62PN8A2T5KDAHGA",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fuser-story\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: user-story\ndescription: >\n  Convert the current context, task, bug, or feature request into a detailed User Story\n  following a structured format that includes: As a [role], I want [goal] so that [benefit],\n  detailed acceptance criteria, links to all GitHub work (issues, PRs, commits), citations\n  for every external reference, and a dedicated \"Reasoning & Reproducibility for LLMs\"\n  section. Use when the user says \"turn this into a user story\", \"write a user story for...\",\n  \"\u002Fuser-story\", \"grok-task-v3-user-story\", or needs traceable product requirements.\nwhen-to-use: Use when the user wants the current work item expressed as a formal User Story with full traceability and an LLM-reproducibility section.\nargument-hint: \"\u003Cshort goal or feature name>\"\nmetadata:\n  short-description: \"Detailed User Story with GitHub links, citations, and LLM reasoning section\"\n  source: \"ported-from-codex\u002Fgrok-task-v3-user-story\"\n  original_codex: \"grok-task-v3-user-story\"\n---\n\n# User Story\n\nProduce a complete, traceable User Story from the provided material.\n\n## Step 1: Research & Link Everything\nBefore writing:\n- Use `grok_com_github` MCP tools (or `run_terminal_cmd` + `gh` if available) to find and link all related GitHub issues, PRs, commits, and discussions. Quote the most relevant snippets.\n- Use `read_file` + `grep` on the local repo for code, tests, docs that implement or relate to the story.\n- Use `web_search` \u002F `web_fetch` \u002F `open_page` for any external standards, papers, or prior art mentioned. Capture exact titles, authors, URLs, and 1-2 sentence relevance + access date.\n- If images, logs, or attachments were provided, describe their content precisely and link or embed references.\n\n## Step 2: Write the User Story\nUse this exact structure (Markdown):\n\n```markdown\n# User Story: \u003CShort Title>\n\n**As a** [specific role, e.g. \"researcher analyzing prime gaps > 10^18\" or \"maintainer of the Z5D predictor\"],\n**I want** [clear goal],\n**so that** [business or research benefit \u002F outcome].\n\n## Acceptance Criteria\n- [ ] AC1: ...\n- [ ] AC2: ... (each must be testable \u002F demonstrable)\n...\n\n## Detailed Requirements\n- Functional\n- Non-functional (performance, accuracy, reproducibility)\n- Edge cases \u002F error handling\n\n## References & Provenance\n### GitHub Work\n- Issue #123: \"...\" (link) — relevant quote\n- PR #456 (merged): \"...\" (link) — files changed summary\n- Commit abc1234: \"...\"\n\n### External Citations\n- Paper: \"Title\" by Author (Year) — URL — \"Exact quote or finding used\"\n- Standard \u002F Spec: ...\n\n### Local Code & Docs\n- `path\u002Fto\u002Ffile.py:42` — \"key function or comment\"\n- `AGENTS.md` — \"PGS-first requirement\"\n\n## Reasoning & Reproducibility for LLMs\n**Context captured at time of writing:** [UTC timestamp]\n\n**Key observations from tools:**\n1. ...\n2. ...\n\n**Why this story is prioritized now:**\n- ...\n\n**Potential implementation notes (non-binding):**\n- ...\n\n**How another LLM can reproduce this analysis:**\n1. Clone repo at \u003Ccommit or branch>.\n2. Run `grep -r \"...\"` for ...\n3. Read the exact files listed above.\n4. ...\n\n## Out of Scope\n- ...\n```\n\n## Step 3: Validate Traceability\n- Every acceptance criterion must be derivable from the \"References & Provenance\" section.\n- The \"Reasoning & Reproducibility for LLMs\" section must contain enough concrete commands, file paths, and quotes that a fresh model with the same tools can arrive at the same story.\n\n## Step 4: Present\nShow the full story. Offer:\n- \"Save this to a local file under docs\u002Fuser-stories\u002F ?\"\n- \"Convert one or more ACs into `\u002Ftechnical-task` GitHub issues?\"\n- \"Create an `\u002Fimplementation-plan` from this story?\"\n\n## Success Criteria\n- A product manager or new engineer can understand the \"why\" and \"what done looks like\" without reading the entire conversation.\n- Every external or GitHub claim has a working link + verbatim supporting quote captured at the time of writing.\n- The reproducibility section is genuinely useful to another LLM (not generic advice).\n\n## For This Repo\nUser stories involving prime-gap or number-theoretic work must explicitly reference the AGENTS.md PGS objects → invariants frame in the Requirements or Reasoning section.\n","# User Story\n\nProduce a complete, traceable User Story from the provided material.\n\n## Step 1: Research & Link Everything\nBefore writing:\n- Use `grok_com_github` MCP tools (or `run_terminal_cmd` + `gh` if available) to find and link all related GitHub issues, PRs, commits, and discussions. Quote the most relevant snippets.\n- Use `read_file` + `grep` on the local repo for code, tests, docs that implement or relate to the story.\n- Use `web_search` \u002F `web_fetch` \u002F `open_page` for any external standards, papers, or prior art mentioned. Capture exact titles, authors, URLs, and 1-2 sentence relevance + access date.\n- If images, logs, or attachments were provided, describe their content precisely and link or embed references.\n\n## Step 2: Write the User Story\nUse this exact structure (Markdown):\n\n```markdown\n# User Story: \u003CShort Title>\n\n**As a** [specific role, e.g. \"researcher analyzing prime gaps > 10^18\" or \"maintainer of the Z5D predictor\"],\n**I want** [clear goal],\n**so that** [business or research benefit \u002F outcome].\n\n## Acceptance Criteria\n- [ ] AC1: ...\n- [ ] AC2: ... (each must be testable \u002F demonstrable)\n...\n\n## Detailed Requirements\n- Functional\n- Non-functional (performance, accuracy, reproducibility)\n- Edge cases \u002F error handling\n\n## References & Provenance\n### GitHub Work\n- Issue #123: \"...\" (link) — relevant quote\n- PR #456 (merged): \"...\" (link) — files changed summary\n- Commit abc1234: \"...\"\n\n### External Citations\n- Paper: \"Title\" by Author (Year) — URL — \"Exact quote or finding used\"\n- Standard \u002F Spec: ...\n\n### Local Code & Docs\n- `path\u002Fto\u002Ffile.py:42` — \"key function or comment\"\n- `AGENTS.md` — \"PGS-first requirement\"\n\n## Reasoning & Reproducibility for LLMs\n**Context captured at time of writing:** [UTC timestamp]\n\n**Key observations from tools:**\n1. ...\n2. ...\n\n**Why this story is prioritized now:**\n- ...\n\n**Potential implementation notes (non-binding):**\n- ...\n\n**How another LLM can reproduce this analysis:**\n1. Clone repo at \u003Ccommit or branch>.\n2. Run `grep -r \"...\"` for ...\n3. Read the exact files listed above.\n4. ...\n\n## Out of Scope\n- ...\n```\n\n## Step 3: Validate Traceability\n- Every acceptance criterion must be derivable from the \"References & Provenance\" section.\n- The \"Reasoning & Reproducibility for LLMs\" section must contain enough concrete commands, file paths, and quotes that a fresh model with the same tools can arrive at the same story.\n\n## Step 4: Present\nShow the full story. Offer:\n- \"Save this to a local file under docs\u002Fuser-stories\u002F ?\"\n- \"Convert one or more ACs into `\u002Ftechnical-task` GitHub issues?\"\n- \"Create an `\u002Fimplementation-plan` from this story?\"\n\n## Success Criteria\n- A product manager or new engineer can understand the \"why\" and \"what done looks like\" without reading the entire conversation.\n- Every external or GitHub claim has a working link + verbatim supporting quote captured at the time of writing.\n- The reproducibility section is genuinely useful to another LLM (not generic advice).\n\n## For This Repo\nUser stories involving prime-gap or number-theoretic work must explicitly reference the AGENTS.md PGS objects → invariants frame in the Requirements or Reasoning section.\n",{"name":5,"metadata":24,"description":28,"when-to-use":29,"argument-hint":30},{"source":25,"original_codex":26,"short-description":27},"ported-from-codex\u002Fgrok-task-v3-user-story","grok-task-v3-user-story","Detailed User Story with GitHub links, citations, and LLM reasoning section","Convert the current context, task, bug, or feature request into a detailed User Story following a structured format that includes: As a [role], I want [goal] so that [benefit], detailed acceptance criteria, links to all GitHub work (issues, PRs, commits), citations for every external reference, and a dedicated \"Reasoning & Reproducibility for LLMs\" section. Use when the user says \"turn this into a user story\", \"write a user story for...\", \"\u002Fuser-story\", \"grok-task-v3-user-story\", or needs traceable product requirements.\n","Use when the user wants the current work item expressed as a formal User Story with full traceability and an LLM-reproducibility section.","\u003Cshort goal or feature name>","main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Fuser-story","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002Fzfifteen","I like to measure things.","2026-07-19 23:41:54",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add zfifteen\u002Fskills-catalog --skill user-story",{"tool":44,"command":45},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill user-story",{"tool":47,"command":48},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill user-story","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fuser-story\u002FSKILL.md",true,[],[53,60,67,74,83,90],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79GXQ2PWPT2E4CJYHXVJ0YE","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79GXN85NETKBE06865CWK6Z","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79GXCYD7FGYS932J9N9RFFY","youtube","Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript.  Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or \"what does this video actually say\".  The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content.  Triggers: \"youtube transcript\", \"get the transcript of this video\", \"summarize this youtube video\", \"what did they say in https:\u002F\u002Fyoutube.com\u002F...\", \"key claims from this talk\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79GX8EXHHYM566BKR7MS778","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M79GX2HFJPX84NMRE5VBTYX9","x-post-creator","Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, \u002Fx-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs\u002Fx-posts\u002F[story-name]\u002F.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-post-creator\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M79GWXQT4HBT6QME6QSBZJFA","x-api","Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X\u002Fx.com, reading threads and replies, creating lists, staging\u002Fpublishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions \u002Fx-api or \"search X\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]