[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77Y5RN55VP6BSNSSDHF4YVR":3,"skill-same:01M77Y5RN55VP6BSNSSDHF4YVR":49},{"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":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M77Y5RN55VP6BSNSSDHF4YVR","scholar-evaluation",null,"Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.","503496348-ops\u002Fmischief-production","503496348-ops","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F266905914?v=4","01M77X5J7XQWWZGT8998HDGXQM","AtomCollide","01M77X5J8V78Y3NXMY6BBC75X9",2,"MIT","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fecc-scientific-thinking-scholar-evaluation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: scholar-evaluation\ndescription: Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.\nmetadata:\n  origin: community\n---\n\n# Scholar Evaluation\n\nUse this skill to evaluate academic or scientific work with a repeatable rubric.\n\n## When to Use\n\n- Reviewing a research paper, proposal, thesis chapter, or literature review.\n- Checking whether claims are supported by cited evidence.\n- Evaluating methodology, study design, analysis, or limitations.\n- Comparing two or more papers for quality or relevance.\n- Producing structured feedback for revision.\n\n## Evaluation Scope\n\nStart by identifying the artifact:\n\n- empirical research paper\n- theoretical paper\n- technical report\n- systematic or narrative literature review\n- research proposal\n- thesis or dissertation chapter\n- conference abstract or short paper\n\nThen choose scope:\n\n- **comprehensive**: all rubric dimensions\n- **targeted**: one or two dimensions, such as method or citations\n- **comparative**: rank multiple works against the same rubric\n\n## Rubric\n\nScore each applicable dimension from 1 to 5:\n\n- 5: excellent; clear, rigorous, and publication-ready\n- 4: good; minor improvements needed\n- 3: adequate; meaningful gaps but usable\n- 2: weak; substantial revision needed\n- 1: poor; major validity or clarity problems\n\nUse `N\u002FA` for dimensions that do not apply.\n\n### 1. Problem and Research Question\n\n- Is the problem clear and specific?\n- Is the contribution meaningful?\n- Are scope and assumptions explicit?\n- Does the question match the claimed contribution?\n\n### 2. Literature and Context\n\n- Is relevant prior work covered?\n- Does the work synthesize rather than merely list sources?\n- Are gaps accurately identified?\n- Are recent and foundational sources balanced?\n\n### 3. Methodology\n\n- Does the method answer the research question?\n- Are design choices justified?\n- Are variables, datasets, participants, or materials described clearly?\n- Could another researcher reproduce the work?\n- Are ethical and practical constraints acknowledged?\n\n### 4. Data and Evidence\n\n- Are data sources credible and appropriate?\n- Is sample size or corpus coverage adequate?\n- Are inclusion, exclusion, and preprocessing decisions documented?\n- Are missing data and bias risks discussed?\n\n### 5. Analysis\n\n- Are statistical, qualitative, or computational methods appropriate?\n- Are baselines and controls fair?\n- Are uncertainty, sensitivity, or robustness checks included when needed?\n- Are alternative explanations considered?\n\n### 6. Results and Interpretation\n\n- Are results clearly presented?\n- Do claims stay within the evidence?\n- Are figures, tables, and metrics understandable?\n- Are negative or null results handled honestly?\n\n### 7. Limitations and Threats to Validity\n\n- Are limitations specific rather than generic?\n- Are internal, external, construct, and conclusion-validity risks addressed?\n- Does the paper distinguish speculation from demonstrated results?\n\n### 8. Writing and Structure\n\n- Is the argument easy to follow?\n- Are sections organized around the research question?\n- Are definitions and notation clear?\n- Is the tone precise and scholarly?\n\n### 9. Citations\n\n- Do cited papers support the claims attached to them?\n- Are primary sources used where possible?\n- Are reviews labeled as reviews?\n- Are preprints labeled as preprints?\n- Are citation metadata and links correct?\n\n## Review Process\n\n1. Read the abstract, introduction, figures, and conclusion for claimed\n   contribution.\n2. Read methods and results for evidence quality.\n3. Check the strongest claims against cited sources.\n4. Score each applicable dimension.\n5. Separate critical blockers from revision suggestions.\n6. End with concrete next edits.\n\n## Output Template\n\n```markdown\n# Scholar Evaluation: \u003CArtifact>\n\n## Overall Assessment\n\n- Overall score: \u003C1-5 or N\u002FA>\n- Confidence: \u003Chigh | medium | low>\n- Summary: \u003C3-5 sentences>\n\n## Dimension Scores\n\n| Dimension | Score | Evidence | Revision priority |\n| --- | ---: | --- | --- |\n| Problem and question |  |  |  |\n| Literature and context |  |  |  |\n| Methodology |  |  |  |\n| Data and evidence |  |  |  |\n| Analysis |  |  |  |\n| Results and interpretation |  |  |  |\n| Limitations |  |  |  |\n| Writing and structure |  |  |  |\n| Citations |  |  |  |\n\n## Critical Issues\n\n## Recommended Revisions\n\n## Evidence Checks Needed\n```\n\n## Pitfalls\n\n- Do not use the score as a substitute for concrete feedback.\n- Do not penalize a paper for omitting a dimension outside its scope.\n- Do not treat citation count, venue, or author reputation as proof of quality.\n- Do not accept unsupported claims just because they appear in the abstract.\n","# Scholar Evaluation\n\nUse this skill to evaluate academic or scientific work with a repeatable rubric.\n\n## When to Use\n\n- Reviewing a research paper, proposal, thesis chapter, or literature review.\n- Checking whether claims are supported by cited evidence.\n- Evaluating methodology, study design, analysis, or limitations.\n- Comparing two or more papers for quality or relevance.\n- Producing structured feedback for revision.\n\n## Evaluation Scope\n\nStart by identifying the artifact:\n\n- empirical research paper\n- theoretical paper\n- technical report\n- systematic or narrative literature review\n- research proposal\n- thesis or dissertation chapter\n- conference abstract or short paper\n\nThen choose scope:\n\n- **comprehensive**: all rubric dimensions\n- **targeted**: one or two dimensions, such as method or citations\n- **comparative**: rank multiple works against the same rubric\n\n## Rubric\n\nScore each applicable dimension from 1 to 5:\n\n- 5: excellent; clear, rigorous, and publication-ready\n- 4: good; minor improvements needed\n- 3: adequate; meaningful gaps but usable\n- 2: weak; substantial revision needed\n- 1: poor; major validity or clarity problems\n\nUse `N\u002FA` for dimensions that do not apply.\n\n### 1. Problem and Research Question\n\n- Is the problem clear and specific?\n- Is the contribution meaningful?\n- Are scope and assumptions explicit?\n- Does the question match the claimed contribution?\n\n### 2. Literature and Context\n\n- Is relevant prior work covered?\n- Does the work synthesize rather than merely list sources?\n- Are gaps accurately identified?\n- Are recent and foundational sources balanced?\n\n### 3. Methodology\n\n- Does the method answer the research question?\n- Are design choices justified?\n- Are variables, datasets, participants, or materials described clearly?\n- Could another researcher reproduce the work?\n- Are ethical and practical constraints acknowledged?\n\n### 4. Data and Evidence\n\n- Are data sources credible and appropriate?\n- Is sample size or corpus coverage adequate?\n- Are inclusion, exclusion, and preprocessing decisions documented?\n- Are missing data and bias risks discussed?\n\n### 5. Analysis\n\n- Are statistical, qualitative, or computational methods appropriate?\n- Are baselines and controls fair?\n- Are uncertainty, sensitivity, or robustness checks included when needed?\n- Are alternative explanations considered?\n\n### 6. Results and Interpretation\n\n- Are results clearly presented?\n- Do claims stay within the evidence?\n- Are figures, tables, and metrics understandable?\n- Are negative or null results handled honestly?\n\n### 7. Limitations and Threats to Validity\n\n- Are limitations specific rather than generic?\n- Are internal, external, construct, and conclusion-validity risks addressed?\n- Does the paper distinguish speculation from demonstrated results?\n\n### 8. Writing and Structure\n\n- Is the argument easy to follow?\n- Are sections organized around the research question?\n- Are definitions and notation clear?\n- Is the tone precise and scholarly?\n\n### 9. Citations\n\n- Do cited papers support the claims attached to them?\n- Are primary sources used where possible?\n- Are reviews labeled as reviews?\n- Are preprints labeled as preprints?\n- Are citation metadata and links correct?\n\n## Review Process\n\n1. Read the abstract, introduction, figures, and conclusion for claimed\n   contribution.\n2. Read methods and results for evidence quality.\n3. Check the strongest claims against cited sources.\n4. Score each applicable dimension.\n5. Separate critical blockers from revision suggestions.\n6. End with concrete next edits.\n\n## Output Template\n\n```markdown\n# Scholar Evaluation: \u003CArtifact>\n\n## Overall Assessment\n\n- Overall score: \u003C1-5 or N\u002FA>\n- Confidence: \u003Chigh | medium | low>\n- Summary: \u003C3-5 sentences>\n\n## Dimension Scores\n\n| Dimension | Score | Evidence | Revision priority |\n| --- | ---: | --- | --- |\n| Problem and question |  |  |  |\n| Literature and context |  |  |  |\n| Methodology |  |  |  |\n| Data and evidence |  |  |  |\n| Analysis |  |  |  |\n| Results and interpretation |  |  |  |\n| Limitations |  |  |  |\n| Writing and structure |  |  |  |\n| Citations |  |  |  |\n\n## Critical Issues\n\n## Recommended Revisions\n\n## Evidence Checks Needed\n```\n\n## Pitfalls\n\n- Do not use the score as a substitute for concrete feedback.\n- Do not penalize a paper for omitting a dimension outside its scope.\n- Do not treat citation count, venue, or author reputation as proof of quality.\n- Do not accept unsupported claims just because they appear in the abstract.\n",{"name":5,"metadata":24,"description":7},{"origin":25},"community","main","c9103dbad48ef3005f163584d0f2abd4591217f6","skills\u002Fecc-scientific-thinking-scholar-evaluation",1,"https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production","https:\u002F\u002Fgithub.com\u002F503496348-ops","https:\u002F\u002F503496348-ops.github.io\u002Fatomcollide-product-matrix\u002F#tree","元素碰撞-AtomCollide-AI 智能体实验室 测试人专属成长社群 正式招募\r\n我们的目标很纯粹：连接每一位测试工程师\u002FAI使用探索与爱好者，让你在这里既能扎实打磨技术硬实力，也能打通职业晋升的新通路，这是一个专注于AI领域的开源组","2026-07-30 00:35:42",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add 503496348-ops\u002Fmischief-production --skill scholar-evaluation",{"tool":41,"command":42},"bunx","bunx skills add 503496348-ops\u002Fmischief-production --skill scholar-evaluation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add 503496348-ops\u002Fmischief-production --skill scholar-evaluation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fecc-scientific-thinking-scholar-evaluation\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M77YG7NPZHE751W9QGK3H9ED","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-skills\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M77YG4HPYH0GJP974DZ6KCPQ","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-plans\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M77YFZW1FZ1GVC5C89NPE5M8","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-verification-before-completion\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M77YFVPWANT5VE5GWBTKHPA2","using-智械工程","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-superpowers\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M77YFQJAW5PX3QYSBCD3B24S","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M77YFMSTB70VX8W2QHNJWYB0","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-test-driven-development\u002FSKILL.md",[],[]]