[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CY26B72FRCVZF3Z2SFBQAY":3,"skill-same:01M6CY26B72FRCVZF3Z2SFBQAY":121},{"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":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":72,"ownerHtmlUrl":73,"ownerBlogUrl":74,"ownerDescription":75,"updatedAt":76,"install":77,"resources":90},"01M6CY26B72FRCVZF3Z2SFBQAY","vue-expert",null,"Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR\u002FSSG projects, sets up Pinia stores, scaffolds Quasar\u002FCapacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.","eric861129\u002FSKILLS_All-in-one","eric861129","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F74950944?v=4","01M6CXHDYEYRPFGGV4EFXCSYCF","ChiYu-Huang","01M6CXHE2J5CN1EBTY0FKV3ZKW",52,"MIT","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Fvue-expert\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"vue expert","expert","vue","Composition","worker","mobile","up","router","pwa","pinia","projects","frontend","api","tuning","code","ssr","config","components","typescript","writing","2026-11-10 10:12:30",false,"---\nname: vue-expert\ndescription: Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR\u002FSSG projects, sets up Pinia stores, scaffolds Quasar\u002FCapacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: frontend\n  triggers: Vue 3, Composition API, Nuxt, Pinia, Vue composables, reactive, ref, Vue Router, Vite Vue, Quasar, Capacitor, PWA, service worker, Fastify SSR, sourcemap, Vite config, build optimization\n  role: specialist\n  scope: implementation\n  output-format: code\n  related-skills: typescript-pro, fullstack-guardian\n---\n\n# Vue Expert\n\nSenior Vue specialist with deep expertise in Vue 3 Composition API, reactivity system, and modern Vue ecosystem.\n\n## Core Workflow\n\n1. **Analyze requirements** - Identify component hierarchy, state needs, routing\n2. **Design architecture** - Plan composables, stores, component structure\n3. **Implement** - Build components with Composition API and proper reactivity\n4. **Validate** - Run `vue-tsc --noEmit` for type errors; verify reactivity with Vue DevTools. If type errors are found: fix each issue and re-run `vue-tsc --noEmit` until the output is clean before proceeding\n5. **Optimize** - Minimize re-renders, optimize computed properties, lazy load\n6. **Test** - Write component tests with Vue Test Utils and Vitest. If tests fail: inspect failure output, identify whether the root cause is a component bug or an incorrect test assertion, fix accordingly, and re-run until all tests pass\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Composition API | `references\u002Fcomposition-api.md` | ref, reactive, computed, watch, lifecycle |\n| Components | `references\u002Fcomponents.md` | Props, emits, slots, provide\u002Finject |\n| State Management | `references\u002Fstate-management.md` | Pinia stores, actions, getters |\n| Nuxt 3 | `references\u002Fnuxt.md` | SSR, file-based routing, useFetch, Fastify, hydration |\n| TypeScript | `references\u002Ftypescript.md` | Typing props, generic components, type safety |\n| Mobile & Hybrid | `references\u002Fmobile-hybrid.md` | Quasar, Capacitor, PWA, service worker, mobile |\n| Build Tooling | `references\u002Fbuild-tooling.md` | Vite config, sourcemaps, optimization, bundling |\n\n## Quick Example\n\nMinimal component demonstrating preferred patterns:\n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport { ref, computed } from 'vue'\n\nconst props = defineProps\u003C{ initialCount?: number }>()\n\nconst count = ref(props.initialCount ?? 0)\nconst doubled = computed(() => count.value * 2)\n\nfunction increment() {\n  count.value++\n}\n\u003C\u002Fscript>\n\n\u003Ctemplate>\n  \u003Cbutton @click=\"increment\">Count: {{ count }} (doubled: {{ doubled }})\u003C\u002Fbutton>\n\u003C\u002Ftemplate>\n```\n\n## Constraints\n\n### MUST DO\n- Use Composition API (NOT Options API)\n- Use `\u003Cscript setup>` syntax for components\n- Use type-safe props with TypeScript\n- Use `ref()` for primitives, `reactive()` for objects\n- Use `computed()` for derived state\n- Use proper lifecycle hooks (onMounted, onUnmounted, etc.)\n- Implement proper cleanup in composables\n- Use Pinia for global state management\n\n### MUST NOT DO\n- Use Options API (data, methods, computed as object)\n- Mix Composition API with Options API\n- Mutate props directly\n- Create reactive objects unnecessarily\n- Use watch when computed is sufficient\n- Forget to cleanup watchers and effects\n- Access DOM before onMounted\n- Use Vuex (deprecated in favor of Pinia)\n\n## Output Templates\n\nWhen implementing Vue features, provide:\n1. Component file with `\u003Cscript setup>` and TypeScript\n2. Composable if reusable logic exists\n3. Pinia store if global state needed\n4. Brief explanation of reactivity decisions\n\n## Knowledge Reference\n\nVue 3 Composition API, Pinia, Nuxt 3, Vue Router 4, Vite, VueUse, TypeScript, Vitest, Vue Test Utils, SSR\u002FSSG, reactive programming, performance optimization\n","# Vue Expert\n\nSenior Vue specialist with deep expertise in Vue 3 Composition API, reactivity system, and modern Vue ecosystem.\n\n## Core Workflow\n\n1. **Analyze requirements** - Identify component hierarchy, state needs, routing\n2. **Design architecture** - Plan composables, stores, component structure\n3. **Implement** - Build components with Composition API and proper reactivity\n4. **Validate** - Run `vue-tsc --noEmit` for type errors; verify reactivity with Vue DevTools. If type errors are found: fix each issue and re-run `vue-tsc --noEmit` until the output is clean before proceeding\n5. **Optimize** - Minimize re-renders, optimize computed properties, lazy load\n6. **Test** - Write component tests with Vue Test Utils and Vitest. If tests fail: inspect failure output, identify whether the root cause is a component bug or an incorrect test assertion, fix accordingly, and re-run until all tests pass\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Composition API | `references\u002Fcomposition-api.md` | ref, reactive, computed, watch, lifecycle |\n| Components | `references\u002Fcomponents.md` | Props, emits, slots, provide\u002Finject |\n| State Management | `references\u002Fstate-management.md` | Pinia stores, actions, getters |\n| Nuxt 3 | `references\u002Fnuxt.md` | SSR, file-based routing, useFetch, Fastify, hydration |\n| TypeScript | `references\u002Ftypescript.md` | Typing props, generic components, type safety |\n| Mobile & Hybrid | `references\u002Fmobile-hybrid.md` | Quasar, Capacitor, PWA, service worker, mobile |\n| Build Tooling | `references\u002Fbuild-tooling.md` | Vite config, sourcemaps, optimization, bundling |\n\n## Quick Example\n\nMinimal component demonstrating preferred patterns:\n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport { ref, computed } from 'vue'\n\nconst props = defineProps\u003C{ initialCount?: number }>()\n\nconst count = ref(props.initialCount ?? 0)\nconst doubled = computed(() => count.value * 2)\n\nfunction increment() {\n  count.value++\n}\n\u003C\u002Fscript>\n\n\u003Ctemplate>\n  \u003Cbutton @click=\"increment\">Count: {{ count }} (doubled: {{ doubled }})\u003C\u002Fbutton>\n\u003C\u002Ftemplate>\n```\n\n## Constraints\n\n### MUST DO\n- Use Composition API (NOT Options API)\n- Use `\u003Cscript setup>` syntax for components\n- Use type-safe props with TypeScript\n- Use `ref()` for primitives, `reactive()` for objects\n- Use `computed()` for derived state\n- Use proper lifecycle hooks (onMounted, onUnmounted, etc.)\n- Implement proper cleanup in composables\n- Use Pinia for global state management\n\n### MUST NOT DO\n- Use Options API (data, methods, computed as object)\n- Mix Composition API with Options API\n- Mutate props directly\n- Create reactive objects unnecessarily\n- Use watch when computed is sufficient\n- Forget to cleanup watchers and effects\n- Access DOM before onMounted\n- Use Vuex (deprecated in favor of Pinia)\n\n## Output Templates\n\nWhen implementing Vue features, provide:\n1. Component file with `\u003Cscript setup>` and TypeScript\n2. Composable if reusable logic exists\n3. Pinia store if global state needed\n4. Brief explanation of reactivity decisions\n\n## Knowledge Reference\n\nVue 3 Composition API, Pinia, Nuxt 3, Vue Router 4, Vite, VueUse, TypeScript, Vitest, Vue Test Utils, SSR\u002FSSG, reactive programming, performance optimization\n",{"name":5,"license":15,"metadata":60,"description":7},{"role":61,"scope":62,"author":63,"domain":46,"version":64,"triggers":65,"output-format":49,"related-skills":66},"specialist","implementation","https:\u002F\u002Fgithub.com\u002FJeffallan","1.1.0","Vue 3, Composition API, Nuxt, Pinia, Vue composables, reactive, ref, Vue Router, Vite Vue, Quasar, Capacitor, PWA, service worker, Fastify SSR, sourcemap, Vite config, build optimization","typescript-pro, fullstack-guardian","main","cbdd44aae21131521c09e42762e36178c790eacf","public\u002FSKILLS\u002FDevelopment & Code Tools\u002Fvue-expert",13,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one","http:\u002F\u002Fhuangchiyu.com\u002FSKILLS_All-in-one\u002F","https:\u002F\u002Fgithub.com\u002Feric861129","https:\u002F\u002Fhuangchiyu.com\u002FChiYu-Blog\u002F","開發工程師，專注於 C#／.NET 系統現代化、AI-assisted engineering、開源工具與技術寫作。","2026-04-16 14:28:14",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add eric861129\u002FSKILLS_All-in-one --skill vue-expert",{"tool":83,"command":84},"bunx","bunx skills add eric861129\u002FSKILLS_All-in-one --skill vue-expert",{"tool":86,"command":87},"pnpm","pnpm dlx skills add eric861129\u002FSKILLS_All-in-one --skill vue-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Fvue-expert\u002FSKILL.md",true,[91,97,101,105,109,113,117],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fbuild-tooling.md","REFERENCE","参考文档",9632,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Fvue-expert\u002Freferences\u002Fbuild-tooling.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fcomponents.md",9039,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Fvue-expert\u002Freferences\u002Fcomponents.md",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fcomposition-api.md",5942,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Fvue-expert\u002Freferences\u002Fcomposition-api.md",{"path":106,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fmobile-hybrid.md",13867,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Fvue-expert\u002Freferences\u002Fmobile-hybrid.md",{"path":110,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fnuxt.md",14397,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Fvue-expert\u002Freferences\u002Fnuxt.md",{"path":114,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fstate-management.md",9850,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Fvue-expert\u002Freferences\u002Fstate-management.md",{"path":118,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Ftypescript.md",10944,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Fvue-expert\u002Freferences\u002Ftypescript.md",[122,150,181,205,229,249],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":129,"publishedAt":55},"01M6CZ1WR3KNVTKSWH4GNWT646","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fwhat-if-oracle\u002FSKILL.md",[128],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149],"oracle","what if oracle","go","run","planning","ux","futures","risk","analysis","explore","decision","branch","question","read","write","idea","exploration","options","stress-test","strategies",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":166,"publishedAt":55},"01M6CZ1QHGJE91A95MSN5EK5Q9","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fvenue-templates\u002FSKILL.md",[156,159,162,163],{"categoryNo":157,"categoryName":158,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":160,"categoryName":161,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":164,"categoryName":165,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者",[167,168,169,170,171,172,173,174,175,176,143,144,177,178,179,180],"templates","venue templates","research","guidelines","NeurIPS","ICML","LaTeX","science","Bash","access","edit","proposals","Academic","requirements",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":189,"publishedAt":55},"01M6CZ1KBQD2E5RTFB3BGVX7CD","the-fool","Use when challenging ideas, plans, decisions, or proposals using structured critical reasoning. Invoke to play devil's advocate, run a pre-mortem, red team, or audit evidence and assumptions.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fthe-fool\u002FSKILL.md",[187,188],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},[190,191,132,192,193,133,49,194,195,196,197,198,199,200,178,201,202,36,203,204],"the fool","review","workflow","architecture","audit","forge","devil","team","designer","reviewer","challenge","stress test","evidence","poke","ideas",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":214,"publishedAt":55},"01M6CZ1ES826S7P1X3333E40TA","scientific-writing","Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA\u002FAMA\u002FVancouver), figures\u002Ftables, reporting guidelines (CONSORT\u002FSTROBE\u002FPRISMA), for research papers and journal submissions.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fscientific-writing\u002FSKILL.md",[211,212,213],{"categoryNo":157,"categoryName":158,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":164,"categoryName":165,"taxonomyType":32,"taxonomyTypeDesc":33},[54,215,170,216,217,218,219,220,175,221,143,144,177,222,223,224,225,226,227,228],"scientific writing","core","reporting","deep research","Citations","Outlines","tool","use","never","structure","deep","full","stage","prisma",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":236,"publishedAt":55},"01M6CZ1B2JGJTB9FRD0TW4RXXE","scientific-brainstorming","Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fscientific-brainstorming\u002FSKILL.md",[235],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[237,238,169,239,134,240,241,242,222,243,244,245,146,246,247,227,248],"brainstorming","scientific brainstorming","sessions","data","hypothesis","open","ideation","creative","do","connections","research ideation","generation",{"skillNo":250,"name":251,"nameZh":6,"description":252,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":253,"categories":254,"keywords":259,"publishedAt":55},"01M6CZ16JG8N7A2ZX04BGE8J2Y","research-lookup","Look up current research information using the Parallel Chat API (primary) or Perplexity sonar-pro-search (academic paper searches). Automatically routes queries to the best backend. Use for finding papers, gathering research data, and verifying scientific information.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fresearch-lookup\u002FSKILL.md",[255,256,257,258],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":160,"categoryName":161,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},[169,260,261,262,240,263,47,175,264,265,143,144,177,222,266,41,267,268,269,179],"lookup","research lookup","search","perplexity","parallel","openrouter","backend","look","queries","chat"]