[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FDGWYC01GP7SW4FQCE08T2":3,"skill-same:01M7FDGWYC01GP7SW4FQCE08T2":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},"01M7FDGWYC01GP7SW4FQCE08T2","review",null,"Launch a multi-agent editorial review with 8 specialists (2 literature scouts plus 6 domain reviewers) orchestrated by an area-chair agent. Produces a unified report plus specialist reports in .papermill\u002Freviews\u002F. Updates .papermill\u002Fstate.md.","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\u002Freview\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: review\ndescription: >-\n  Launch a multi-agent editorial review with 8 specialists (2 literature\n  scouts plus 6 domain reviewers) orchestrated by an area-chair agent.\n  Produces a unified report plus specialist reports in .papermill\u002Freviews\u002F.\n  Updates .papermill\u002Fstate.md.\n---\n\n# Multi-Agent Editorial Review\n\nLaunch a comprehensive multi-agent review of a research paper. The review system uses 8 specialist agents orchestrated by an area chair to evaluate logic, novelty, methodology, prose, citations, and formatting: grounded in literature context.\n\n## Step 1: Read Context\n\nRead `.papermill\u002Fstate.md` (Read tool) for:\n- **Thesis**: What the paper claims (the review checks if the paper delivers).\n- **Venue**: Target venue (review against its standards).\n- **Review history**: Previous reviews and their findings.\n- **Format**: Paper format (latex, markdown, rmarkdown).\n\nIf `.papermill\u002Fstate.md` does not exist, the review can still proceed by reading the manuscript directly, but the review will be less targeted without thesis and venue context. Note this limitation to the user and suggest running `\u002Fpapermill:init` first for best results.\n\n## Step 2: Identify the Manuscript\n\nLocate the manuscript files:\n1. Check `.papermill\u002Fstate.md` for format and any recorded manuscript path.\n2. Scan for manuscript files (Glob tool): `*.tex`, `*.Rmd`, `paper.md`, `manuscript.md`.\n3. Identify the main file and any supporting files (bibliography, figures, included files).\n\nRead the manuscript to confirm it has enough content for review.\n\n## Step 3: Ask for Focus Areas\n\nBefore launching the review, ask the user:\n\n> I'll launch a multi-agent review with specialists covering:\n> - **Logic & proofs**: mathematical correctness and argument structure\n> - **Novelty**: contribution evaluation against the literature\n> - **Methodology**: experimental design and statistical rigor\n> - **Prose**: writing quality and narrative structure\n> - **Citations**: reference accuracy and completeness\n> - **Formatting**: build verification and venue compliance\n>\n> Are there specific areas you want me to focus on, or should I run the full review?\n\nIf the user specifies focus areas, note them for the orchestrator. If they want the full review, proceed with all specialists.\n\n## Step 4: Launch the Reviewer Orchestrator\n\nLaunch the **reviewer** agent (Agent tool with `subagent_type: \"papermill:reviewer\"`).\n\nPass the agent:\n- Path to the manuscript file(s)\n- Path to `.papermill\u002Fstate.md` (if it exists)\n- Any user-specified focus areas or tone preferences\n- The thesis statement and target venue (if known)\n\nThe agent will:\n1. Read the paper and produce a comprehension summary\n2. Spawn 2 literature scouts in parallel for field context\n3. Spawn 6 specialist reviewers in parallel\n4. Cross-verify critical findings\n5. Write individual specialist reports and a unified report to `.papermill\u002Freviews\u002FYYYY-MM-DD-HHMM\u002F`, with stable finding ids (F1, F2, ...)\n6. Return the `review.md` path, recommendation, and counts\n\n## Step 5: Present Results\n\nAfter the agent completes, read the `review.md` path it returned (Read tool).\n\nPresent a summary to the user:\n\n> **Review Complete**\n>\n> **Recommendation**: [ready | minor-revision | major-revision | not-ready]\n>\n> | Severity | Count |\n> |----------|-------|\n> | Critical | N |\n> | Major | M |\n> | Minor | P |\n> | Suggestions | Q |\n>\n> **Top findings:**\n> 1. [Most important finding]\n> 2. [Second most important finding]\n> 3. [Third most important finding]\n>\n> The full report is at `[returned review.md path]`.\n> Individual specialist reports are in the same directory.\n\nThen ask: \"Would you like to go through the findings in detail, or address the critical issues first?\"\n\n## Step 6: Update State File\n\nUpdate `.papermill\u002Fstate.md` (Edit tool). If `.papermill\u002Fstate.md` does not exist, skip this step and suggest `\u002Fpapermill:init`. Updates:\n\nAdd a review record to `review_history`:\n\n```yaml\nreview_history:\n  - date: \"YYYY-MM-DD\"\n    type: \"multi-agent-review\"\n    findings_critical: K\n    findings_major: N\n    findings_minor: M\n    recommendation: \"ready | minor-revision | major-revision | not-ready\"\n    notes: \"Brief summary of key findings\"\n    report_path: \"[returned review.md path]\"\n```\n\nAdvance `stage` to `review` unless it is already `review` or `submission` (never move it backward).\n\nAppend a timestamped note to the markdown body.\n\n## Step 7: Suggest Next Steps\n\nBased on the recommendation, suggest the most relevant next step:\n\n- **Ready for submission** → `\u002Fpapermill:polish` to prepare, then `\u002Fpapermill:venue` if no venue is selected yet.\n- **Minor revision** → `\u002Fpapermill:revise` to apply the fixes with verification, then re-run `\u002Fpapermill:review`.\n- **Major revision** → `\u002Fpapermill:revise` for the concrete findings. If issues are structural, suggest `\u002Fpapermill:outline` first; if issues are with the argument, suggest `\u002Fpapermill:thesis`. Then re-run `\u002Fpapermill:review`.\n- **Not ready** → Identify the root cause. Weak thesis → `\u002Fpapermill:thesis`. Insufficient evidence → `\u002Fpapermill:experiment` or `\u002Fpapermill:simulation`. Missing related work → `\u002Fpapermill:prior-art`. Proof gaps → `\u002Fpapermill:proof`.\n","# Multi-Agent Editorial Review\n\nLaunch a comprehensive multi-agent review of a research paper. The review system uses 8 specialist agents orchestrated by an area chair to evaluate logic, novelty, methodology, prose, citations, and formatting: grounded in literature context.\n\n## Step 1: Read Context\n\nRead `.papermill\u002Fstate.md` (Read tool) for:\n- **Thesis**: What the paper claims (the review checks if the paper delivers).\n- **Venue**: Target venue (review against its standards).\n- **Review history**: Previous reviews and their findings.\n- **Format**: Paper format (latex, markdown, rmarkdown).\n\nIf `.papermill\u002Fstate.md` does not exist, the review can still proceed by reading the manuscript directly, but the review will be less targeted without thesis and venue context. Note this limitation to the user and suggest running `\u002Fpapermill:init` first for best results.\n\n## Step 2: Identify the Manuscript\n\nLocate the manuscript files:\n1. Check `.papermill\u002Fstate.md` for format and any recorded manuscript path.\n2. Scan for manuscript files (Glob tool): `*.tex`, `*.Rmd`, `paper.md`, `manuscript.md`.\n3. Identify the main file and any supporting files (bibliography, figures, included files).\n\nRead the manuscript to confirm it has enough content for review.\n\n## Step 3: Ask for Focus Areas\n\nBefore launching the review, ask the user:\n\n> I'll launch a multi-agent review with specialists covering:\n> - **Logic & proofs**: mathematical correctness and argument structure\n> - **Novelty**: contribution evaluation against the literature\n> - **Methodology**: experimental design and statistical rigor\n> - **Prose**: writing quality and narrative structure\n> - **Citations**: reference accuracy and completeness\n> - **Formatting**: build verification and venue compliance\n>\n> Are there specific areas you want me to focus on, or should I run the full review?\n\nIf the user specifies focus areas, note them for the orchestrator. If they want the full review, proceed with all specialists.\n\n## Step 4: Launch the Reviewer Orchestrator\n\nLaunch the **reviewer** agent (Agent tool with `subagent_type: \"papermill:reviewer\"`).\n\nPass the agent:\n- Path to the manuscript file(s)\n- Path to `.papermill\u002Fstate.md` (if it exists)\n- Any user-specified focus areas or tone preferences\n- The thesis statement and target venue (if known)\n\nThe agent will:\n1. Read the paper and produce a comprehension summary\n2. Spawn 2 literature scouts in parallel for field context\n3. Spawn 6 specialist reviewers in parallel\n4. Cross-verify critical findings\n5. Write individual specialist reports and a unified report to `.papermill\u002Freviews\u002FYYYY-MM-DD-HHMM\u002F`, with stable finding ids (F1, F2, ...)\n6. Return the `review.md` path, recommendation, and counts\n\n## Step 5: Present Results\n\nAfter the agent completes, read the `review.md` path it returned (Read tool).\n\nPresent a summary to the user:\n\n> **Review Complete**\n>\n> **Recommendation**: [ready | minor-revision | major-revision | not-ready]\n>\n> | Severity | Count |\n> |----------|-------|\n> | Critical | N |\n> | Major | M |\n> | Minor | P |\n> | Suggestions | Q |\n>\n> **Top findings:**\n> 1. [Most important finding]\n> 2. [Second most important finding]\n> 3. [Third most important finding]\n>\n> The full report is at `[returned review.md path]`.\n> Individual specialist reports are in the same directory.\n\nThen ask: \"Would you like to go through the findings in detail, or address the critical issues first?\"\n\n## Step 6: Update State File\n\nUpdate `.papermill\u002Fstate.md` (Edit tool). If `.papermill\u002Fstate.md` does not exist, skip this step and suggest `\u002Fpapermill:init`. Updates:\n\nAdd a review record to `review_history`:\n\n```yaml\nreview_history:\n  - date: \"YYYY-MM-DD\"\n    type: \"multi-agent-review\"\n    findings_critical: K\n    findings_major: N\n    findings_minor: M\n    recommendation: \"ready | minor-revision | major-revision | not-ready\"\n    notes: \"Brief summary of key findings\"\n    report_path: \"[returned review.md path]\"\n```\n\nAdvance `stage` to `review` unless it is already `review` or `submission` (never move it backward).\n\nAppend a timestamped note to the markdown body.\n\n## Step 7: Suggest Next Steps\n\nBased on the recommendation, suggest the most relevant next step:\n\n- **Ready for submission** → `\u002Fpapermill:polish` to prepare, then `\u002Fpapermill:venue` if no venue is selected yet.\n- **Minor revision** → `\u002Fpapermill:revise` to apply the fixes with verification, then re-run `\u002Fpapermill:review`.\n- **Major revision** → `\u002Fpapermill:revise` for the concrete findings. If issues are structural, suggest `\u002Fpapermill:outline` first; if issues are with the argument, suggest `\u002Fpapermill:thesis`. Then re-run `\u002Fpapermill:review`.\n- **Not ready** → Identify the root cause. Weak thesis → `\u002Fpapermill:thesis`. Insufficient evidence → `\u002Fpapermill:experiment` or `\u002Fpapermill:simulation`. Missing related work → `\u002Fpapermill:prior-art`. Proof gaps → `\u002Fpapermill:proof`.\n",{"name":5,"description":7},"main","f6f3133da90d79585262853f985437619b96f30d","papermill\u002Fskills\u002Freview","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 review",{"tool":37,"command":38},"bunx","bunx skills add Abdulqudduz\u002Fclaude-anvil --skill review",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Abdulqudduz\u002Fclaude-anvil --skill review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fpapermill\u002Fskills\u002Freview\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",[],[]]