[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78BYR4N3Q2ADFDY33A9P54P":3,"skill-same:01M78BYR4N3Q2ADFDY33A9P54P":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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M78BYR4N3Q2ADFDY33A9P54P","documentation-lookup",null,"Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fdocumentation-lookup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: documentation-lookup\ndescription: Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).\norigin: ECC\n---\n\n# Documentation Lookup (Context7)\n\nWhen the user asks about libraries, frameworks, or APIs, fetch current documentation via the Context7 MCP (tools `resolve-library-id` and `query-docs`) instead of relying on training data.\n\n## Core Concepts\n\n- **Context7**: MCP server that exposes live documentation; use it instead of training data for libraries and APIs.\n- **resolve-library-id**: Returns Context7-compatible library IDs (e.g. `\u002Fvercel\u002Fnext.js`) from a library name and query.\n- **query-docs**: Fetches documentation and code snippets for a given library ID and question. Always call resolve-library-id first to get a valid library ID.\n\n## When to use\n\nActivate when the user:\n\n- Asks setup or configuration questions (e.g. \"How do I configure Next.js middleware?\")\n- Requests code that depends on a library (\"Write a Prisma query for...\")\n- Needs API or reference information (\"What are the Supabase auth methods?\")\n- Mentions specific frameworks or libraries (React, Vue, Svelte, Express, Tailwind, Prisma, Supabase, etc.)\n\nUse this skill whenever the request depends on accurate, up-to-date behavior of a library, framework, or API. Applies across harnesses that have the Context7 MCP configured (e.g. Claude Code, Cursor, Codex).\n\n## How it works\n\n### Step 1: Resolve the Library ID\n\nCall the **resolve-library-id** MCP tool with:\n\n- **libraryName**: The library or product name taken from the user's question (e.g. `Next.js`, `Prisma`, `Supabase`).\n- **query**: The user's full question. This improves relevance ranking of results.\n\nYou must obtain a Context7-compatible library ID (format `\u002Forg\u002Fproject` or `\u002Forg\u002Fproject\u002Fversion`) before querying docs. Do not call query-docs without a valid library ID from this step.\n\n### Step 2: Select the Best Match\n\nFrom the resolution results, choose one result using:\n\n- **Name match**: Prefer exact or closest match to what the user asked for.\n- **Benchmark score**: Higher scores indicate better documentation quality (100 is highest).\n- **Source reputation**: Prefer High or Medium reputation when available.\n- **Version**: If the user specified a version (e.g. \"React 19\", \"Next.js 15\"), prefer a version-specific library ID if listed (e.g. `\u002Forg\u002Fproject\u002Fv1.2.0`).\n\n### Step 3: Fetch the Documentation\n\nCall the **query-docs** MCP tool with:\n\n- **libraryId**: The selected Context7 library ID from Step 2 (e.g. `\u002Fvercel\u002Fnext.js`).\n- **query**: The user's specific question or task. Be specific to get relevant snippets.\n\nLimit: do not call query-docs (or resolve-library-id) more than 3 times per question. If the answer is unclear after 3 calls, state the uncertainty and use the best information you have rather than guessing.\n\n### Step 4: Use the Documentation\n\n- Answer the user's question using the fetched, current information.\n- Include relevant code examples from the docs when helpful.\n- Cite the library or version when it matters (e.g. \"In Next.js 15...\").\n\n## Examples\n\n### Example: Next.js middleware\n\n1. Call **resolve-library-id** with `libraryName: \"Next.js\"`, `query: \"How do I set up Next.js middleware?\"`.\n2. From results, pick the best match (e.g. `\u002Fvercel\u002Fnext.js`) by name and benchmark score.\n3. Call **query-docs** with `libraryId: \"\u002Fvercel\u002Fnext.js\"`, `query: \"How do I set up Next.js middleware?\"`.\n4. Use the returned snippets and text to answer; include a minimal `middleware.ts` example from the docs if relevant.\n\n### Example: Prisma query\n\n1. Call **resolve-library-id** with `libraryName: \"Prisma\"`, `query: \"How do I query with relations?\"`.\n2. Select the official Prisma library ID (e.g. `\u002Fprisma\u002Fprisma`).\n3. Call **query-docs** with that `libraryId` and the query.\n4. Return the Prisma Client pattern (e.g. `include` or `select`) with a short code snippet from the docs.\n\n### Example: Supabase auth methods\n\n1. Call **resolve-library-id** with `libraryName: \"Supabase\"`, `query: \"What are the auth methods?\"`.\n2. Pick the Supabase docs library ID.\n3. Call **query-docs**; summarize the auth methods and show minimal examples from the fetched docs.\n\n## Best Practices\n\n- **Be specific**: Use the user's full question as the query where possible for better relevance.\n- **Version awareness**: When users mention versions, use version-specific library IDs from the resolve step when available.\n- **Prefer official sources**: When multiple matches exist, prefer official or primary packages over community forks.\n- **No sensitive data**: Redact API keys, passwords, tokens, and other secrets from any query sent to Context7. Treat the user's question as potentially containing secrets before passing it to resolve-library-id or query-docs.\n","# Documentation Lookup (Context7)\n\nWhen the user asks about libraries, frameworks, or APIs, fetch current documentation via the Context7 MCP (tools `resolve-library-id` and `query-docs`) instead of relying on training data.\n\n## Core Concepts\n\n- **Context7**: MCP server that exposes live documentation; use it instead of training data for libraries and APIs.\n- **resolve-library-id**: Returns Context7-compatible library IDs (e.g. `\u002Fvercel\u002Fnext.js`) from a library name and query.\n- **query-docs**: Fetches documentation and code snippets for a given library ID and question. Always call resolve-library-id first to get a valid library ID.\n\n## When to use\n\nActivate when the user:\n\n- Asks setup or configuration questions (e.g. \"How do I configure Next.js middleware?\")\n- Requests code that depends on a library (\"Write a Prisma query for...\")\n- Needs API or reference information (\"What are the Supabase auth methods?\")\n- Mentions specific frameworks or libraries (React, Vue, Svelte, Express, Tailwind, Prisma, Supabase, etc.)\n\nUse this skill whenever the request depends on accurate, up-to-date behavior of a library, framework, or API. Applies across harnesses that have the Context7 MCP configured (e.g. Claude Code, Cursor, Codex).\n\n## How it works\n\n### Step 1: Resolve the Library ID\n\nCall the **resolve-library-id** MCP tool with:\n\n- **libraryName**: The library or product name taken from the user's question (e.g. `Next.js`, `Prisma`, `Supabase`).\n- **query**: The user's full question. This improves relevance ranking of results.\n\nYou must obtain a Context7-compatible library ID (format `\u002Forg\u002Fproject` or `\u002Forg\u002Fproject\u002Fversion`) before querying docs. Do not call query-docs without a valid library ID from this step.\n\n### Step 2: Select the Best Match\n\nFrom the resolution results, choose one result using:\n\n- **Name match**: Prefer exact or closest match to what the user asked for.\n- **Benchmark score**: Higher scores indicate better documentation quality (100 is highest).\n- **Source reputation**: Prefer High or Medium reputation when available.\n- **Version**: If the user specified a version (e.g. \"React 19\", \"Next.js 15\"), prefer a version-specific library ID if listed (e.g. `\u002Forg\u002Fproject\u002Fv1.2.0`).\n\n### Step 3: Fetch the Documentation\n\nCall the **query-docs** MCP tool with:\n\n- **libraryId**: The selected Context7 library ID from Step 2 (e.g. `\u002Fvercel\u002Fnext.js`).\n- **query**: The user's specific question or task. Be specific to get relevant snippets.\n\nLimit: do not call query-docs (or resolve-library-id) more than 3 times per question. If the answer is unclear after 3 calls, state the uncertainty and use the best information you have rather than guessing.\n\n### Step 4: Use the Documentation\n\n- Answer the user's question using the fetched, current information.\n- Include relevant code examples from the docs when helpful.\n- Cite the library or version when it matters (e.g. \"In Next.js 15...\").\n\n## Examples\n\n### Example: Next.js middleware\n\n1. Call **resolve-library-id** with `libraryName: \"Next.js\"`, `query: \"How do I set up Next.js middleware?\"`.\n2. From results, pick the best match (e.g. `\u002Fvercel\u002Fnext.js`) by name and benchmark score.\n3. Call **query-docs** with `libraryId: \"\u002Fvercel\u002Fnext.js\"`, `query: \"How do I set up Next.js middleware?\"`.\n4. Use the returned snippets and text to answer; include a minimal `middleware.ts` example from the docs if relevant.\n\n### Example: Prisma query\n\n1. Call **resolve-library-id** with `libraryName: \"Prisma\"`, `query: \"How do I query with relations?\"`.\n2. Select the official Prisma library ID (e.g. `\u002Fprisma\u002Fprisma`).\n3. Call **query-docs** with that `libraryId` and the query.\n4. Return the Prisma Client pattern (e.g. `include` or `select`) with a short code snippet from the docs.\n\n### Example: Supabase auth methods\n\n1. Call **resolve-library-id** with `libraryName: \"Supabase\"`, `query: \"What are the auth methods?\"`.\n2. Pick the Supabase docs library ID.\n3. Call **query-docs**; summarize the auth methods and show minimal examples from the fetched docs.\n\n## Best Practices\n\n- **Be specific**: Use the user's full question as the query where possible for better relevance.\n- **Version awareness**: When users mention versions, use version-specific library IDs from the resolve step when available.\n- **Prefer official sources**: When multiple matches exist, prefer official or primary packages over community forks.\n- **No sensitive data**: Redact API keys, passwords, tokens, and other secrets from any query sent to Context7. Treat the user's question as potentially containing secrets before passing it to resolve-library-id or query-docs.\n",{"name":5,"origin":24,"description":7},"ECC","master","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Fdocumentation-lookup","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill documentation-lookup",{"tool":38,"command":39},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill documentation-lookup",{"tool":41,"command":42},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill documentation-lookup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fdocumentation-lookup\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",273,"https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fdocumentation-lookup\u002Fagents\u002Fopenai.yaml",[53,60,67,74,81,88],{"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},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\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},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\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},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\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":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]