[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASGZTW3G55QZ45ERXM3F1R":3,"skill-same:01M7ASGZTW3G55QZ45ERXM3F1R":52},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7ASGZTW3G55QZ45ERXM3F1R","documentation-lookup",null,"Use current library and framework docs through Context7, preferring MCP tools with the CLI as a fallback. Activates for setup questions, API references, code examples, or named frameworks such as React, Next.js, or Prisma.","saski\u002Farnesto","saski","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F140356?v=4","01M7ASBDSNXTRYDYB4K1PEA1RV","01M7ASBDTAKBDAAV99S1GE7HK6",6,"Unlicense","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdocumentation-lookup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: documentation-lookup\ndescription: Use current library and framework docs through Context7, preferring MCP tools with the CLI as a fallback. Activates for setup questions, API references, code examples, or named frameworks such as React, Next.js, or Prisma.\norigin: ECC\n---\n\n# Documentation Lookup (Context7)\n\nWhen a request depends on current library, framework, SDK, API, CLI, or cloud-service behavior, fetch current documentation through Context7 instead of relying on training data.\n\n## When to Use\n\nActivate when the user:\n\n- Asks setup or configuration questions.\n- Requests code that depends on a library.\n- Needs API or reference information.\n- Names a framework, SDK, CLI, or cloud service whose behavior may have changed.\n\nDo not use Context7 for refactoring, business-logic debugging, code review, scripts written from scratch, or general programming concepts that do not depend on current external documentation.\n\n## Workflow\n\n### Step 1: Choose the Transport\n\nPrefer the Context7 MCP tools when they are available. Use the CLI only when the current harness does not expose the MCP tools.\n\nUse no more than three Context7 resolution or documentation calls per question, regardless of transport.\n\n### Step 2: Resolve the Library ID\n\nIf the user did not provide a valid `\u002Forg\u002Fproject` or `\u002Forg\u002Fproject\u002Fversion` ID:\n\n- **MCP:** Call `resolve-library-id` with the official library name and the user's full question.\n- **CLI fallback:** Run `npx ctx7@latest library \u003Cname> \"\u003Cuser's question>\"`.\n\nDo not send API keys, passwords, credentials, or other secrets in the query.\n\n### Step 3: Select the Best Match\n\nChoose one result using:\n\n- Exact or closest official name match.\n- Description relevance to the user's question.\n- High or Medium source reputation when available.\n- Higher benchmark score and useful snippet coverage.\n- A version-specific ID when the user specified a version.\n\n### Step 4: Fetch the Documentation\n\n- **MCP:** Call `query-docs` with the selected library ID and the user's specific question.\n- **CLI fallback:** Run `npx ctx7@latest docs \u003ClibraryId> \"\u003Cuser's question>\"`.\n\nIf a CLI request fails with a quota error, tell the user and suggest `npx ctx7@latest login` or `CONTEXT7_API_KEY`. If the answer remains unclear after the call limit, state the uncertainty instead of guessing.\n\n### Step 5: Use the Documentation\n\n- Answer from the fetched documentation.\n- Include minimal code examples when useful.\n- Cite the library and version when it matters.\n- Keep one transport for the question unless it is unavailable or fails.\n","# Documentation Lookup (Context7)\n\nWhen a request depends on current library, framework, SDK, API, CLI, or cloud-service behavior, fetch current documentation through Context7 instead of relying on training data.\n\n## When to Use\n\nActivate when the user:\n\n- Asks setup or configuration questions.\n- Requests code that depends on a library.\n- Needs API or reference information.\n- Names a framework, SDK, CLI, or cloud service whose behavior may have changed.\n\nDo not use Context7 for refactoring, business-logic debugging, code review, scripts written from scratch, or general programming concepts that do not depend on current external documentation.\n\n## Workflow\n\n### Step 1: Choose the Transport\n\nPrefer the Context7 MCP tools when they are available. Use the CLI only when the current harness does not expose the MCP tools.\n\nUse no more than three Context7 resolution or documentation calls per question, regardless of transport.\n\n### Step 2: Resolve the Library ID\n\nIf the user did not provide a valid `\u002Forg\u002Fproject` or `\u002Forg\u002Fproject\u002Fversion` ID:\n\n- **MCP:** Call `resolve-library-id` with the official library name and the user's full question.\n- **CLI fallback:** Run `npx ctx7@latest library \u003Cname> \"\u003Cuser's question>\"`.\n\nDo not send API keys, passwords, credentials, or other secrets in the query.\n\n### Step 3: Select the Best Match\n\nChoose one result using:\n\n- Exact or closest official name match.\n- Description relevance to the user's question.\n- High or Medium source reputation when available.\n- Higher benchmark score and useful snippet coverage.\n- A version-specific ID when the user specified a version.\n\n### Step 4: Fetch the Documentation\n\n- **MCP:** Call `query-docs` with the selected library ID and the user's specific question.\n- **CLI fallback:** Run `npx ctx7@latest docs \u003ClibraryId> \"\u003Cuser's question>\"`.\n\nIf a CLI request fails with a quota error, tell the user and suggest `npx ctx7@latest login` or `CONTEXT7_API_KEY`. If the answer remains unclear after the call limit, state the uncertainty instead of guessing.\n\n### Step 5: Use the Documentation\n\n- Answer from the fetched documentation.\n- Include minimal code examples when useful.\n- Cite the library and version when it matters.\n- Keep one transport for the question unless it is unavailable or fails.\n",{"name":5,"origin":23,"description":7},"ECC","main","3c24fc2c035029b08c7326774bee3fef8fb95566",".agents\u002Fskills\u002Fdocumentation-lookup",0,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto","https:\u002F\u002Fgithub.com\u002Fsaski","http:\u002F\u002Fsaski.com","2026-11-12 20:09:16",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add saski\u002Farnesto --skill documentation-lookup",{"tool":38,"command":39},"bunx","bunx skills add saski\u002Farnesto --skill documentation-lookup",{"tool":41,"command":42},"pnpm","pnpm dlx skills add saski\u002Farnesto --skill documentation-lookup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdocumentation-lookup\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",241,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\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":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7AT7F5FSHNAMFMF01N0QA1X","visualize","Use \u002Fvisualize for creating compact charts, diagrams, or other visuals inline as part of the conversation itself. It chooses among Markdown tables, Mermaid, inline HTML, and other supported in-transcript forms. Use Canvas for durable artifacts outside the transcript that users may revisit, refine, or share.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fvisualize\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7AT79MHSAR3JDDMP7DGERM9","update-cursor-settings","Modify Cursor\u002FVSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cursor-settings\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7AT73WF3Y22E0FKYAMCCJES","update-cli-config","View and modify Cursor CLI configuration settings in ~\u002F.cursor\u002Fcli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cli-config\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7AT6F3FBP85AJJ5BJNR8B5W","statusline","Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fstatusline\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7AT6D24QFS5XRAFN8S5XJ7W","split-to-prs","Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fsplit-to-prs\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M7AT69FYFN84XZKW452JV5DF","shell","Runs the rest of a \u002Fshell request as a literal shell command. Use only when the user explicitly invokes \u002Fshell and wants the following text executed directly in the terminal.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fshell\u002FSKILL.md",[],[]]