[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2YHSZ5QH0SCEBX5AGSWGC":3,"skill-same:01M7B2YHSZ5QH0SCEBX5AGSWGC":50},{"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":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7B2YHSZ5QH0SCEBX5AGSWGC","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.","lytong760-cell\u002Fcompiler_ko","lytong760-cell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F289977458?v=4","01M7B1YD239K88PFQRD4PVC9DW","Nguyên Games","01M7B1YD2RM70TZ71QNQ0XTN4R",2,"MIT","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fresearch-ops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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","c32dc0b68600587f78aff3310f3bbd4212173ab3",".kilo\u002Fskills\u002Fresearch-ops",1,"https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko","https:\u002F\u002Fko-lang.ai.studio","https:\u002F\u002Fgithub.com\u002Flytong760-cell","hanaminikata.com","hello ","2026-11-05 18:26:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lytong760-cell\u002Fcompiler_ko --skill research-ops",{"tool":42,"command":43},"bunx","bunx skills add lytong760-cell\u002Fcompiler_ko --skill research-ops",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lytong760-cell\u002Fcompiler_ko --skill research-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fresearch-ops\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7B36K22Z7155PTGEGTSDNJ4","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\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fx-api\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7B36HCAE9ESGBVS6J0FR52F","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7B36DYH4ZFJ3GZHPAEMVQAY","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7B36A1QXMEZT8VZMFVQNR5E","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7B364EK3N88VQQJ6HFATJQE","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwindows-desktop-e2e\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7B360YF7GGNAF21KT4QB5PG","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]