[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75VT3K33SMM9Q9HSVXJ6S7R":3,"skill-same:01M75VT3K33SMM9Q9HSVXJ6S7R":44},{"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":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":27,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M75VT3K33SMM9Q9HSVXJ6S7R","optimized-research",null,"Research routing for Shuttle apps: decompose questions, assign fast\u002Fmedium\u002Fdeep depth, route to Parallel\u002FTavily MCP or better primary sources, cite every claim. Load before any domain skill that performs external research.","Domount\u002Fshuttle","Domount","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F294621842?v=4","01M75VS8XJK5XRR2M9D37FTYDT","01M75VS8Y7510RFRYSZNP4NQMW",0,"MIT","https:\u002F\u002Fgithub.com\u002FDomount\u002Fshuttle\u002Fblob\u002Fmaster\u002Ftemplates\u002Fdefault-app\u002Fskills\u002Foptimized-research\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: optimized-research\ndescription: >-\n  Research routing for Shuttle apps: decompose questions, assign fast\u002Fmedium\u002Fdeep\n  depth, route to Parallel\u002FTavily MCP or better primary sources, cite every claim.\n  Load before any domain skill that performs external research.\n---\n\n# Optimized Research\n\nProject skill: `skills\u002Foptimized-research\u002F`. **Do not** store or look for this under `~\u002F.cursor\u002Fskills-cursor\u002F` — that path is Cursor-managed and not durable.\n\nUse **Cursor MCP only** — no CLI installs, no curl to MCP endpoints.\n\n## Prerequisites\n\nConfirm these MCP servers are enabled (names may vary per workspace):\n\n| Server | Tools | Role |\n|--------|-------|------|\n| Parallel Search MCP | `web_search`, `web_fetch` | Fast lookup, fact-check, official pages |\n| Tavily | `tavily_search`, `tavily_research`, `tavily_extract` | Medium search, deep synthesis |\n\nRead tool schemas from the project's `mcps\u002F` folder before calling.\n\n**User override:** If the user asks to use only Parallel, only Tavily, or a specific tool\u002Fmethod, skip the routing below and follow their instruction.\n\n**Beyond these two tools:** Any other research method — direct fetch of primary sources, public APIs, local `data\u002F` files, other available MCPs — is allowed when it is clearly more valid, cheaper, or easier than the defaults. State the reasoning in one line when deviating.\n\n## Workflow\n\n### 1. Clarify scope\n\n- What questions must be answered?\n- Any local files or ground-truth data to reconcile against?\n- **Output format:** If the user already specified (JSON schema, markdown report, website, etc.), use that. Otherwise **ask once** how they want results delivered before researching.\n\n### 2. Decompose\n\nSplit the job into atomic sub-questions. For each, assign a depth:\n\n| Depth | When | Tool |\n|-------|------|------|\n| **Fast** | Single fact, current number, \"does X match Y?\", one official stat | Parallel `web_search`; `web_fetch` if excerpts are thin and URL is known |\n| **Medium** | A few related facts, light comparison, recent news | Parallel `web_search` (batch queries in one call) or Tavily `tavily_search` |\n| **Deep** | Multi-domain synthesis, narrative report, strategies, broad explainers | Tavily `tavily_research` (`pro` for broad topics) |\n\nRun independent legs in parallel where possible.\n\n### 3. Execute\n\n- Prefer **Tier 1 sources** when verifying facts: official agencies, primary documentation, authoritative data publishers.\n- Cross-check numbers against user-supplied or parsed local data when present.\n- Cite every factual claim with a URL from tool results.\n- Do not invent statistics.\n\n### 4. Synthesize\n\nMerge sub-results into the user's requested output format. Note disagreements between sources or tools when they matter.\n\n## Routing heuristics\n\n**Parallel wins when:** speed matters, you need a specific official page\u002Ftable, fact-checking a few figures, or fetching a known URL.\n\n**Tavily wins when:** one prompt should produce a cohesive long-form answer, multi-angle comparison, or actionable narrative across domains.\n\n**Default for mixed jobs:** Parallel for verification legs, Tavily for synthesis legs — don't run Tavily deep research for a question Parallel can answer in one search.\n\n## What not to do\n\n- Do not install CLIs or use bash wrappers when MCP tools are available.\n- Do not use one deep research call for the entire job if most sub-questions are simple lookups.\n- Do not assume output structure — ask if unspecified.\n\n## Downstream skills\n\nDomain-specific scope lives in your project's `skills\u002F\u003Cname>\u002F` files. **Load this skill first**; then the scoped skill for the task (e.g. `skills\u002Fresearch-task\u002F`, `skills\u002Fcontacts-research\u002F`).\n\nRecord depth choices per leg in `runMeta` on agent-written artifacts.\n","# Optimized Research\n\nProject skill: `skills\u002Foptimized-research\u002F`. **Do not** store or look for this under `~\u002F.cursor\u002Fskills-cursor\u002F` — that path is Cursor-managed and not durable.\n\nUse **Cursor MCP only** — no CLI installs, no curl to MCP endpoints.\n\n## Prerequisites\n\nConfirm these MCP servers are enabled (names may vary per workspace):\n\n| Server | Tools | Role |\n|--------|-------|------|\n| Parallel Search MCP | `web_search`, `web_fetch` | Fast lookup, fact-check, official pages |\n| Tavily | `tavily_search`, `tavily_research`, `tavily_extract` | Medium search, deep synthesis |\n\nRead tool schemas from the project's `mcps\u002F` folder before calling.\n\n**User override:** If the user asks to use only Parallel, only Tavily, or a specific tool\u002Fmethod, skip the routing below and follow their instruction.\n\n**Beyond these two tools:** Any other research method — direct fetch of primary sources, public APIs, local `data\u002F` files, other available MCPs — is allowed when it is clearly more valid, cheaper, or easier than the defaults. State the reasoning in one line when deviating.\n\n## Workflow\n\n### 1. Clarify scope\n\n- What questions must be answered?\n- Any local files or ground-truth data to reconcile against?\n- **Output format:** If the user already specified (JSON schema, markdown report, website, etc.), use that. Otherwise **ask once** how they want results delivered before researching.\n\n### 2. Decompose\n\nSplit the job into atomic sub-questions. For each, assign a depth:\n\n| Depth | When | Tool |\n|-------|------|------|\n| **Fast** | Single fact, current number, \"does X match Y?\", one official stat | Parallel `web_search`; `web_fetch` if excerpts are thin and URL is known |\n| **Medium** | A few related facts, light comparison, recent news | Parallel `web_search` (batch queries in one call) or Tavily `tavily_search` |\n| **Deep** | Multi-domain synthesis, narrative report, strategies, broad explainers | Tavily `tavily_research` (`pro` for broad topics) |\n\nRun independent legs in parallel where possible.\n\n### 3. Execute\n\n- Prefer **Tier 1 sources** when verifying facts: official agencies, primary documentation, authoritative data publishers.\n- Cross-check numbers against user-supplied or parsed local data when present.\n- Cite every factual claim with a URL from tool results.\n- Do not invent statistics.\n\n### 4. Synthesize\n\nMerge sub-results into the user's requested output format. Note disagreements between sources or tools when they matter.\n\n## Routing heuristics\n\n**Parallel wins when:** speed matters, you need a specific official page\u002Ftable, fact-checking a few figures, or fetching a known URL.\n\n**Tavily wins when:** one prompt should produce a cohesive long-form answer, multi-angle comparison, or actionable narrative across domains.\n\n**Default for mixed jobs:** Parallel for verification legs, Tavily for synthesis legs — don't run Tavily deep research for a question Parallel can answer in one search.\n\n## What not to do\n\n- Do not install CLIs or use bash wrappers when MCP tools are available.\n- Do not use one deep research call for the entire job if most sub-questions are simple lookups.\n- Do not assume output structure — ask if unspecified.\n\n## Downstream skills\n\nDomain-specific scope lives in your project's `skills\u002F\u003Cname>\u002F` files. **Load this skill first**; then the scoped skill for the task (e.g. `skills\u002Fresearch-task\u002F`, `skills\u002Fcontacts-research\u002F`).\n\nRecord depth choices per leg in `runMeta` on agent-written artifacts.\n",{"name":5,"description":7},"master","93887aaa963645c678f7c3812ccab7a126789752","templates\u002Fdefault-app\u002Fskills\u002Foptimized-research","https:\u002F\u002Fgithub.com\u002FDomount\u002Fshuttle","https:\u002F\u002Fdomount.github.io\u002Fshuttle\u002F","https:\u002F\u002Fgithub.com\u002FDomount","2026-11-12 14:37:59",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Domount\u002Fshuttle --skill optimized-research",{"tool":36,"command":37},"bunx","bunx skills add Domount\u002Fshuttle --skill optimized-research",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Domount\u002Fshuttle --skill optimized-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDomount\u002Fshuttle\u002Fblob\u002Fmaster\u002Ftemplates\u002Fdefault-app\u002Fskills\u002Foptimized-research\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M75VT24Z5BG9Y4GW1690W4KR","change-verification","Mandatory post-change gate for Shuttle apps. Run npm run verify before marking coding tasks done.","https:\u002F\u002Fgithub.com\u002FDomount\u002Fshuttle\u002Fblob\u002Fmaster\u002Ftemplates\u002Fdefault-app\u002Fskills\u002Fchange-verification\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M75VSZZHPSM2AYDTQ1KCZC0N","_template","Template for new domain skills. Copy to skills\u002F\u003Cname>\u002FSKILL.md.","https:\u002F\u002Fgithub.com\u002FDomount\u002Fshuttle\u002Fblob\u002Fmaster\u002Ftemplates\u002Fdefault-app\u002Fskills\u002F_template\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M75VSXM6771F4C3D1K081G6V","scaffold-feature","Scaffold a new web feature page with npm run scaffold:feature -- Name","https:\u002F\u002Fgithub.com\u002FDomount\u002Fshuttle\u002Fblob\u002Fmaster\u002Ftemplates\u002Fdefault-app\u002F.cursor\u002Fskills\u002Fscaffold-feature\u002FSKILL.md",[],[],{"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":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75VSTZ7Z76SEJTCA0RF2SAE","scaffold-api","Scaffold server API routes and service with npm run scaffold:api -- Name","https:\u002F\u002Fgithub.com\u002FDomount\u002Fshuttle\u002Fblob\u002Fmaster\u002Ftemplates\u002Fdefault-app\u002F.cursor\u002Fskills\u002Fscaffold-api\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75VSQA8PVXJGBXMH07FNT7Q","research-task","Simple research workflow for hello-agent example — write a note JSON file.","https:\u002F\u002Fgithub.com\u002FDomount\u002Fshuttle\u002Fblob\u002Fmaster\u002Fexamples\u002Fhello-agent\u002Fskills\u002Fresearch-task\u002FSKILL.md",[],[],{"skillNo":81,"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":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75VSM376PWB5FQAK7WF6PPK","https:\u002F\u002Fgithub.com\u002FDomount\u002Fshuttle\u002Fblob\u002Fmaster\u002Fexamples\u002Fhello-agent\u002Fskills\u002Foptimized-research\u002FSKILL.md",[],[]]