[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70H2WGYP2R7C5NBVKDZ2E9K":3,"skill-same:01M70H2WGYP2R7C5NBVKDZ2E9K":75},{"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":26,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M70H2WGYP2R7C5NBVKDZ2E9K","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.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fresearch-ops\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"research","research ops","ops","when","for","facts","recommendation","fresh","local","evidence","use","user","context","public","first","enrichment","state","research workflow","workflow","2026-11-10 10:12:30",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":51,"description":7},{"origin":52},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fresearch-ops",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill research-ops",{"tool":67,"command":68},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill research-ops",{"tool":70,"command":71},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill research-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fresearch-ops\u002FSKILL.md",true,[],[76,84,92,99,106,113],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":83},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":91},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":91},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":91},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":91},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":91},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]