[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADMPWDBEVYY9S1KRB1Z4MC":3,"skill-same:01M6ADMPWDBEVYY9S1KRB1Z4MC":109},{"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":23,"publishedAt":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6ADMPWDBEVYY9S1KRB1Z4MC","deep-research",null,"Research a technical topic thoroughly by exploring the codebase and summarizing findings. Use when asked to investigate how something works, research an area of the codebase, trace a data flow, or understand a component in depth.","davila7\u002Fclaude-with-skills","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHY7XW1NT6J5EJ61Q42B",13,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-03-skill-calls-subagent\u002Fexamples\u002Fdeep-research\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26],"research","deep research","component","2026-11-10 10:12:30",false,"---\ntitle: \"deep-research\"\nname: deep-research\ndescription: Research a technical topic thoroughly by exploring the codebase and summarizing findings. Use when asked to investigate how something works, research an area of the codebase, trace a data flow, or understand a component in depth.\ncontext: fork\nagent: Explore\nargument-hint: [topic or question]\n---\n\nResearch the following topic thoroughly: $ARGUMENTS\n\n## Steps\n\n1. Identify the scope of the research. Parse the topic into concrete searchable terms: class names, function names, file name patterns, configuration keys, or framework-specific terms.\n\n2. Search broadly before reading deeply:\n   - Use Grep to search for the most distinctive identifiers (class names, function names, error strings)\n   - Use Glob to find files by name pattern (e.g., `*auth*`, `*middleware*`, `*.config.*`)\n   - Prioritize files that appear in multiple search results — they are likely central to the topic\n\n3. Read the most relevant files completely. Do not skim. Missing a detail in a critical file leads to incorrect conclusions.\n\n4. For key files, check recent git history to understand why things are the way they are:\n   ```\n   git log --oneline --follow -20 \u003Cfilepath>\n   ```\n   Read the most informative commit messages. If a commit message references a PR or issue number, note it.\n\n5. Follow import and dependency chains one level deep. If the main file imports from three other modules, read those modules too.\n\n6. Synthesize findings into a structured report with these sections:\n\n   **Overview**\n   What this system or component does, in two to four sentences. Write for someone who has never touched this codebase.\n\n   **Key files**\n   A table: file path | one-line description of its role. Include every file you read that was materially relevant.\n\n   **How it works**\n   The main flow, data structures, and key design decisions. Use concrete terms: function names, type names, config keys. Reference file paths and approximate line numbers for the most important details.\n\n   **Recent changes**\n   What changed in the last 20 commits in the relevant area, and why (based on commit messages and diff context).\n\n   **Open questions**\n   Anything that is unclear from the code alone and would benefit from asking a team member or reading documentation. Be specific.\n\n7. Be precise. If you are uncertain, say so. Do not infer things that are not in the code.\n","Research the following topic thoroughly: $ARGUMENTS\n\n## Steps\n\n1. Identify the scope of the research. Parse the topic into concrete searchable terms: class names, function names, file name patterns, configuration keys, or framework-specific terms.\n\n2. Search broadly before reading deeply:\n   - Use Grep to search for the most distinctive identifiers (class names, function names, error strings)\n   - Use Glob to find files by name pattern (e.g., `*auth*`, `*middleware*`, `*.config.*`)\n   - Prioritize files that appear in multiple search results — they are likely central to the topic\n\n3. Read the most relevant files completely. Do not skim. Missing a detail in a critical file leads to incorrect conclusions.\n\n4. For key files, check recent git history to understand why things are the way they are:\n   ```\n   git log --oneline --follow -20 \u003Cfilepath>\n   ```\n   Read the most informative commit messages. If a commit message references a PR or issue number, note it.\n\n5. Follow import and dependency chains one level deep. If the main file imports from three other modules, read those modules too.\n\n6. Synthesize findings into a structured report with these sections:\n\n   **Overview**\n   What this system or component does, in two to four sentences. Write for someone who has never touched this codebase.\n\n   **Key files**\n   A table: file path | one-line description of its role. Include every file you read that was materially relevant.\n\n   **How it works**\n   The main flow, data structures, and key design decisions. Use concrete terms: function names, type names, config keys. Reference file paths and approximate line numbers for the most important details.\n\n   **Recent changes**\n   What changed in the last 20 commits in the relevant area, and why (based on commit messages and diff context).\n\n   **Open questions**\n   Anything that is unclear from the code alone and would benefit from asking a team member or reading documentation. Be specific.\n\n7. Be precise. If you are uncertain, say so. Do not infer things that are not in the code.\n",{"name":5,"agent":32,"title":5,"context":33,"description":7,"argument-hint":34},"Explore","fork",[35],"topic or question","main","55e6468ba43345d07c8a68de983e58403db57c25","src\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-03-skill-calls-subagent\u002Fexamples\u002Fdeep-research",1,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills","https:\u002F\u002Fclaude-with-skills.vercel.app","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-05-15 21:54:25",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add davila7\u002Fclaude-with-skills --skill deep-research",{"tool":52,"command":53},"bunx","bunx skills add davila7\u002Fclaude-with-skills --skill deep-research",{"tool":55,"command":56},"pnpm","pnpm dlx skills add davila7\u002Fclaude-with-skills --skill deep-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-03-skill-calls-subagent\u002Fexamples\u002Fdeep-research\u002FSKILL.md",true,[60,66,70,74,78,82,86,90,94,97,101,105],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"agents\u002Fopenai.yaml","REFERENCE","参考文档",247,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagentic-qa\u002Fagents\u002Fopenai.yaml",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fjourneys.md",8414,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagentic-qa\u002Freferences\u002Fjourneys.md",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fparticipant.md",5506,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagentic-qa\u002Freferences\u002Fparticipant.md",{"path":75,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fprotocols\u002Fchat.md",7592,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagentic-qa\u002Freferences\u002Fprotocols\u002Fchat.md",{"path":79,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fprotocols\u002Fcreative.md",9318,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagentic-qa\u002Freferences\u002Fprotocols\u002Fcreative.md",{"path":83,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fprotocols\u002Ffirst-use.md",6874,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagentic-qa\u002Freferences\u002Fprotocols\u002Ffirst-use.md",{"path":87,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fprotocols\u002Flibrary.md",11225,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagentic-qa\u002Freferences\u002Fprotocols\u002Flibrary.md",{"path":91,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fprotocols\u002FREADME.md",6559,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagentic-qa\u002Freferences\u002Fprotocols\u002FREADME.md",{"path":95,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":96},"references\u002Fprotocols\u002Fworkflows.md","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagentic-qa\u002Freferences\u002Fprotocols\u002Fworkflows.md",{"path":98,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Freport.md",3050,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagentic-qa\u002Freferences\u002Freport.md",{"path":102,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fruntime.md",16378,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagentic-qa\u002Freferences\u002Fruntime.md",{"path":106,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fux-review.md",3994,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagentic-qa\u002Freferences\u002Fux-review.md",[110,126,137,143,151,161],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":27},"01M6ADNEC991ZW0GD2D4MY6NEP","tag-version","Bump the package version and create an annotated git tag. Accepts a semantic version number (1.2.0) or a bump type (patch, minor, major). Does not push — use the publish skill to push. Use as part of a release workflow.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-08-plugins-and-distribution\u002Fexamples\u002Frelease-plugin\u002Fskills\u002Ftag-version\u002FSKILL.md",[],[117,118,119,120,121,122,123,124,125],"tag version","workflow","create","release","git","push","npm","package","publish",{"skillNo":127,"name":120,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":27},"01M6ADNCNHCXNHVAW43ZV43ZC8","Run the complete release workflow: changelog entry, version bump, git tag, and GitHub release. Invokes changelog-entry, tag-version, and publish in sequence. Use when releasing a new version of the project.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-08-plugins-and-distribution\u002Fexamples\u002Frelease-plugin\u002Fskills\u002Frelease\u002FSKILL.md",[],[120,121,132,123,133,134,125,135,136,118],"changelog","changelog entry","run","status","github",{"skillNo":138,"name":125,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":27},"01M6ADNAWDDDDX4CS69E1D496X","Push the current branch and all tags to origin, then create a GitHub release using the latest tag and its CHANGELOG.md entry. Use after tag-version to complete a release.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-08-plugins-and-distribution\u002Fexamples\u002Frelease-plugin\u002Fskills\u002Fpublish\u002FSKILL.md",[],[125,122,136,119,120,121,132],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":27},"01M6ADN9MP0ASQ6SX14NEPP5XE","changelog-entry","Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-08-plugins-and-distribution\u002Fexamples\u002Frelease-plugin\u002Fskills\u002Fchangelog-entry\u002FSKILL.md",[],[133,132,150,121],"security",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":27},"01M6ADN8243TD9X8FH7FCQ608R","auto-format-on-edit","Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-07-hooks-in-skills\u002Fexamples\u002Fauto-format-on-edit\u002FSKILL.md",[],[158,159,160],"auto format on edit","code","file",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":172,"publishedAt":27},"01M6ADN5VVNV7Y2WPYQA13M4ZQ","code-quality-audit","Run a comprehensive code quality audit covering security, performance, and maintainability. Use for quarterly audits, pre-release reviews, or when onboarding to a large codebase.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-with-skills\u002Fblob\u002Fmain\u002Fsrc\u002Fcontent\u002Fdocs\u002F03-advanced\u002Flesson-06-context-window-mastery\u002Fexamples\u002Flightweight-orchestrator\u002FSKILL.md",[167],{"categoryNo":168,"categoryName":169,"taxonomyType":170,"taxonomyTypeDesc":171},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[173,174,159,175,176,134,120,177,150],"code quality audit","audit","code quality","performance","onboarding"]