[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PPVS55PJC2TVCE4V7P9BD":3,"skill-same:01M75PPVS55PJC2TVCE4V7P9BD":68},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75PPVS55PJC2TVCE4V7P9BD","pre-submission-reviewer",null,"Runs a pre-submission review of a technical paper across five dimensions: macro logic, writing details, English grammar, LaTeX formatting, and figure quality. Uses a reviewer-style severity taxonomy (CRITICAL \u002F MAJOR \u002F MINOR) and flags banned AI-tone vocabulary and em-dash misuse. Use when the user asks to 'review this paper', 'audit before submission', 'check the draft', 'find issues', 'proofread', or within one week of a submission deadline.","stanfish06\u002Fskillquarium","stanfish06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93099613?v=4","01M75F1CK4ZW109ZK3T26VN52F","Zhiyuan","01M75F1CM53VH6F79DZ8GXKKES",12,"CC-BY-4.0","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fpre-submission-reviewer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: pre-submission-reviewer\ndescription: >-\n  Runs a pre-submission review of a technical paper across five\n  dimensions: macro logic, writing details, English grammar, LaTeX\n  formatting, and figure quality. Uses a reviewer-style severity\n  taxonomy (CRITICAL \u002F MAJOR \u002F MINOR) and flags banned AI-tone\n  vocabulary and em-dash misuse. Use when the user asks to 'review\n  this paper', 'audit before submission', 'check the draft', 'find\n  issues', 'proofread', or within one week of a submission\n  deadline.\nlicense: CC-BY-4.0\n---\n\n# Pre-Submission Reviewer\n\n> [!note] Vault audit 2026-07-24 — USE-13\n> Use this to polish your own draft before submission — writing\u002FLaTeX\u002Ffigure mechanics, AI-tone vocabulary, and grammar, tagged CRITICAL\u002FMAJOR\u002FMINOR; for reviewer-side scientific evaluation of methodology and stats use `peer-review`, and to critique published claims use `scientific-critical-thinking`. Author-side pre-submission polish vs reviewer-side scientific evaluation is the distinguishing axis.\n\n## Overview\n\nThree to five days before a submission deadline is the window where\na careful external review pays off most. This skill takes a full\npaper or key sections and produces a structured review across five\ndimensions, each with severity-tagged findings and concrete\nrewrite suggestions. It enforces the mechanical rules from the\nwriting-checklist section (no em-dashes, no banned AI-tone\nvocabulary, leading text per paragraph, topic-sentence discipline,\ncitation-format uniformity) and surfaces the patterns that\nnon-native English-speaking authors most commonly violate\n(articles, subject-verb agreement, tense consistency, which versus\nthat, Chinglish phrasing).\n\nThe output is not a rewrite. It is a prioritised list of findings\nwith severity tags; the author decides which to fix. CRITICAL items\nshould block submission until addressed.\n\n## When to use this skill\n\n- Three to five days before a submission deadline.\n- The user asks to 'review this paper', 'audit before submission',\n  'check the draft', 'find issues', 'proofread'.\n- After a camera-ready revision, before sending the final version.\n- After any major rewrite (rebuttal responses, Section 3 overhaul).\n- When the user suspects AI-tone contamination in a section.\n\n## When NOT to use this skill\n\n- The paper is still being structured. Use `tech-paper-template`,\n  `intro-drafter`, or `benchmark-paper-template` (separate plugin) first.\n- The user wants structural advice rather than review. Use the\n  drafting skills instead.\n\n## Core procedure\n\n### Step 1: Dimension 1 Macro logic review\n\nSee: references\u002Flogic-and-structure.md for the Logic First rule,\nSelf-contained rule, Leading Text rule, and Running Example rule.\n\nCheck:\n\n- Introduction flowchart is intact (Background, Limitations, Goal\n  or Key Idea, Challenges, Methodology, Contributions).\n- Contributions map one-to-one with methodology modules and with\n  section numbers.\n- Experiments validate the paper's main claims, not tangential\n  ones.\n- Related Work covers the necessary prior art.\n- Running example is consistent across Introduction, Methodology,\n  Experiments.\n\nEvery break in the chain is CRITICAL.\n\n### Step 2: Dimension 2 Writing details review\n\nSee: references\u002Flogic-and-structure.md for paragraph-level rules.\n\nCheck:\n\n- Every paragraph has a topic sentence.\n- Paragraphs transition smoothly; no orphan paragraphs.\n- Paragraphs are not over 10 lines; split if so.\n- No repeated or redundant passages.\n- Abstract covers problem, method, result.\n\n### Step 3: Dimension 3 English grammar review\n\nSee: references\u002Fgrammar-rules.md for the canonical list of errors\ncommon to non-native English authors, with corrections and\nexamples.\n\nCheck the usual suspects:\n\n- Article use (a, an, the).\n- Subject-verb agreement (third-person singular).\n- Tense consistency (Related Work past, method present).\n- Passive-voice overuse.\n- Which versus that.\n- Sentence length; split long sentences at \"Specifically,\".\n- Chinglish patterns.\n\n### Step 4: Dimension 4 LaTeX format review\n\nSee: references\u002Flatex-rules.md for the canonical list of LaTeX-\nspecific issues.\n\nCheck:\n\n- Equation numbering contiguous; every numbered equation\n  referenced.\n- Figures and tables have captions; captions are detailed.\n- Citations use the correct command and the non-breaking tilde\n  (for example, `ResNet~\\cite{X}`, never `ResNet\\cite{X}`).\n- Labels use underscores, not spaces or hyphens.\n- Vector figure format; no raster.\n- Page-limit compliance.\n\n### Step 5: Dimension 5 Figure quality review\n\nSee: references\u002Fforbidden-patterns.md for chartjunk patterns and\nthe full figure-quality checklist.\n\nFor each figure:\n\n- Vector format.\n- Font size large enough post-scaling.\n- Colour-blind-safe palette; dual encoding.\n- Self-contained caption with a finding in the first sentence.\n- No chartjunk.\n- Motivated example is concrete and failure-revealing.\n- Solution overview has labels matching section titles.\n\n### Step 6: Banned-vocabulary and em-dash scan\n\nSee: references\u002Fforbidden-patterns.md for the banned-word list.\n\nScan the full paper for:\n\n- Em-dashes used as sentence connectors (banned; project rule).\n- AI-tone words: innovative, pioneering, revolutionary paradigm,\n  transformative framework, superior, surpass, excel, remarkable,\n  unprecedented, breakthrough performance, general-purpose, is\n  capable of, notably, yet, yielding, at its essence, encompass,\n  differentiate, reveal, underscore, pave the way for, highlight\n  the potential of, profound challenges, stems from, rigid,\n  impede.\n\nFlag each occurrence with a severity tag. Em-dashes are MAJOR by\ndefault; banned AI-tone words are MAJOR if they appear three or\nmore times.\n\n### Step 7: Section-by-section review\n\nSee: references\u002Fsection-guides.md for the per-section writing\nguides for Abstract, Introduction, Problem Formulation, Framework\nor Method, Experiments, Related Work, and Conclusion.\n\nFor each section, check that the section's content matches the\nguide's canonical structure (for example, Abstract's five-sentence\nformula: what, why, challenges, how, results).\n\n### Step 8: Integrity gate\n\nRun the checks in the Integrity gate section below.\n\n### Step 9: Output\n\nEmit the review in the Output format below.\n\n## Severity taxonomy\n\n- **CRITICAL**: blocks submission. Example: contributions do not\n  map to sections; introduction flowchart broken; no real-world\n  running example; raster figure in final draft; missing key\n  baseline; page-limit violation.\n- **MAJOR**: reviewers will flag in first round. Example:\n  topic-sentence absent from 3+ paragraphs; em-dash in 5+ places;\n  banned AI-tone word in 3+ places; Table 1 comparison missing;\n  chart type mismatched with data.\n- **MINOR**: polish. Example: two long sentences that could be\n  split; default Matplotlib styling; single article error.\n\n## Integrity gate\n\nEach bullet is tagged [inspection] (LLM verifies from the paper\ntext) or [attestation] (LLM runs the procedure and states it has\ndone so; user remains responsible for confirming completeness).\n\nBefore emitting the review:\n\n1. **[inspection]** Every finding quotes specific text (sentence,\n   phrase, figure name); no \"the Introduction is unclear\" without\n   a quoted line.\n2. **[inspection]** Every CRITICAL finding has a concrete fix\n   suggestion, not \"rewrite entirely\".\n3. **[inspection]** No fabricated quotes: only text actually\n   present in the submitted material.\n4. **[inspection]** Severity assignments follow the taxonomy;\n   nothing is marked CRITICAL for taste reasons.\n5. **[inspection]** Dimension 3 (grammar) findings cite the\n   specific grammar rule from `references\u002Fgrammar-rules.md`.\n6. **[attestation]** Dimension 6 banned-vocabulary scan is run in\n   full on the entire paper, not sampled. The skill attests the\n   full scan; if the paper is extremely long, the skill states it\n   chunked the input and describes the chunking strategy.\n7. **[inspection]** Final score matches the CRITICAL + MAJOR\n   count; a score of 9 or 10 requires zero CRITICAL and at most\n   two MAJOR items.\n\nIf any [inspection] check fails, mark the output as \"needs user\nattention\". For [attestation] bullets, the skill states the scope\nof its scan and the user confirms completeness.\n\n## Output format\n\n### Summary\n- CRITICAL: \u003Cn>\n- MAJOR: \u003Cm>\n- MINOR: \u003Ck>\n- Top three fixes first: ...\n\n### Dimension 1: Macro logic\n| # | Finding | Severity | Suggested fix |\n|---|---|---|---|\n| 1 | \u003Cquoted text> | CRITICAL or MAJOR or MINOR | \u003Cfix> |\n\n### Dimension 2: Writing details\n\u003Csame table shape>\n\n### Dimension 3: English grammar\n\u003Csame table shape, citing grammar-rule ID>\n\n### Dimension 4: LaTeX format\n\u003Csame table shape>\n\n### Dimension 5: Figure quality\n\u003Csame table shape>\n\n### Banned-vocabulary and em-dash scan\n\u003Clist with line references>\n\n### Integrity gate result\n- Gate 1 through 7: \u003Cpass or fail>\n\n### Final score (1-10)\n\u003Cscore>\n\n### Submission recommendation\n- \u003CReady to submit | Needs 1-2 days more work | Needs major revision before submission>\n","# Pre-Submission Reviewer\n\n> [!note] Vault audit 2026-07-24 — USE-13\n> Use this to polish your own draft before submission — writing\u002FLaTeX\u002Ffigure mechanics, AI-tone vocabulary, and grammar, tagged CRITICAL\u002FMAJOR\u002FMINOR; for reviewer-side scientific evaluation of methodology and stats use `peer-review`, and to critique published claims use `scientific-critical-thinking`. Author-side pre-submission polish vs reviewer-side scientific evaluation is the distinguishing axis.\n\n## Overview\n\nThree to five days before a submission deadline is the window where\na careful external review pays off most. This skill takes a full\npaper or key sections and produces a structured review across five\ndimensions, each with severity-tagged findings and concrete\nrewrite suggestions. It enforces the mechanical rules from the\nwriting-checklist section (no em-dashes, no banned AI-tone\nvocabulary, leading text per paragraph, topic-sentence discipline,\ncitation-format uniformity) and surfaces the patterns that\nnon-native English-speaking authors most commonly violate\n(articles, subject-verb agreement, tense consistency, which versus\nthat, Chinglish phrasing).\n\nThe output is not a rewrite. It is a prioritised list of findings\nwith severity tags; the author decides which to fix. CRITICAL items\nshould block submission until addressed.\n\n## When to use this skill\n\n- Three to five days before a submission deadline.\n- The user asks to 'review this paper', 'audit before submission',\n  'check the draft', 'find issues', 'proofread'.\n- After a camera-ready revision, before sending the final version.\n- After any major rewrite (rebuttal responses, Section 3 overhaul).\n- When the user suspects AI-tone contamination in a section.\n\n## When NOT to use this skill\n\n- The paper is still being structured. Use `tech-paper-template`,\n  `intro-drafter`, or `benchmark-paper-template` (separate plugin) first.\n- The user wants structural advice rather than review. Use the\n  drafting skills instead.\n\n## Core procedure\n\n### Step 1: Dimension 1 Macro logic review\n\nSee: references\u002Flogic-and-structure.md for the Logic First rule,\nSelf-contained rule, Leading Text rule, and Running Example rule.\n\nCheck:\n\n- Introduction flowchart is intact (Background, Limitations, Goal\n  or Key Idea, Challenges, Methodology, Contributions).\n- Contributions map one-to-one with methodology modules and with\n  section numbers.\n- Experiments validate the paper's main claims, not tangential\n  ones.\n- Related Work covers the necessary prior art.\n- Running example is consistent across Introduction, Methodology,\n  Experiments.\n\nEvery break in the chain is CRITICAL.\n\n### Step 2: Dimension 2 Writing details review\n\nSee: references\u002Flogic-and-structure.md for paragraph-level rules.\n\nCheck:\n\n- Every paragraph has a topic sentence.\n- Paragraphs transition smoothly; no orphan paragraphs.\n- Paragraphs are not over 10 lines; split if so.\n- No repeated or redundant passages.\n- Abstract covers problem, method, result.\n\n### Step 3: Dimension 3 English grammar review\n\nSee: references\u002Fgrammar-rules.md for the canonical list of errors\ncommon to non-native English authors, with corrections and\nexamples.\n\nCheck the usual suspects:\n\n- Article use (a, an, the).\n- Subject-verb agreement (third-person singular).\n- Tense consistency (Related Work past, method present).\n- Passive-voice overuse.\n- Which versus that.\n- Sentence length; split long sentences at \"Specifically,\".\n- Chinglish patterns.\n\n### Step 4: Dimension 4 LaTeX format review\n\nSee: references\u002Flatex-rules.md for the canonical list of LaTeX-\nspecific issues.\n\nCheck:\n\n- Equation numbering contiguous; every numbered equation\n  referenced.\n- Figures and tables have captions; captions are detailed.\n- Citations use the correct command and the non-breaking tilde\n  (for example, `ResNet~\\cite{X}`, never `ResNet\\cite{X}`).\n- Labels use underscores, not spaces or hyphens.\n- Vector figure format; no raster.\n- Page-limit compliance.\n\n### Step 5: Dimension 5 Figure quality review\n\nSee: references\u002Fforbidden-patterns.md for chartjunk patterns and\nthe full figure-quality checklist.\n\nFor each figure:\n\n- Vector format.\n- Font size large enough post-scaling.\n- Colour-blind-safe palette; dual encoding.\n- Self-contained caption with a finding in the first sentence.\n- No chartjunk.\n- Motivated example is concrete and failure-revealing.\n- Solution overview has labels matching section titles.\n\n### Step 6: Banned-vocabulary and em-dash scan\n\nSee: references\u002Fforbidden-patterns.md for the banned-word list.\n\nScan the full paper for:\n\n- Em-dashes used as sentence connectors (banned; project rule).\n- AI-tone words: innovative, pioneering, revolutionary paradigm,\n  transformative framework, superior, surpass, excel, remarkable,\n  unprecedented, breakthrough performance, general-purpose, is\n  capable of, notably, yet, yielding, at its essence, encompass,\n  differentiate, reveal, underscore, pave the way for, highlight\n  the potential of, profound challenges, stems from, rigid,\n  impede.\n\nFlag each occurrence with a severity tag. Em-dashes are MAJOR by\ndefault; banned AI-tone words are MAJOR if they appear three or\nmore times.\n\n### Step 7: Section-by-section review\n\nSee: references\u002Fsection-guides.md for the per-section writing\nguides for Abstract, Introduction, Problem Formulation, Framework\nor Method, Experiments, Related Work, and Conclusion.\n\nFor each section, check that the section's content matches the\nguide's canonical structure (for example, Abstract's five-sentence\nformula: what, why, challenges, how, results).\n\n### Step 8: Integrity gate\n\nRun the checks in the Integrity gate section below.\n\n### Step 9: Output\n\nEmit the review in the Output format below.\n\n## Severity taxonomy\n\n- **CRITICAL**: blocks submission. Example: contributions do not\n  map to sections; introduction flowchart broken; no real-world\n  running example; raster figure in final draft; missing key\n  baseline; page-limit violation.\n- **MAJOR**: reviewers will flag in first round. Example:\n  topic-sentence absent from 3+ paragraphs; em-dash in 5+ places;\n  banned AI-tone word in 3+ places; Table 1 comparison missing;\n  chart type mismatched with data.\n- **MINOR**: polish. Example: two long sentences that could be\n  split; default Matplotlib styling; single article error.\n\n## Integrity gate\n\nEach bullet is tagged [inspection] (LLM verifies from the paper\ntext) or [attestation] (LLM runs the procedure and states it has\ndone so; user remains responsible for confirming completeness).\n\nBefore emitting the review:\n\n1. **[inspection]** Every finding quotes specific text (sentence,\n   phrase, figure name); no \"the Introduction is unclear\" without\n   a quoted line.\n2. **[inspection]** Every CRITICAL finding has a concrete fix\n   suggestion, not \"rewrite entirely\".\n3. **[inspection]** No fabricated quotes: only text actually\n   present in the submitted material.\n4. **[inspection]** Severity assignments follow the taxonomy;\n   nothing is marked CRITICAL for taste reasons.\n5. **[inspection]** Dimension 3 (grammar) findings cite the\n   specific grammar rule from `references\u002Fgrammar-rules.md`.\n6. **[attestation]** Dimension 6 banned-vocabulary scan is run in\n   full on the entire paper, not sampled. The skill attests the\n   full scan; if the paper is extremely long, the skill states it\n   chunked the input and describes the chunking strategy.\n7. **[inspection]** Final score matches the CRITICAL + MAJOR\n   count; a score of 9 or 10 requires zero CRITICAL and at most\n   two MAJOR items.\n\nIf any [inspection] check fails, mark the output as \"needs user\nattention\". For [attestation] bullets, the skill states the scope\nof its scan and the user confirms completeness.\n\n## Output format\n\n### Summary\n- CRITICAL: \u003Cn>\n- MAJOR: \u003Cm>\n- MINOR: \u003Ck>\n- Top three fixes first: ...\n\n### Dimension 1: Macro logic\n| # | Finding | Severity | Suggested fix |\n|---|---|---|---|\n| 1 | \u003Cquoted text> | CRITICAL or MAJOR or MINOR | \u003Cfix> |\n\n### Dimension 2: Writing details\n\u003Csame table shape>\n\n### Dimension 3: English grammar\n\u003Csame table shape, citing grammar-rule ID>\n\n### Dimension 4: LaTeX format\n\u003Csame table shape>\n\n### Dimension 5: Figure quality\n\u003Csame table shape>\n\n### Banned-vocabulary and em-dash scan\n\u003Clist with line references>\n\n### Integrity gate result\n- Gate 1 through 7: \u003Cpass or fail>\n\n### Final score (1-10)\n\u003Cscore>\n\n### Submission recommendation\n- \u003CReady to submit | Needs 1-2 days more work | Needs major revision before submission>\n",{"name":5,"license":15,"description":7},"master","49e49abf2f670d429e0b7e2c0349739c3fdd5cbe","skills\u002Fpre-submission-reviewer",5,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium","https:\u002F\u002Fgithub.com\u002Fstanfish06","https:\u002F\u002Fwww.stanfish.dev\u002F","2026-11-14 21:31:37",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add stanfish06\u002Fskillquarium --skill pre-submission-reviewer",{"tool":38,"command":39},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill pre-submission-reviewer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill pre-submission-reviewer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fpre-submission-reviewer\u002FSKILL.md",true,[46,52,56,60,64],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fforbidden-patterns.md","REFERENCE","参考文档",4801,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fpre-submission-reviewer\u002Freferences\u002Fforbidden-patterns.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fgrammar-rules.md",4767,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fpre-submission-reviewer\u002Freferences\u002Fgrammar-rules.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Flatex-rules.md",4439,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fpre-submission-reviewer\u002Freferences\u002Flatex-rules.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Flogic-and-structure.md",4663,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fpre-submission-reviewer\u002Freferences\u002Flogic-and-structure.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fsection-guides.md",5334,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fpre-submission-reviewer\u002Freferences\u002Fsection-guides.md",[69,77,86,93,100,107],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M76ZJTRVA456GD7K8Y3EP82H","zarr-python","Stores and queries chunked N-D scientific arrays with Zarr-Python 3, including codecs, sharding, S3\u002FGCS storage, and NumPy\u002FDask\u002FXarray integration. Use for array layout, bounded I\u002FO, format migration, or scientific metadata preservation.","MIT","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M76ZJQZ15Q1HKC5V85NHE325","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\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":81,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M76ZJ8ASZ4QYQ70Y6SBA4Z4S","xarray","N-dimensional labeled arrays and datasets in Python. Built on top of NumPy and Dask. It introduces labels in the form of dimensions, coordinates, and attributes on top of raw NumPy-like arrays, making data analysis in physical sciences more intuitive and less error-prone. Use for working with multi-dimensional scientific data, NetCDF\u002FGRIB\u002FZarr files, climate\u002Fweather\u002Foceanographic datasets, remote sensing, geospatial imaging, large out-of-memory datasets with Dask, and labeled array operations.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fxarray\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M76ZHFBXD6VXPQ02VCEG202B","writing-mstest-tests","Use when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for \"review\" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected\u002Factual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext\u002Flifecycle; timeout\u002Fcancellation; OS\u002FCI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest\u002Fnon-.NET code.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwriting-mstest-tests\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M76ZDFDF4N88RH6HSYGS7GP2","wgs-prs","End-to-end WGS to polygenic risk score pipeline. Takes paired-end FASTQ files (or a pre-existing VCF) through nf-core\u002Fsarek for variant calling, applies VCF QC (normalisation, hard filtering, Ti\u002FTv and Het\u002FHom checks), then computes polygenic risk scores via the PGS Catalog. Fills the FASTQ to VCF gap upstream of the gwas-prs skill.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwgs-prs\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M76ZCC1SC68J42QK4MDC8RCG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[]]