[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73407QTP2S6TJT4P3ZXDS6Y":3,"skill-same:01M73407QTP2S6TJT4P3ZXDS6Y":51},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M73407QTP2S6TJT4P3ZXDS6Y","ask-deep-research",null,"Deep Research: Runs autonomous multi-source investigation with contradiction analysis and a cited handoff. Use for complex technical questions. Common triggers: deep research, exhaustive research, comprehensive investigation, complex technical investigation, complex contested high-stakes question, complex compatibility question, complex compatibility issue, complex question, contested research, high-stakes research, full compatibility investigation, compare competing implementations, compare local and upstream implementations, investigate historical changes, determine protocol behaviour, investigate protocol behavior, protocol behavior exhaustively, multiple sources, research everything relevant, investigate open issues, open issues comprehensively, compare against upstream.","MarkBovee\u002Fagent-skills-kit","MarkBovee","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1203948?v=4","01M733X7T9ZYGXR05VBXNZEH36","Mark Bovee","01M733X7V1Q57ZK772WYENHFAV",1,"MIT","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fask-deep-research\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"ask-deep-research\"\ndescription: \"Deep Research: Runs autonomous multi-source investigation with contradiction analysis and a cited handoff. Use for complex technical questions. Common triggers: deep research, exhaustive research, comprehensive investigation, complex technical investigation, complex contested high-stakes question, complex compatibility question, complex compatibility issue, complex question, contested research, high-stakes research, full compatibility investigation, compare competing implementations, compare local and upstream implementations, investigate historical changes, determine protocol behaviour, investigate protocol behavior, protocol behavior exhaustively, multiple sources, research everything relevant, investigate open issues, open issues comprehensively, compare against upstream.\"\ndisable-model-invocation: true\n---\n# ASK Deep Research\n\nTurn hard technical uncertainty into an autonomous research program. Gather and challenge evidence; do not implement source changes.\n\n## Start\n\nWrite a research brief before broad search: question, objectives and decisions enabled, in\u002Fout scope, constraints, key unknowns, initial hypotheses, expected report. Do not repeatedly ask permission when the next source follows from this brief.\n\n## Research Program\n\n1. Build a dynamic plan. Split independent tracks: local implementation, real fixtures\u002Flogs\u002Fcaptures, upstream, history, official standards\u002Fdocs, and community evidence where relevant.\n2. Inspect local code, tests, fixtures, configuration, Git history, issues, and PRs before interpreting external claims about local behavior.\n3. Discover sources broadly, then narrow with identifiers, versions, hardware, protocol fields, and terminology learned. Prefer direct runtime evidence, reproducible tests, source, standards, and official docs.\n4. Delegate independent tracks through `agent-workflows`; coordinator owns scope, evidence reconciliation, plan updates, and synthesis. Report meaningful findings at milestones, not tool noise.\n5. Extract evidence, not URL lists: `Source | section | observation | interpretation | confidence | contradiction`.\n6. Track each important statement as `FACT`, `OBSERVATION`, `INFERENCE`, `HYPOTHESIS`, `ASSUMPTION`, or `UNKNOWN`. Maintain hypotheses with support, contradictions, status (`OPEN`, `SUPPORTED`, `WEAKENED`, `DISPROVEN`, `CONFIRMED`), and confidence.\n7. Compare working\u002Fbroken, old\u002Fnew, local\u002Fupstream, hardware\u002Fsoftware variants, fixtures, timing, fields, mappings, and state transitions. For protocols inspect identity, addresses, IDs, lengths, positions, types, bits, enumerations, read\u002Fwrite semantics, and observed state changes.\n8. After every pass, update plan: learned facts, changed hypotheses, open questions, new leads, and highest-value next source. Emit a checkpoint for long work using [research-report-template.md](.\u002Fresearch-report-template.md).\n9. Search deliberately for disconfirming evidence before conclusions. Resolve conflicts by source authority, scope, history, and reproducible behavior; never silently choose a source.\n10. Stop only when answer is confirmed, actionable despite remaining uncertainty, evidence-blocked, or at diminishing returns. State why and name minimum next evidence.\n\n## Depth\n\n- **Standard:** 3-5 tracks, multiple source types, iterative synthesis.\n- **Comprehensive:** 5-10 tracks plus history, differential analysis, contradiction search, and hypothesis tests.\n- **Exhaustive:** explicit request or justified stakes; expand corpus and track all evidence gaps without inventing certainty.\n\n## Output\n\nUse [research-report-template.md](.\u002Fresearch-report-template.md). Cite every externally derived factual claim; local citations use `path:line`, fixture section, commit, issue, or PR. Include a compact continuation state so a follow-up such as “dig deeper into point 3” resumes rather than restarts.\n\nReturn `ASK_WORKFLOW_PASS phase=RESEARCH` only with cited findings, confidence, remaining gaps, and implementation handoff. Use `ASK_WORKFLOW_BLOCKED phase=RESEARCH` when essential primary evidence is unavailable.\n\n## Use with\n\n- `intake` to classify scope before or after evidence changes the decision\n- `agent-workflows` for independent research tracks and evidence contract\n- `debugging` for root-cause testing after research establishes likely causes\n- `develop` for the separate implementation pass after research handoff\n\n## Avoid\n\n- One-search answers, confirmation bias, or search snippets as proof\n- Treating names as protocol semantics without observed behavior\n- Coding while evidence is still the deliverable\n","# ASK Deep Research\n\nTurn hard technical uncertainty into an autonomous research program. Gather and challenge evidence; do not implement source changes.\n\n## Start\n\nWrite a research brief before broad search: question, objectives and decisions enabled, in\u002Fout scope, constraints, key unknowns, initial hypotheses, expected report. Do not repeatedly ask permission when the next source follows from this brief.\n\n## Research Program\n\n1. Build a dynamic plan. Split independent tracks: local implementation, real fixtures\u002Flogs\u002Fcaptures, upstream, history, official standards\u002Fdocs, and community evidence where relevant.\n2. Inspect local code, tests, fixtures, configuration, Git history, issues, and PRs before interpreting external claims about local behavior.\n3. Discover sources broadly, then narrow with identifiers, versions, hardware, protocol fields, and terminology learned. Prefer direct runtime evidence, reproducible tests, source, standards, and official docs.\n4. Delegate independent tracks through `agent-workflows`; coordinator owns scope, evidence reconciliation, plan updates, and synthesis. Report meaningful findings at milestones, not tool noise.\n5. Extract evidence, not URL lists: `Source | section | observation | interpretation | confidence | contradiction`.\n6. Track each important statement as `FACT`, `OBSERVATION`, `INFERENCE`, `HYPOTHESIS`, `ASSUMPTION`, or `UNKNOWN`. Maintain hypotheses with support, contradictions, status (`OPEN`, `SUPPORTED`, `WEAKENED`, `DISPROVEN`, `CONFIRMED`), and confidence.\n7. Compare working\u002Fbroken, old\u002Fnew, local\u002Fupstream, hardware\u002Fsoftware variants, fixtures, timing, fields, mappings, and state transitions. For protocols inspect identity, addresses, IDs, lengths, positions, types, bits, enumerations, read\u002Fwrite semantics, and observed state changes.\n8. After every pass, update plan: learned facts, changed hypotheses, open questions, new leads, and highest-value next source. Emit a checkpoint for long work using [research-report-template.md](.\u002Fresearch-report-template.md).\n9. Search deliberately for disconfirming evidence before conclusions. Resolve conflicts by source authority, scope, history, and reproducible behavior; never silently choose a source.\n10. Stop only when answer is confirmed, actionable despite remaining uncertainty, evidence-blocked, or at diminishing returns. State why and name minimum next evidence.\n\n## Depth\n\n- **Standard:** 3-5 tracks, multiple source types, iterative synthesis.\n- **Comprehensive:** 5-10 tracks plus history, differential analysis, contradiction search, and hypothesis tests.\n- **Exhaustive:** explicit request or justified stakes; expand corpus and track all evidence gaps without inventing certainty.\n\n## Output\n\nUse [research-report-template.md](.\u002Fresearch-report-template.md). Cite every externally derived factual claim; local citations use `path:line`, fixture section, commit, issue, or PR. Include a compact continuation state so a follow-up such as “dig deeper into point 3” resumes rather than restarts.\n\nReturn `ASK_WORKFLOW_PASS phase=RESEARCH` only with cited findings, confidence, remaining gaps, and implementation handoff. Use `ASK_WORKFLOW_BLOCKED phase=RESEARCH` when essential primary evidence is unavailable.\n\n## Use with\n\n- `intake` to classify scope before or after evidence changes the decision\n- `agent-workflows` for independent research tracks and evidence contract\n- `debugging` for root-cause testing after research establishes likely causes\n- `develop` for the separate implementation pass after research handoff\n\n## Avoid\n\n- One-search answers, confirmation bias, or search snippets as proof\n- Treating names as protocol semantics without observed behavior\n- Coding while evidence is still the deliverable\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","cef5fa0ba7fd07c76ac37b31c2d09db85419e0b9",".github\u002Fskills\u002Fask-deep-research",0,"https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit","https:\u002F\u002Fgithub.com\u002FMarkBovee","2026-11-09 02:17:08",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add MarkBovee\u002Fagent-skills-kit --skill ask-deep-research",{"tool":38,"command":39},"bunx","bunx skills add MarkBovee\u002Fagent-skills-kit --skill ask-deep-research",{"tool":41,"command":42},"pnpm","pnpm dlx skills add MarkBovee\u002Fagent-skills-kit --skill ask-deep-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fask-deep-research\u002FSKILL.md",[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"research-report-template.md","REFERENCE","参考文档",1888,"https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fask-deep-research\u002Fresearch-report-template.md",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7343K5655Z7JCBPJKXMC24K","ask-write-skill","Write Skill: Creates and revises skills and guardrails from reusable workflow gaps. Use when making a skill or when agent behavior exposes a routing gap.","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002Fask-write-skill\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7343G7HSVYVB1BKK49ZD04R","ask-verification","Verification: Proves work is fixed or ready and cleans up changed repos. Use before claiming something works or handing off.","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002Fask-verification\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7343D2RDXYZRRQWJKW15MHW","ask-text-writing","Text Writing: Writes emails, posts, articles, bios, READMEs, and docs that sound human and avoid AI writing patterns. Use when drafting or rewriting prose.","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002Fask-text-writing\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7343A980X77TDWV0FZAYBS2","ask-summary","Summary: Explains what changed and what is proven, walks through code, or re-pitches unclear output. Use when work is done or the user asks what changed.","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002Fask-summary\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M73438ARMNM8W991A7EPGRG1","ask-session-review","Session Review: Reflects on skill usage and gaps and files GitHub issues from bugs, findings, or follow-ups. Use after completing work.","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002Fask-session-review\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M734362MZYM4CT488AAFX84G","ask-research","Research: Does bounded fact-finding across the repository, docs, code, or external sources. Use when a question needs evidence before an answer or decision.","https:\u002F\u002Fgithub.com\u002FMarkBovee\u002Fagent-skills-kit\u002Fblob\u002Fmain\u002Fskills\u002Fask-research\u002FSKILL.md",[],[]]