[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FDFRVZRASZF9SV67B00WKG":3,"skill-same:01M7FDFRVZRASZF9SV67B00WKG":45},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7FDFRVZRASZF9SV67B00WKG","polish",null,"Perform final pre-submission checks: formatting, citations, figures, metadata, and build verification. Systematic checklist identifies remaining issues and suggests fixes.","Abdulqudduz\u002Fclaude-anvil","Abdulqudduz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F111210054?v=4","01M7FDCB600A6D0CXP9AZ75K5G","MAQGEEK","01M7FDCB6K7XH3DSTYWD1B4GVB",0,"MIT","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fpapermill\u002Fskills\u002Fpolish\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: polish\ndescription: >-\n  Perform final pre-submission checks: formatting, citations, figures,\n  metadata, and build verification. Systematic checklist identifies\n  remaining issues and suggests fixes.\n---\n\n# Submission Polish\n\nPerform a final quality check on a research paper before submission. This is the last line of defense: catch everything that would annoy a reviewer or cause a desk rejection.\n\n## Step 1: Read Context\n\nRead `.papermill\u002Fstate.md` (Read tool) for:\n- **Venue**: Target venue and its requirements.\n- **Format**: Paper format (latex, markdown, rmarkdown).\n- **Review history**: Outstanding issues from previous reviews.\n\nIf `.papermill\u002Fstate.md` does not exist, the pre-flight check can still run: infer the format from the manuscript files and ask the user for the target venue. The checklist works regardless. Suggest running `\u002Fpapermill:init` to capture venue and format persistently.\n\nRead the complete manuscript (Read tool).\n\n## Step 2: Pre-Flight Checklist\n\nWork through each category systematically. Report issues as they are found.\n\n### Formatting\n- [ ] Paper compiles without errors\n- [ ] No LaTeX warnings (especially undefined references, missing citations)\n- [ ] Page count within venue limits\n- [ ] Correct venue template\u002Fstyle file used\n- [ ] Margins, font size, and spacing match requirements\n- [ ] Line numbers included if required by venue\n- [ ] Anonymous submission if required (no author names in text or metadata)\n\n### Abstract\n- [ ] Word count within venue limits (typically 150-300 words)\n- [ ] Self-contained (no citations, no undefined terms)\n- [ ] States the problem, approach, main result, and significance\n- [ ] Matches the paper's actual content\n\n### Citations and References\n- [ ] All citations resolve (no \"?\" in the PDF)\n- [ ] Bibliography is complete (no missing fields)\n- [ ] Citation style matches venue requirements\n- [ ] All references are cited in the text (no orphan bib entries that should be removed)\n- [ ] All cited works are in the bibliography\n- [ ] Self-citations are reasonable in number\n\n### Figures and Tables\n- [ ] All figures are referenced in the text\n- [ ] Figure captions are self-contained (reader should understand without reading the text)\n- [ ] Resolution is sufficient for print (300+ DPI for raster images)\n- [ ] Color is used accessibly (works in grayscale, colorblind-safe)\n- [ ] Tables have clear headers and units\n\n### Mathematical Content\n- [ ] All symbols are defined before use\n- [ ] Notation is consistent throughout\n- [ ] Equation numbering is correct and referenced\n- [ ] Theorem\u002Fdefinition\u002Fproof environments are properly labeled\n- [ ] No orphan proofs (every proof has a parent theorem\u002Fproposition)\n\n### Writing Quality\n- [ ] No first-person narrative inconsistencies (\"I\" vs \"we\")\n- [ ] Consistent tense usage\n- [ ] No obvious typos or grammatical errors\n- [ ] Acronyms defined on first use\n- [ ] No overly long paragraphs (break up walls of text)\n\n### Metadata\n- [ ] Author names and affiliations are correct\n- [ ] ORCID identifiers included if venue supports them\n- [ ] Keywords\u002Fsubject classification provided\n- [ ] Acknowledgments section present (funding, help, etc.)\n- [ ] Data availability statement if required\n- [ ] Code availability statement if applicable\n\n### Supplementary Material\n- [ ] Appendices are referenced from the main text\n- [ ] Supplementary files are in the required format\n- [ ] Appendix content is not essential to understanding the main paper\n\n## Step 3: Build Verification\n\nLaunch the format validator (Agent tool, `subagent_type: \"papermill:format-validator\"`) with the manuscript path from Step 1 in `\u003Cpaper>` and the state file contents in `\u003Cstate>`. It owns the build recipe for every format and reports build status, page count, warnings, undefined references, and overfull\u002Funderfull boxes. Fold its findings into the checklist results.\n\n## Step 4: Present Results\n\nPresent the checklist results:\n\n> **Pre-Flight Report**\n>\n> **Status**: [Ready \u002F Issues found]\n>\n> **Passing**: N\u002FM checks passed\n> **Issues**:\n> 1. [issue + suggested fix]\n> 2. [issue + suggested fix]\n> ...\n\n## Step 5: Fix Issues\n\nOffer to fix issues directly:\n\n- Formatting fixes: Apply them.\n- Content fixes: Suggest specific changes and ask for approval.\n- Style fixes: Propose rewording.\n\n## Step 6: Update State File\n\nAfter all issues are resolved (if `.papermill\u002Fstate.md` does not exist, skip this step and suggest `\u002Fpapermill:init`):\n\n- Set `stage` to `submission` in `.papermill\u002Fstate.md` (Edit tool).\n- Append a timestamped note: \"Pre-flight check passed. Ready for submission to [venue].\"\n\n## Step 7: Suggest Next Steps\n\n> Paper is polished and ready. Final steps:\n>\n> - **Submit**: Follow the venue's submission instructions.\n> - **`\u002Fpapermill:venue`**: If you haven't selected a venue yet, do so now.\n> - **Archive**: Consider creating a git tag marking the submitted version.\n","# Submission Polish\n\nPerform a final quality check on a research paper before submission. This is the last line of defense: catch everything that would annoy a reviewer or cause a desk rejection.\n\n## Step 1: Read Context\n\nRead `.papermill\u002Fstate.md` (Read tool) for:\n- **Venue**: Target venue and its requirements.\n- **Format**: Paper format (latex, markdown, rmarkdown).\n- **Review history**: Outstanding issues from previous reviews.\n\nIf `.papermill\u002Fstate.md` does not exist, the pre-flight check can still run: infer the format from the manuscript files and ask the user for the target venue. The checklist works regardless. Suggest running `\u002Fpapermill:init` to capture venue and format persistently.\n\nRead the complete manuscript (Read tool).\n\n## Step 2: Pre-Flight Checklist\n\nWork through each category systematically. Report issues as they are found.\n\n### Formatting\n- [ ] Paper compiles without errors\n- [ ] No LaTeX warnings (especially undefined references, missing citations)\n- [ ] Page count within venue limits\n- [ ] Correct venue template\u002Fstyle file used\n- [ ] Margins, font size, and spacing match requirements\n- [ ] Line numbers included if required by venue\n- [ ] Anonymous submission if required (no author names in text or metadata)\n\n### Abstract\n- [ ] Word count within venue limits (typically 150-300 words)\n- [ ] Self-contained (no citations, no undefined terms)\n- [ ] States the problem, approach, main result, and significance\n- [ ] Matches the paper's actual content\n\n### Citations and References\n- [ ] All citations resolve (no \"?\" in the PDF)\n- [ ] Bibliography is complete (no missing fields)\n- [ ] Citation style matches venue requirements\n- [ ] All references are cited in the text (no orphan bib entries that should be removed)\n- [ ] All cited works are in the bibliography\n- [ ] Self-citations are reasonable in number\n\n### Figures and Tables\n- [ ] All figures are referenced in the text\n- [ ] Figure captions are self-contained (reader should understand without reading the text)\n- [ ] Resolution is sufficient for print (300+ DPI for raster images)\n- [ ] Color is used accessibly (works in grayscale, colorblind-safe)\n- [ ] Tables have clear headers and units\n\n### Mathematical Content\n- [ ] All symbols are defined before use\n- [ ] Notation is consistent throughout\n- [ ] Equation numbering is correct and referenced\n- [ ] Theorem\u002Fdefinition\u002Fproof environments are properly labeled\n- [ ] No orphan proofs (every proof has a parent theorem\u002Fproposition)\n\n### Writing Quality\n- [ ] No first-person narrative inconsistencies (\"I\" vs \"we\")\n- [ ] Consistent tense usage\n- [ ] No obvious typos or grammatical errors\n- [ ] Acronyms defined on first use\n- [ ] No overly long paragraphs (break up walls of text)\n\n### Metadata\n- [ ] Author names and affiliations are correct\n- [ ] ORCID identifiers included if venue supports them\n- [ ] Keywords\u002Fsubject classification provided\n- [ ] Acknowledgments section present (funding, help, etc.)\n- [ ] Data availability statement if required\n- [ ] Code availability statement if applicable\n\n### Supplementary Material\n- [ ] Appendices are referenced from the main text\n- [ ] Supplementary files are in the required format\n- [ ] Appendix content is not essential to understanding the main paper\n\n## Step 3: Build Verification\n\nLaunch the format validator (Agent tool, `subagent_type: \"papermill:format-validator\"`) with the manuscript path from Step 1 in `\u003Cpaper>` and the state file contents in `\u003Cstate>`. It owns the build recipe for every format and reports build status, page count, warnings, undefined references, and overfull\u002Funderfull boxes. Fold its findings into the checklist results.\n\n## Step 4: Present Results\n\nPresent the checklist results:\n\n> **Pre-Flight Report**\n>\n> **Status**: [Ready \u002F Issues found]\n>\n> **Passing**: N\u002FM checks passed\n> **Issues**:\n> 1. [issue + suggested fix]\n> 2. [issue + suggested fix]\n> ...\n\n## Step 5: Fix Issues\n\nOffer to fix issues directly:\n\n- Formatting fixes: Apply them.\n- Content fixes: Suggest specific changes and ask for approval.\n- Style fixes: Propose rewording.\n\n## Step 6: Update State File\n\nAfter all issues are resolved (if `.papermill\u002Fstate.md` does not exist, skip this step and suggest `\u002Fpapermill:init`):\n\n- Set `stage` to `submission` in `.papermill\u002Fstate.md` (Edit tool).\n- Append a timestamped note: \"Pre-flight check passed. Ready for submission to [venue].\"\n\n## Step 7: Suggest Next Steps\n\n> Paper is polished and ready. Final steps:\n>\n> - **Submit**: Follow the venue's submission instructions.\n> - **`\u002Fpapermill:venue`**: If you haven't selected a venue yet, do so now.\n> - **Archive**: Consider creating a git tag marking the submitted version.\n",{"name":5,"description":7},"main","f6f3133da90d79585262853f985437619b96f30d","papermill\u002Fskills\u002Fpolish","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil","https:\u002F\u002Fgithub.com\u002FAbdulqudduz","Hi there! 👋\r\nI'm Muhammed Abdulquddus, a software developer passionate about Flutter and Python, based in Abuja, Nigeria.","2026-10-23 13:31:03",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Abdulqudduz\u002Fclaude-anvil --skill polish",{"tool":37,"command":38},"bunx","bunx skills add Abdulqudduz\u002Fclaude-anvil --skill polish",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Abdulqudduz\u002Fclaude-anvil --skill polish","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fpapermill\u002Fskills\u002Fpolish\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7FDMZAFJXWE6EQJRZE0RQCA","worldsmith-methodology","Use when working in a project with a worldbuilding documentation ecosystem (docs\u002F or lore\u002F directory). Provides the documentation-first methodology: canonical hierarchy, doc roles (timeline, lore, characters, systems), propagation discipline, and the dual canonical and exploratory workflow.","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fworldsmith\u002Fskills\u002Fworldsmith-methodology\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7FDMTEXZNE8RXCTCJVXFE4P","prose-craft","Use when writing fiction, editing fiction prose, reviewing chapters, or drafting scenes. Covers prose craft, dialogue mechanics, scene structure, and common failure modes in AI-assisted fiction. Trigger phrases: \"write fiction\", \"edit chapter\", \"prose review\", \"scene draft\", \"dialogue check\", \"fiction craft\", \"edit this scene\", \"review my prose\".","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fworldsmith\u002Fskills\u002Fprose-craft\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7FDMN0VRXW0G92593BJ5DTS","vista","This skill should be used when the user asks about research directions, open problems, future work, or follow-up research from the academic literature. Trigger phrases include \"open problems in X\", \"what's next for Y\", \"future work for paper Z\", \"research directions on T\", \"salient follow-up research\", \"what should I work on next in\", \"find me follow-up research unrelated to my prior work\", \"broad survey of W\", \"neglected directions in V\". Routes the request to the right Vista MCP tool, reads back the structured paper sections, and synthesizes research directions in the conversation.","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fvista\u002Fskills\u002Fvista\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7FDMHKJX5F49JEGRPZXWQH9","synthesize","Make a research-agent run conclude and write synthesis.md (outcome, key findings, failed approaches, open questions, recommendations). Signals a live researcher to wrap up, or launches one in synthesis mode when none is running. Use when results are good enough or the agent is stalling.","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fresearch-agent\u002Fskills\u002Fsynthesize\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7FDMDJT58GYN0YHMWPH3RH5","status","Show the current state of a research-agent run from .research\u002F: liveness, cycles and budget, sub-problem and hypothesis statuses, eval trend, current focus, and branches. Read-only.","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fresearch-agent\u002Fskills\u002Fstatus\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7FDM90XM3H52XNDNKBB5SAP","resume","Resume an interrupted research-agent run from .research\u002F. Re-launches the researcher to reload its structured state and continue from the current focus, optionally on a named branch or with a new budget. Use after a session restart, crash, or explicit pause.","https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fresearch-agent\u002Fskills\u002Fresume\u002FSKILL.md",[],[]]