[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75D7P45AFECDAC6YJMBEH78":3,"skill-same:01M75D7P45AFECDAC6YJMBEH78":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75D7P45AFECDAC6YJMBEH78","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).","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fdocumentation-lookup\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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":23,"description":7},"ECC","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fdocumentation-lookup",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add agisota\u002Fold-one --skill documentation-lookup",{"tool":39,"command":40},"bunx","bunx skills add agisota\u002Fold-one --skill documentation-lookup",{"tool":42,"command":43},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill documentation-lookup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fdocumentation-lookup\u002FSKILL.md",true,[],[48,55,62,71,78,85],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","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\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]