[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0T15QH4VR5RBWMNJ8P0DQ":3,"skill-same:01M7F0T15QH4VR5RBWMNJ8P0DQ":46},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7F0T15QH4VR5RBWMNJ8P0DQ","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.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fecc\u002Fresearch-ops\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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.\nmetadata:\n  origin: 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,"metadata":24,"description":7},{"origin":25},"ECC","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fecc\u002Fresearch-ops","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill research-ops",{"tool":38,"command":39},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill research-ops",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill research-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fecc\u002Fresearch-ops\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"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},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]