[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YVNRBD4CNNWA4913M87RA":3,"skill-same:01M72YVNRBD4CNNWA4913M87RA":48},{"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":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M72YVNRBD4CNNWA4913M87RA","research-ops",null,"Evidence-first current-state research workflow for ECC. Use when the user wants fresh facts, comparisons, enrichment, or a recommendation built from current public evidence and any supplied local context.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Feverything-claude-code\u002Fskills\u002Fresearch-ops\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: research-ops\ndescription: Evidence-first current-state research workflow for ECC. Use when the user wants fresh facts, comparisons, enrichment, or a recommendation built from current public evidence and any supplied local context.\norigin: ECC\n---\n\n# Research Ops\n\nUse this when the user asks to research something current, compare options, enrich people or companies, or turn repeated lookups into a monitored workflow.\n\nThis is the operator wrapper around the repo's research stack. It is not a replacement for `deep-research`, `exa-search`, or `market-research`; it tells you when and how to use them together.\n\n## Skill Stack\n\nPull these ECC-native skills into the workflow when relevant:\n\n- `exa-search` for fast current-web discovery\n- `deep-research` for multi-source synthesis with citations\n- `market-research` when the end result should be a recommendation or ranked decision\n- `lead-intelligence` when the task is people\u002Fcompany targeting instead of generic research\n- `knowledge-ops` when the result should be stored in durable context afterward\n\n## When to Use\n\n- user says \"research\", \"look up\", \"compare\", \"who should I talk to\", or \"what's the latest\"\n- the answer depends on current public information\n- the user already supplied evidence and wants it factored into a fresh recommendation\n- the task may be recurring enough that it should become a monitor instead of a one-off lookup\n\n## Guardrails\n\n- do not answer current questions from stale memory when fresh search is cheap\n- separate:\n  - sourced fact\n  - user-provided evidence\n  - inference\n  - recommendation\n- do not spin up a heavyweight research pass if the answer is already in local code or docs\n\n## Workflow\n\n### 1. Start from what the user already gave you\n\nNormalize any supplied material into:\n\n- already-evidenced facts\n- needs verification\n- open questions\n\nDo not restart the analysis from zero if the user already built part of the model.\n\n### 2. Classify the ask\n\nChoose the right lane before searching:\n\n- quick factual answer\n- comparison or decision memo\n- lead\u002Fenrichment pass\n- recurring monitoring candidate\n\n### 3. Take the lightest useful evidence path first\n\n- use `exa-search` for fast discovery\n- escalate to `deep-research` when synthesis or multiple sources matter\n- use `market-research` when the outcome should end in a recommendation\n- hand off to `lead-intelligence` when the real ask is target ranking or warm-path discovery\n\n### 4. Report with explicit evidence boundaries\n\nFor important claims, say whether they are:\n\n- sourced facts\n- user-supplied context\n- inference\n- recommendation\n\nFreshness-sensitive answers should include concrete dates.\n\n### 5. Decide whether the task should stay manual\n\nIf the user is likely to ask the same research question repeatedly, say so explicitly and recommend a monitoring or workflow layer instead of repeating the same manual search forever.\n\n## Output Format\n\n```text\nQUESTION TYPE\n- factual \u002F comparison \u002F enrichment \u002F monitoring\n\nEVIDENCE\n- sourced facts\n- user-provided context\n\nINFERENCE\n- what follows from the evidence\n\nRECOMMENDATION\n- answer or next move\n- whether this should become a monitor\n```\n\n## Pitfalls\n\n- do not mix inference into sourced facts without labeling it\n- do not ignore user-provided evidence\n- do not use a heavy research lane for a question local repo context can answer\n- do not give freshness-sensitive answers without dates\n\n## Verification\n\n- important claims are labeled by evidence type\n- freshness-sensitive outputs include dates\n- the final recommendation matches the actual research mode used\n","# Research Ops\n\nUse this when the user asks to research something current, compare options, enrich people or companies, or turn repeated lookups into a monitored workflow.\n\nThis is the operator wrapper around the repo's research stack. It is not a replacement for `deep-research`, `exa-search`, or `market-research`; it tells you when and how to use them together.\n\n## Skill Stack\n\nPull these ECC-native skills into the workflow when relevant:\n\n- `exa-search` for fast current-web discovery\n- `deep-research` for multi-source synthesis with citations\n- `market-research` when the end result should be a recommendation or ranked decision\n- `lead-intelligence` when the task is people\u002Fcompany targeting instead of generic research\n- `knowledge-ops` when the result should be stored in durable context afterward\n\n## When to Use\n\n- user says \"research\", \"look up\", \"compare\", \"who should I talk to\", or \"what's the latest\"\n- the answer depends on current public information\n- the user already supplied evidence and wants it factored into a fresh recommendation\n- the task may be recurring enough that it should become a monitor instead of a one-off lookup\n\n## Guardrails\n\n- do not answer current questions from stale memory when fresh search is cheap\n- separate:\n  - sourced fact\n  - user-provided evidence\n  - inference\n  - recommendation\n- do not spin up a heavyweight research pass if the answer is already in local code or docs\n\n## Workflow\n\n### 1. Start from what the user already gave you\n\nNormalize any supplied material into:\n\n- already-evidenced facts\n- needs verification\n- open questions\n\nDo not restart the analysis from zero if the user already built part of the model.\n\n### 2. Classify the ask\n\nChoose the right lane before searching:\n\n- quick factual answer\n- comparison or decision memo\n- lead\u002Fenrichment pass\n- recurring monitoring candidate\n\n### 3. Take the lightest useful evidence path first\n\n- use `exa-search` for fast discovery\n- escalate to `deep-research` when synthesis or multiple sources matter\n- use `market-research` when the outcome should end in a recommendation\n- hand off to `lead-intelligence` when the real ask is target ranking or warm-path discovery\n\n### 4. Report with explicit evidence boundaries\n\nFor important claims, say whether they are:\n\n- sourced facts\n- user-supplied context\n- inference\n- recommendation\n\nFreshness-sensitive answers should include concrete dates.\n\n### 5. Decide whether the task should stay manual\n\nIf the user is likely to ask the same research question repeatedly, say so explicitly and recommend a monitoring or workflow layer instead of repeating the same manual search forever.\n\n## Output Format\n\n```text\nQUESTION TYPE\n- factual \u002F comparison \u002F enrichment \u002F monitoring\n\nEVIDENCE\n- sourced facts\n- user-provided context\n\nINFERENCE\n- what follows from the evidence\n\nRECOMMENDATION\n- answer or next move\n- whether this should become a monitor\n```\n\n## Pitfalls\n\n- do not mix inference into sourced facts without labeling it\n- do not ignore user-provided evidence\n- do not use a heavy research lane for a question local repo context can answer\n- do not give freshness-sensitive answers without dates\n\n## Verification\n\n- important claims are labeled by evidence type\n- freshness-sensitive outputs include dates\n- the final recommendation matches the actual research mode used\n",{"name":5,"origin":24,"description":7},"ECC","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","everything-claude-code\u002Fskills\u002Fresearch-ops",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SriramGandhiS\u002FSkills --skill research-ops",{"tool":40,"command":41},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill research-ops",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill research-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Feverything-claude-code\u002Fskills\u002Fresearch-ops\u002FSKILL.md",true,[],[49,56,61,67,74,81],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":6,"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},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\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},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\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},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\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},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]