[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CXYPCS7PEN96NRF60TFH5S":3,"skill-same:01M6CXYPCS7PEN96NRF60TFH5S":110},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6CXYPCS7PEN96NRF60TFH5S","legacy-modernizer",null,"Designs incremental migration strategies, identifies service boundaries, produces dependency maps and migration roadmaps, and generates API facade designs for aging codebases. Use when modernizing legacy systems, implementing strangler fig pattern or branch by abstraction, decomposing monoliths, upgrading frameworks or languages, or reducing technical debt without disrupting business operations.","eric861129\u002FSKILLS_All-in-one","eric861129","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F74950944?v=4","01M6CXHDYEYRPFGGV4EFXCSYCF","ChiYu-Huang","01M6CXHE2J5CN1EBTY0FKV3ZKW",52,"MIT","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Flegacy-modernizer\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"legacy modernizer","Legacy","dependency","technical debt","strategies","pattern","frameworks","maps","master","engineer","architecture","specialized","branch","technical","system","refactoring","api","analysis","code","modernization","2026-11-10 10:12:30",false,"---\nname: legacy-modernizer\ndescription: Designs incremental migration strategies, identifies service boundaries, produces dependency maps and migration roadmaps, and generates API facade designs for aging codebases. Use when modernizing legacy systems, implementing strangler fig pattern or branch by abstraction, decomposing monoliths, upgrading frameworks or languages, or reducing technical debt without disrupting business operations.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: specialized\n  triggers: legacy modernization, strangler fig, incremental migration, technical debt, legacy refactoring, system migration, legacy system, modernize codebase\n  role: specialist\n  scope: architecture\n  output-format: code+analysis\n  related-skills: test-master, devops-engineer\n---\n\n# Legacy Modernizer\n\n## Core Workflow\n\n1. **Assess system** — Analyze codebase, dependencies, risks, and business constraints. Produce a dependency map and risk register before proceeding.\n   - *Validation checkpoint:* Confirm all external integrations and data contracts are documented before moving to step 2.\n\n2. **Plan migration** — Design an incremental roadmap with explicit rollback strategies per phase. Reference `references\u002Fsystem-assessment.md` for code analysis templates.\n   - *Validation checkpoint:* Confirm each phase has a defined rollback trigger and owner.\n\n3. **Build safety net** — Create characterization tests and monitoring before touching production code. Target 80%+ coverage of existing behavior.\n   - *Validation checkpoint:* Run the characterization test suite and confirm it passes green on the unmodified legacy system before proceeding.\n\n4. **Migrate incrementally** — Apply strangler fig pattern with feature flags. Route traffic via a facade; shift load gradually.\n   - *Validation checkpoint:* Verify error rates and latency metrics remain within baseline thresholds after each traffic increment (e.g., 5% → 25% → 50% → 100%).\n\n5. **Validate & iterate** — Run full test suite, review monitoring dashboards, and confirm business behavior is preserved before retiring legacy code.\n   - *Validation checkpoint:* New code must be proven stable at 100% traffic for at least one release cycle before legacy path is removed.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Strangler Fig | `references\u002Fstrangler-fig-pattern.md` | Incremental replacement, facade layer, routing |\n| Refactoring | `references\u002Frefactoring-patterns.md` | Extract service, branch by abstraction, adapters |\n| Migration | `references\u002Fmigration-strategies.md` | Database, UI, API, framework migrations |\n| Testing | `references\u002Flegacy-testing.md` | Characterization tests, golden master, approval |\n| Assessment | `references\u002Fsystem-assessment.md` | Code analysis, dependency mapping, risk evaluation |\n\n## Code Examples\n\n### Strangler Fig Facade (Python)\n```python\n# facade.py — routes requests to legacy or new service based on a feature flag\nimport os\nfrom legacy_service import LegacyOrderService\nfrom new_service import NewOrderService\n\nclass OrderServiceFacade:\n    def __init__(self):\n        self._legacy = LegacyOrderService()\n        self._new = NewOrderService()\n\n    def get_order(self, order_id: str):\n        if os.getenv(\"USE_NEW_ORDER_SERVICE\", \"false\").lower() == \"true\":\n            return self._new.fetch(order_id)\n        return self._legacy.get(order_id)\n```\n\n### Feature Flag Wrapper\n```python\n# feature_flags.py — thin wrapper around an environment or config-based flag store\nimport os\n\ndef flag_enabled(flag_name: str, default: bool = False) -> bool:\n    \"\"\"Check whether a migration feature flag is active.\"\"\"\n    return os.getenv(flag_name, str(default)).lower() == \"true\"\n\n# Usage\nif flag_enabled(\"USE_NEW_PAYMENT_GATEWAY\"):\n    result = new_gateway.charge(order)\nelse:\n    result = legacy_gateway.charge(order)\n```\n\n### Characterization Test Template (pytest)\n```python\n# test_characterization_orders.py\n# Captures existing legacy behavior as a golden-master safety net.\nimport pytest\nfrom legacy_service import LegacyOrderService\n\nservice = LegacyOrderService()\n\n@pytest.mark.parametrize(\"order_id,expected_status\", [\n    (\"ORD-001\", \"SHIPPED\"),\n    (\"ORD-002\", \"PENDING\"),\n    (\"ORD-003\", \"CANCELLED\"),\n])\ndef test_order_status_golden_master(order_id, expected_status):\n    \"\"\"Fail loudly if legacy behavior changes unexpectedly.\"\"\"\n    result = service.get(order_id)\n    assert result[\"status\"] == expected_status, (\n        f\"Characterization broken for {order_id}: \"\n        f\"expected {expected_status}, got {result['status']}\"\n    )\n```\n\n## Constraints\n\n### MUST DO\n- Maintain zero production disruption during all migrations\n- Create comprehensive test coverage before refactoring (target 80%+)\n- Use feature flags for all incremental rollouts\n- Implement monitoring and rollback procedures\n- Document all migration decisions and rationale\n- Preserve existing business logic and behavior\n- Communicate progress and risks transparently\n\n### MUST NOT DO\n- Big bang rewrites or replacements\n- Skip testing legacy behavior before changes\n- Deploy without rollback capability\n- Break existing integrations or APIs\n- Ignore technical debt in new code\n- Rush migrations without proper validation\n- Remove legacy code before new code is proven\n\n## Output Templates\n\nWhen implementing modernization, provide:\n1. Assessment summary (risks, dependencies, approach)\n2. Migration plan (phases, rollback strategy, metrics)\n3. Implementation code (facades, adapters, new services)\n4. Test coverage (characterization, integration, e2e)\n5. Monitoring setup (metrics, alerts, dashboards)\n\n## Knowledge Reference\n\nStrangler fig pattern, branch by abstraction, characterization testing, incremental migration, feature flags, canary deployments, API versioning, database refactoring, microservices extraction, technical debt reduction, zero-downtime deployment\n","# Legacy Modernizer\n\n## Core Workflow\n\n1. **Assess system** — Analyze codebase, dependencies, risks, and business constraints. Produce a dependency map and risk register before proceeding.\n   - *Validation checkpoint:* Confirm all external integrations and data contracts are documented before moving to step 2.\n\n2. **Plan migration** — Design an incremental roadmap with explicit rollback strategies per phase. Reference `references\u002Fsystem-assessment.md` for code analysis templates.\n   - *Validation checkpoint:* Confirm each phase has a defined rollback trigger and owner.\n\n3. **Build safety net** — Create characterization tests and monitoring before touching production code. Target 80%+ coverage of existing behavior.\n   - *Validation checkpoint:* Run the characterization test suite and confirm it passes green on the unmodified legacy system before proceeding.\n\n4. **Migrate incrementally** — Apply strangler fig pattern with feature flags. Route traffic via a facade; shift load gradually.\n   - *Validation checkpoint:* Verify error rates and latency metrics remain within baseline thresholds after each traffic increment (e.g., 5% → 25% → 50% → 100%).\n\n5. **Validate & iterate** — Run full test suite, review monitoring dashboards, and confirm business behavior is preserved before retiring legacy code.\n   - *Validation checkpoint:* New code must be proven stable at 100% traffic for at least one release cycle before legacy path is removed.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Strangler Fig | `references\u002Fstrangler-fig-pattern.md` | Incremental replacement, facade layer, routing |\n| Refactoring | `references\u002Frefactoring-patterns.md` | Extract service, branch by abstraction, adapters |\n| Migration | `references\u002Fmigration-strategies.md` | Database, UI, API, framework migrations |\n| Testing | `references\u002Flegacy-testing.md` | Characterization tests, golden master, approval |\n| Assessment | `references\u002Fsystem-assessment.md` | Code analysis, dependency mapping, risk evaluation |\n\n## Code Examples\n\n### Strangler Fig Facade (Python)\n```python\n# facade.py — routes requests to legacy or new service based on a feature flag\nimport os\nfrom legacy_service import LegacyOrderService\nfrom new_service import NewOrderService\n\nclass OrderServiceFacade:\n    def __init__(self):\n        self._legacy = LegacyOrderService()\n        self._new = NewOrderService()\n\n    def get_order(self, order_id: str):\n        if os.getenv(\"USE_NEW_ORDER_SERVICE\", \"false\").lower() == \"true\":\n            return self._new.fetch(order_id)\n        return self._legacy.get(order_id)\n```\n\n### Feature Flag Wrapper\n```python\n# feature_flags.py — thin wrapper around an environment or config-based flag store\nimport os\n\ndef flag_enabled(flag_name: str, default: bool = False) -> bool:\n    \"\"\"Check whether a migration feature flag is active.\"\"\"\n    return os.getenv(flag_name, str(default)).lower() == \"true\"\n\n# Usage\nif flag_enabled(\"USE_NEW_PAYMENT_GATEWAY\"):\n    result = new_gateway.charge(order)\nelse:\n    result = legacy_gateway.charge(order)\n```\n\n### Characterization Test Template (pytest)\n```python\n# test_characterization_orders.py\n# Captures existing legacy behavior as a golden-master safety net.\nimport pytest\nfrom legacy_service import LegacyOrderService\n\nservice = LegacyOrderService()\n\n@pytest.mark.parametrize(\"order_id,expected_status\", [\n    (\"ORD-001\", \"SHIPPED\"),\n    (\"ORD-002\", \"PENDING\"),\n    (\"ORD-003\", \"CANCELLED\"),\n])\ndef test_order_status_golden_master(order_id, expected_status):\n    \"\"\"Fail loudly if legacy behavior changes unexpectedly.\"\"\"\n    result = service.get(order_id)\n    assert result[\"status\"] == expected_status, (\n        f\"Characterization broken for {order_id}: \"\n        f\"expected {expected_status}, got {result['status']}\"\n    )\n```\n\n## Constraints\n\n### MUST DO\n- Maintain zero production disruption during all migrations\n- Create comprehensive test coverage before refactoring (target 80%+)\n- Use feature flags for all incremental rollouts\n- Implement monitoring and rollback procedures\n- Document all migration decisions and rationale\n- Preserve existing business logic and behavior\n- Communicate progress and risks transparently\n\n### MUST NOT DO\n- Big bang rewrites or replacements\n- Skip testing legacy behavior before changes\n- Deploy without rollback capability\n- Break existing integrations or APIs\n- Ignore technical debt in new code\n- Rush migrations without proper validation\n- Remove legacy code before new code is proven\n\n## Output Templates\n\nWhen implementing modernization, provide:\n1. Assessment summary (risks, dependencies, approach)\n2. Migration plan (phases, rollback strategy, metrics)\n3. Implementation code (facades, adapters, new services)\n4. Test coverage (characterization, integration, e2e)\n5. Monitoring setup (metrics, alerts, dashboards)\n\n## Knowledge Reference\n\nStrangler fig pattern, branch by abstraction, characterization testing, incremental migration, feature flags, canary deployments, API versioning, database refactoring, microservices extraction, technical debt reduction, zero-downtime deployment\n",{"name":5,"license":15,"metadata":57,"description":7},{"role":58,"scope":42,"author":59,"domain":43,"version":60,"triggers":61,"output-format":62,"related-skills":63},"specialist","https:\u002F\u002Fgithub.com\u002FJeffallan","1.1.0","legacy modernization, strangler fig, incremental migration, technical debt, legacy refactoring, system migration, legacy system, modernize codebase","code+analysis","test-master, devops-engineer","main","cbdd44aae21131521c09e42762e36178c790eacf","public\u002FSKILLS\u002FDevelopment & Code Tools\u002Flegacy-modernizer",13,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one","http:\u002F\u002Fhuangchiyu.com\u002FSKILLS_All-in-one\u002F","https:\u002F\u002Fgithub.com\u002Feric861129","https:\u002F\u002Fhuangchiyu.com\u002FChiYu-Blog\u002F","開發工程師，專注於 C#／.NET 系統現代化、AI-assisted engineering、開源工具與技術寫作。","2026-04-16 14:28:14",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add eric861129\u002FSKILLS_All-in-one --skill legacy-modernizer",{"tool":80,"command":81},"bunx","bunx skills add eric861129\u002FSKILLS_All-in-one --skill legacy-modernizer",{"tool":83,"command":84},"pnpm","pnpm dlx skills add eric861129\u002FSKILLS_All-in-one --skill legacy-modernizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Flegacy-modernizer\u002FSKILL.md",true,[88,94,98,102,106],{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Flegacy-testing.md","REFERENCE","参考文档",11537,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Flegacy-modernizer\u002Freferences\u002Flegacy-testing.md",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fmigration-strategies.md",11802,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Flegacy-modernizer\u002Freferences\u002Fmigration-strategies.md",{"path":99,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Frefactoring-patterns.md",12202,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Flegacy-modernizer\u002Freferences\u002Frefactoring-patterns.md",{"path":103,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fstrangler-fig-pattern.md",8433,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Flegacy-modernizer\u002Freferences\u002Fstrangler-fig-pattern.md",{"path":107,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fsystem-assessment.md",15140,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FDevelopment & Code Tools\u002Flegacy-modernizer\u002Freferences\u002Fsystem-assessment.md",[111,136,167,191,216,236],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":118,"publishedAt":52},"01M6CZ1WR3KNVTKSWH4GNWT646","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fwhat-if-oracle\u002FSKILL.md",[117],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[119,120,121,122,123,124,125,126,49,127,128,44,129,130,131,132,133,134,135,36],"oracle","what if oracle","go","run","planning","ux","futures","risk","explore","decision","question","read","write","idea","exploration","options","stress-test",{"skillNo":137,"name":138,"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":152,"publishedAt":52},"01M6CZ1QHGJE91A95MSN5EK5Q9","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fvenue-templates\u002FSKILL.md",[142,145,148,149],{"categoryNo":143,"categoryName":144,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":150,"categoryName":151,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[153,154,155,156,157,158,159,160,161,162,130,131,163,164,165,166],"templates","venue templates","research","guidelines","NeurIPS","ICML","LaTeX","science","Bash","access","edit","proposals","Academic","requirements",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":175,"publishedAt":52},"01M6CZ1KBQD2E5RTFB3BGVX7CD","the-fool","Use when challenging ideas, plans, decisions, or proposals using structured critical reasoning. Invoke to play devil's advocate, run a pre-mortem, red team, or audit evidence and assumptions.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fthe-fool\u002FSKILL.md",[173,174],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[176,177,121,178,42,122,50,179,180,181,182,183,184,185,164,186,187,188,189,190],"the fool","review","workflow","audit","forge","devil","team","designer","reviewer","challenge","stress test","evidence","expert","poke","ideas",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":200,"publishedAt":52},"01M6CZ1ES826S7P1X3333E40TA","scientific-writing","Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA\u002FAMA\u002FVancouver), figures\u002Ftables, reporting guidelines (CONSORT\u002FSTROBE\u002FPRISMA), for research papers and journal submissions.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fscientific-writing\u002FSKILL.md",[197,198,199],{"categoryNo":143,"categoryName":144,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":150,"categoryName":151,"taxonomyType":29,"taxonomyTypeDesc":30},[201,202,156,203,204,205,206,207,161,208,130,131,163,209,210,211,212,213,214,215],"writing","scientific writing","core","reporting","deep research","Citations","Outlines","tool","use","never","structure","deep","full","stage","prisma",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":223,"publishedAt":52},"01M6CZ1B2JGJTB9FRD0TW4RXXE","scientific-brainstorming","Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fscientific-brainstorming\u002FSKILL.md",[222],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[224,225,155,226,123,227,228,229,209,230,231,232,133,233,234,214,235],"brainstorming","scientific brainstorming","sessions","data","hypothesis","open","ideation","creative","do","connections","research ideation","generation",{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":248,"publishedAt":52},"01M6CZ16JG8N7A2ZX04BGE8J2Y","research-lookup","Look up current research information using the Parallel Chat API (primary) or Perplexity sonar-pro-search (academic paper searches). Automatically routes queries to the best backend. Use for finding papers, gathering research data, and verifying scientific information.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fresearch-lookup\u002FSKILL.md",[242,245,246,247],{"categoryNo":243,"categoryName":244,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[155,249,250,251,227,252,48,161,253,254,130,131,163,209,255,256,257,258,259,165],"lookup","research lookup","search","perplexity","parallel","openrouter","backend","up","look","queries","chat"]