[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M791ZHSX7KE0DTZRZPYVC6G1":3,"skill-same:01M791ZHSX7KE0DTZRZPYVC6G1":54},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M791ZHSX7KE0DTZRZPYVC6G1","qa",null,"Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions \"QA session\".","dotlas\u002Fskills","dotlas","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F88832003?v=4","01M791ZCS9BAQ40PZ8ADG8TCR1","Dotlas","01M791ZCT18PGXY969S8EZ1MVV",2,"MIT","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fcoding\u002Fqa\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: qa\ndescription: Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions \"QA session\".\n---\n# QA Session\n\nRun an interactive QA session.\nThe user describes problems they’re encountering.\nYou clarify, explore the codebase for context, and file GitHub issues that are durable,\nuser-focused, and use the project’s domain language.\n\n## For each issue the user raises\n\n### 1. Listen and lightly clarify\n\nLet the user describe the problem in their own words.\nAsk **at most 2-3 short clarifying questions** focused on:\n\n- What they expected vs what actually happened\n- Steps to reproduce (if not obvious)\n- Whether it’s consistent or intermittent\n\nDo NOT over-interview.\nIf the description is clear enough to file, move on.\n\n### 2. Explore the codebase in the background\n\nWhile talking to the user, kick off an Agent (subagent_type=Explore) in the background\nto understand the relevant area.\nThe goal is NOT to find a fix — it’s to:\n\n- Learn the domain language used in that area (check UBIQUITOUS_LANGUAGE.md)\n- Understand what the feature is supposed to do\n- Identify the user-facing behavior boundary\n\nThis context helps you write a better issue — but the issue itself should NOT reference\nspecific files, line numbers, or internal implementation details.\n\n### 3. Assess scope: single issue or breakdown?\n\nBefore filing, decide whether this is a **single issue** or needs to be **broken down**\ninto multiple issues.\n\nBreak down when:\n\n- The fix spans multiple independent areas (e.g. “the form validation is wrong AND the\n  success message is missing AND the redirect is broken”)\n- There are clearly separable concerns that different people could work on in parallel\n- The user describes something that has multiple distinct failure modes or symptoms\n\nKeep as a single issue when:\n\n- It’s one behavior that’s wrong in one place\n- The symptoms are all caused by the same root behavior\n\n### 4. File the GitHub issue(s)\n\nCreate issues with `gh issue create`. Do NOT ask the user to review first — just file\nand share URLs.\n\nIssues must be **durable** — they should still make sense after major refactors.\nWrite from the user’s perspective.\n\n#### For a single issue\n\nUse this template:\n\n```\n## What happened\n\n[Describe the actual behavior the user experienced, in plain language]\n\n## What I expected\n\n[Describe the expected behavior]\n\n## Steps to reproduce\n\n1. [Concrete, numbered steps a developer can follow]\n2. [Use domain terms from the codebase, not internal module names]\n3. [Include relevant inputs, flags, or configuration]\n\n## Additional context\n\n[Any extra observations from the user or from codebase exploration that help frame the issue — e.g. \"this only happens when using the Docker layer, not the filesystem layer\" — use domain language but don't cite files]\n```\n\n#### For a breakdown (multiple issues)\n\nCreate issues in dependency order (blockers first) so you can reference real issue\nnumbers.\n\nUse this template for each sub-issue:\n\n```\n## Parent issue\n\n#\u003Cparent-issue-number> (if you created a tracking issue) or \"Reported during QA session\"\n\n## What's wrong\n\n[Describe this specific behavior problem — just this slice, not the whole report]\n\n## What I expected\n\n[Expected behavior for this specific slice]\n\n## Steps to reproduce\n\n1. [Steps specific to THIS issue]\n\n## Blocked by\n\n- #\u003Cissue-number> (if this issue can't be fixed until another is resolved)\n\nOr \"None — can start immediately\" if no blockers.\n\n## Additional context\n\n[Any extra observations relevant to this slice]\n```\n\nWhen creating a breakdown:\n\n- **Prefer many thin issues over few thick ones** — each should be independently fixable\n  and verifiable\n- **Mark blocking relationships honestly** — if issue B genuinely can’t be tested until\n  issue A is fixed, say so.\n  If they’re independent, mark both as “None — can start immediately”\n- **Create issues in dependency order** so you can reference real issue numbers in\n  “Blocked by”\n- **Maximize parallelism** — the goal is that multiple people (or agents) can grab\n  different issues simultaneously\n\n#### Rules for all issue bodies\n\n- **No file paths or line numbers** — these go stale\n- **Use the project’s domain language** (check UBIQUITOUS_LANGUAGE.md if it exists)\n- **Describe behaviors, not code** — “the sync service fails to apply the patch” not\n  “applyPatch() throws on line 42”\n- **Reproduction steps are mandatory** — if you can’t determine them, ask the user\n- **Keep it concise** — a developer should be able to read the issue in 30 seconds\n\nAfter filing, print all issue URLs (with blocking relationships summarized) and ask:\n“Next issue, or are we done?”\n\n### 5. Continue the session\n\nKeep going until the user says they’re done.\nEach issue is independent — don’t batch them.\n","# QA Session\n\nRun an interactive QA session.\nThe user describes problems they’re encountering.\nYou clarify, explore the codebase for context, and file GitHub issues that are durable,\nuser-focused, and use the project’s domain language.\n\n## For each issue the user raises\n\n### 1. Listen and lightly clarify\n\nLet the user describe the problem in their own words.\nAsk **at most 2-3 short clarifying questions** focused on:\n\n- What they expected vs what actually happened\n- Steps to reproduce (if not obvious)\n- Whether it’s consistent or intermittent\n\nDo NOT over-interview.\nIf the description is clear enough to file, move on.\n\n### 2. Explore the codebase in the background\n\nWhile talking to the user, kick off an Agent (subagent_type=Explore) in the background\nto understand the relevant area.\nThe goal is NOT to find a fix — it’s to:\n\n- Learn the domain language used in that area (check UBIQUITOUS_LANGUAGE.md)\n- Understand what the feature is supposed to do\n- Identify the user-facing behavior boundary\n\nThis context helps you write a better issue — but the issue itself should NOT reference\nspecific files, line numbers, or internal implementation details.\n\n### 3. Assess scope: single issue or breakdown?\n\nBefore filing, decide whether this is a **single issue** or needs to be **broken down**\ninto multiple issues.\n\nBreak down when:\n\n- The fix spans multiple independent areas (e.g. “the form validation is wrong AND the\n  success message is missing AND the redirect is broken”)\n- There are clearly separable concerns that different people could work on in parallel\n- The user describes something that has multiple distinct failure modes or symptoms\n\nKeep as a single issue when:\n\n- It’s one behavior that’s wrong in one place\n- The symptoms are all caused by the same root behavior\n\n### 4. File the GitHub issue(s)\n\nCreate issues with `gh issue create`. Do NOT ask the user to review first — just file\nand share URLs.\n\nIssues must be **durable** — they should still make sense after major refactors.\nWrite from the user’s perspective.\n\n#### For a single issue\n\nUse this template:\n\n```\n## What happened\n\n[Describe the actual behavior the user experienced, in plain language]\n\n## What I expected\n\n[Describe the expected behavior]\n\n## Steps to reproduce\n\n1. [Concrete, numbered steps a developer can follow]\n2. [Use domain terms from the codebase, not internal module names]\n3. [Include relevant inputs, flags, or configuration]\n\n## Additional context\n\n[Any extra observations from the user or from codebase exploration that help frame the issue — e.g. \"this only happens when using the Docker layer, not the filesystem layer\" — use domain language but don't cite files]\n```\n\n#### For a breakdown (multiple issues)\n\nCreate issues in dependency order (blockers first) so you can reference real issue\nnumbers.\n\nUse this template for each sub-issue:\n\n```\n## Parent issue\n\n#\u003Cparent-issue-number> (if you created a tracking issue) or \"Reported during QA session\"\n\n## What's wrong\n\n[Describe this specific behavior problem — just this slice, not the whole report]\n\n## What I expected\n\n[Expected behavior for this specific slice]\n\n## Steps to reproduce\n\n1. [Steps specific to THIS issue]\n\n## Blocked by\n\n- #\u003Cissue-number> (if this issue can't be fixed until another is resolved)\n\nOr \"None — can start immediately\" if no blockers.\n\n## Additional context\n\n[Any extra observations relevant to this slice]\n```\n\nWhen creating a breakdown:\n\n- **Prefer many thin issues over few thick ones** — each should be independently fixable\n  and verifiable\n- **Mark blocking relationships honestly** — if issue B genuinely can’t be tested until\n  issue A is fixed, say so.\n  If they’re independent, mark both as “None — can start immediately”\n- **Create issues in dependency order** so you can reference real issue numbers in\n  “Blocked by”\n- **Maximize parallelism** — the goal is that multiple people (or agents) can grab\n  different issues simultaneously\n\n#### Rules for all issue bodies\n\n- **No file paths or line numbers** — these go stale\n- **Use the project’s domain language** (check UBIQUITOUS_LANGUAGE.md if it exists)\n- **Describe behaviors, not code** — “the sync service fails to apply the patch” not\n  “applyPatch() throws on line 42”\n- **Reproduction steps are mandatory** — if you can’t determine them, ask the user\n- **Keep it concise** — a developer should be able to read the issue in 30 seconds\n\nAfter filing, print all issue URLs (with blocking relationships summarized) and ask:\n“Next issue, or are we done?”\n\n### 5. Continue the session\n\nKeep going until the user says they’re done.\nEach issue is independent — don’t batch them.\n",{"name":5,"description":7},"main","44a7c5d185b1020f689d2129547d7470c3715e76","skills\u002Fcommunity\u002Fcoding\u002Fqa",0,"https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills","https:\u002F\u002Fwww.skills.sh\u002Fdotlas\u002Fskills","https:\u002F\u002Fgithub.com\u002Fdotlas","www.dotlas.com","A platform to help companies make better city-level decisions and improve the bottom line of their retail footprint.","2026-10-27 22:40:58",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add dotlas\u002Fskills --skill qa",{"tool":40,"command":41},"bunx","bunx skills add dotlas\u002Fskills --skill qa",{"tool":43,"command":44},"pnpm","pnpm dlx skills add dotlas\u002Fskills --skill qa","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fcoding\u002Fqa\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",91,"https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fcoding\u002Fqa\u002Fagents\u002Fopenai.yaml",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M792400972AXPY3XESVHRFRA","where-were-we","Provide the user with a refresher of existing chat turns. Useful when the user wants to understand where we stand in the conversation.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fwhere-were-we\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7923T58GM9G9TVAZB9TGTWE","update-global-dotlas-skills","Sync the globally-installed dotlas\u002Fskills catalog and prune stale remnants. Runs the documented global install command, then detects skills that were installed from dotlas\u002Fskills but no longer exist in the catalog and removes them (with confirmation). Use when the user wants to update, refresh, or clean up their global Dotlas skills, or invokes \u002Fupdate-global-dotlas-skills.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fupdate-global-dotlas-skills\u002FSKILL.md",[],[],{"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":75,"publishedAt":19},"01M7923KGCMXT25Y7XVC6G1ERX","unpack","Explain an unfamiliar thing plainly and from first principles, structured so the reader sees why it is true. Use when someone is trying to understand something — a dense or jargon-heavy passage, a baffling error, an unfamiliar mechanism, a codebase, or a document — asks to break something down (\"walk me through this\", \"what does this actually mean\"), or wants their intent turned into a precise instruction for another agent. Trigger on confusion or a request to understand, not on difficulty alone; technical or long content is not itself a signal.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Funpack\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7923HNVVHRKRVQ5M0P7TXZA","sum","Use when the previous response is too technical, complex, or jargon-heavy and needs a clear, plain-language explanation","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fsum\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},"01M7923CY3FR71VPKBYRHZNNVH","slack","Compose a Slack message, or digest a Slack thread into compact context. Use when the user asks to reply to a person or channel, write a Slack post, or catch up on a thread without reading the whole transcript. This skill covers how to write well for Slack — both jobs share the same standard.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fslack\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},"01M79234W72RKWYV2S38G2B0SY","plan-with-me","Collaborative, human-in-the-loop planning for something new that spans several parts and needs human judgement at each fork. A brainstorming partner that funnels — each fork opens up the real options, then narrows to a decision, surfacing caveats and breaking points, and co-authoring the plan instead of guessing alone. Fits any domain where you plan something new against existing context. Resolves one decision at a time, each with a recommendation, then emits a lightweight plan to hand off for implementation. Use when planning alone would make wrong assumptions, or the user wants to shape something new together.","https:\u002F\u002Fgithub.com\u002Fdotlas\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcustom\u002Fcommon\u002Fplan-with-me\u002FSKILL.md",[],[]]