[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FDKQHK5RVTM7722YTGWNZQ":3,"skill-same:01M7FDKQHK5RVTM7722YTGWNZQ":46},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7FDKQHK5RVTM7722YTGWNZQ","r-publish",null,"Orchestrate the full R package publication pipeline: CRAN (and R-universe) for distribution, JOSS for a peer-reviewed DOI, optionally a JSS methods paper. Use for \"publish my R package\". For a Python package use pypi-publish; for a standalone LaTeX paper (no DESCRIPTION) use the papermill plugin instead.","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\u002Fpub-pipeline\u002Fskills\u002Fr-publish\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: r-publish\ndescription: >-\n  Orchestrate the full R package publication pipeline: CRAN (and\n  R-universe) for distribution, JOSS for a peer-reviewed DOI, optionally a\n  JSS methods paper. Use for \"publish my R package\". For a Python package\n  use pypi-publish; for a standalone LaTeX paper (no DESCRIPTION) use the\n  papermill plugin instead.\nargument-hint: \"[package path]\"\n---\n\n# R Package Publication Pipeline\n\nOrchestrate CRAN submission, then a JOSS paper, then optionally a JSS methods paper. This skill coordinates `\u002Fpub-pipeline:cran-audit`, `\u002Fpub-pipeline:joss-audit`, and `\u002Fpub-pipeline:joss-draft` into one workflow. Package root: `$ARGUMENTS` if given, else the current directory. If it has no `DESCRIPTION` with a `Package:` field, say so: point to `\u002Fpub-pipeline:pypi-publish` for a `pyproject.toml` project, or the papermill plugin for a `.tex` paper.\n\n## Strategy\n\n1. **CRAN**: distribution, discoverability, `install.packages()`.\n2. **JOSS**: quick DOI, peer-reviewed citation, Crossref\u002FGoogle Scholar indexing.\n3. **JSS** (optional): high-prestige methods paper, Web of Science indexed.\n\nEach stage builds on the previous: CRAN gives legitimacy, JOSS a citable DOI, JSS academic weight for the methodology.\n\n## Workflow\n\n### Phase 1: Assess Current State\n\n**Load user config** (Read tool): read `.claude\u002Fpub-pipeline.local.md` if it exists. Extract author metadata, `r.domain`, `r.audience`, `r.competitors`, `r.targets`, `r.universe`, `r.dependency_chain`, and `related_work`. Companion papers and preprints in `related_work` shape the JOSS paper (cite them) and the overall strategy. If the file is missing, offer to create it from `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fuser-config-template.md`.\n\n1. Read `DESCRIPTION` for package metadata (Read tool).\n2. Check git history (Bash tool).\n3. Look for existing `paper.md`, `CITATION.cff` (Glob tool).\n4. CRAN status: fetch `https:\u002F\u002Fcran.r-project.org\u002Fpackage={name}` (WebFetch tool).\n5. R-universe status (Bash tool, structured JSON; `{user}` is `r.universe`, skip if unset): `curl -s https:\u002F\u002F{user}.r-universe.dev\u002Fapi\u002Fpackages\u002F{name}` returns `Version`, `_registered`, and `_status` (build result); a 404 means the package is not in that universe.\n6. JOSS status: search joss.theoj.org (WebSearch tool).\n\n**Dependency chain** (Bash tool): for each non-base, non-recommended package in `Imports`, `Depends`, and `LinkingTo`:\n```bash\nRscript -e 'ap \u003C- available.packages(); cat(\"PKG_NAME\" %in% rownames(ap))'\n```\nA dependency missing from CRAN is a hard blocker for `R CMD check --as-cran`. Present the submission order (dependencies first), cross-check `r.dependency_chain`, and offer to switch to the dependency package.\n\n**CI status**: if `.github\u002Fworkflows\u002F` exists (Glob tool), run `gh run list --limit 3 --json conclusion,name,headBranch` (Bash tool). Failing CI undermines both CRAN confidence and JOSS reviewer trust.\n\nClassify the package:\n\n| State | Next Step |\n|-------|-----------|\n| Dependencies not on CRAN | Start with the dependency package |\n| On R-universe only, not on CRAN | CRAN audit; R-universe already gives installable binaries, so JOSS can proceed in parallel |\n| Not on CRAN, no paper.md | Start with CRAN audit |\n| On CRAN, no paper.md | Start with JOSS audit |\n| On CRAN, has paper.md | Review paper, prepare JOSS submission |\n| On CRAN, published in JOSS | Consider JSS (if substantive methodology) |\n\nBioinformatics packages (genomics, proteomics) usually belong on Bioconductor instead of CRAN, which has its own submission process.\n\nPresent the assessment and confirm the plan before proceeding.\n\n### Phase 2: CRAN Readiness\n\nRun `\u002Fpub-pipeline:cran-audit`. If the package is not ready: present the gap report, fix automatable issues, guide manual fixes, re-audit. Skip to Phase 3 if already on CRAN.\n\n**Submission steps** (when ready):\n1. `usethis::use_version(\"minor\")` to bump the version (commit pending changes first; it prompts otherwise).\n2. `devtools::check(args = \"--as-cran\")` for the final check.\n3. Other platforms: `devtools::check_win_devel()` (win-builder) and `rhub::rhub_check()` (R-hub v2; one-time `rhub::rhub_setup()`; `rhub::rc_submit()` for non-GitHub repos).\n4. **Submit (user runs this)**: `devtools::submit_cran()` asks interactive confirmation questions that the Bash tool cannot answer. Hand it to the user to type in the prompt:\n   ```\n   ! Rscript -e 'devtools::submit_cran()'\n   ```\n   or to run in an interactive R session. Then they confirm via the emailed link.\n5. After acceptance: `usethis::use_github_release()`, then `usethis::use_dev_version()`.\n\n**If CRAN rejects**: read the email carefully, fix every identified issue (not a subset), re-run `devtools::check(args = \"--as-cran\")`, note the fixes in `cran-comments.md`, and resubmit. Do not resubmit more than once a week unless CRAN asks.\n\n### Phase 3: JOSS Readiness\n\nRun `\u002Fpub-pipeline:joss-audit`. Common gaps: under 6 months of public history, no `CONTRIBUTING.md`, no `paper.md`. If there is no paper, go to Phase 4.\n\n### Phase 4: Draft JOSS Paper\n\nRun `\u002Fpub-pipeline:joss-draft`. Then present the draft, iterate on feedback, re-run `\u002Fpub-pipeline:joss-audit` for a full checklist review, and commit the paper to the repository.\n\n### Phase 5: JOSS Submission\n\n1. **Pre-submission**: package installable (ideally on CRAN), `paper.md` and `paper.bib` committed, audit passes, ORCID for all authors.\n2. **Submit** at https:\u002F\u002Fjoss.theoj.org\u002Fpapers\u002Fnew with the repository URL; wait for the pre-review issue.\n3. **During review** (typically 4-12 weeks): respond promptly, make requested changes, re-run the audit.\n4. **Post-acceptance**: tag a release; archive it on Zenodo (enable the Zenodo GitHub integration for the repository, publish a GitHub release with `gh release create`, copy the deposit DOI); post the version and archive DOI in the review issue. JOSS then assigns the paper DOI via Crossref.\n\n### Phase 6: JSS Consideration (Optional)\n\n**Appropriate when** the package implements novel statistical methodology with substantive mathematical content, the paper would be 20-50 pages of methods plus software description, and the audience is academic statisticians.\n\n**Not appropriate when** the package is primarily a software tool (JOSS covers it), the mathematics is textbook material, or the paper would just be a longer JOSS paper.\n\nIf appropriate: JSS uses the `rticles::jss_article` format, is indexed in Web of Science, and reviews take 6-18 months. The `papermill:writer` agent can draft long-form academic papers.\n\n## Decision Helpers\n\n| Criterion | Minimum for CRAN | Minimum for JOSS |\n|-----------|-----------------|-----------------|\n| License | OSI-approved | OSI-approved |\n| Tests | Pass R CMD check | Automated test suite |\n| Docs | Man pages for exports | README, examples, API docs |\n| History | Any | 6+ months public, sustained |\n| Users | Not required | Research impact evidence |\n| Paper | Not required | 750-1750 word paper.md |\n\n| Stage | Duration |\n|-------|----------|\n| CRAN prep and audit | 1-3 days |\n| CRAN review | 1-7 days (usually 1-2) |\n| JOSS prep and paper | 1-2 days |\n| JOSS review | 4-12 weeks |\n| JSS prep and paper | 2-4 weeks |\n| JSS review | 6-18 months |\n\n## Reference Files\n\n- **`${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fcran-reference.md`**: CRAN Repository Policy, submission workflow, common rejections\n- **`${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fjoss-reference.md`**: JOSS requirements, reviewer checklist, paper format\n\n## Important Notes\n\n- Never submit to JOSS before the package is installable (ideally on CRAN).\n- CRAN and JOSS are complementary: CRAN for distribution, JOSS for citation.\n- The user controls the pace: present options, don't push.\n","# R Package Publication Pipeline\n\nOrchestrate CRAN submission, then a JOSS paper, then optionally a JSS methods paper. This skill coordinates `\u002Fpub-pipeline:cran-audit`, `\u002Fpub-pipeline:joss-audit`, and `\u002Fpub-pipeline:joss-draft` into one workflow. Package root: `$ARGUMENTS` if given, else the current directory. If it has no `DESCRIPTION` with a `Package:` field, say so: point to `\u002Fpub-pipeline:pypi-publish` for a `pyproject.toml` project, or the papermill plugin for a `.tex` paper.\n\n## Strategy\n\n1. **CRAN**: distribution, discoverability, `install.packages()`.\n2. **JOSS**: quick DOI, peer-reviewed citation, Crossref\u002FGoogle Scholar indexing.\n3. **JSS** (optional): high-prestige methods paper, Web of Science indexed.\n\nEach stage builds on the previous: CRAN gives legitimacy, JOSS a citable DOI, JSS academic weight for the methodology.\n\n## Workflow\n\n### Phase 1: Assess Current State\n\n**Load user config** (Read tool): read `.claude\u002Fpub-pipeline.local.md` if it exists. Extract author metadata, `r.domain`, `r.audience`, `r.competitors`, `r.targets`, `r.universe`, `r.dependency_chain`, and `related_work`. Companion papers and preprints in `related_work` shape the JOSS paper (cite them) and the overall strategy. If the file is missing, offer to create it from `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fuser-config-template.md`.\n\n1. Read `DESCRIPTION` for package metadata (Read tool).\n2. Check git history (Bash tool).\n3. Look for existing `paper.md`, `CITATION.cff` (Glob tool).\n4. CRAN status: fetch `https:\u002F\u002Fcran.r-project.org\u002Fpackage={name}` (WebFetch tool).\n5. R-universe status (Bash tool, structured JSON; `{user}` is `r.universe`, skip if unset): `curl -s https:\u002F\u002F{user}.r-universe.dev\u002Fapi\u002Fpackages\u002F{name}` returns `Version`, `_registered`, and `_status` (build result); a 404 means the package is not in that universe.\n6. JOSS status: search joss.theoj.org (WebSearch tool).\n\n**Dependency chain** (Bash tool): for each non-base, non-recommended package in `Imports`, `Depends`, and `LinkingTo`:\n```bash\nRscript -e 'ap \u003C- available.packages(); cat(\"PKG_NAME\" %in% rownames(ap))'\n```\nA dependency missing from CRAN is a hard blocker for `R CMD check --as-cran`. Present the submission order (dependencies first), cross-check `r.dependency_chain`, and offer to switch to the dependency package.\n\n**CI status**: if `.github\u002Fworkflows\u002F` exists (Glob tool), run `gh run list --limit 3 --json conclusion,name,headBranch` (Bash tool). Failing CI undermines both CRAN confidence and JOSS reviewer trust.\n\nClassify the package:\n\n| State | Next Step |\n|-------|-----------|\n| Dependencies not on CRAN | Start with the dependency package |\n| On R-universe only, not on CRAN | CRAN audit; R-universe already gives installable binaries, so JOSS can proceed in parallel |\n| Not on CRAN, no paper.md | Start with CRAN audit |\n| On CRAN, no paper.md | Start with JOSS audit |\n| On CRAN, has paper.md | Review paper, prepare JOSS submission |\n| On CRAN, published in JOSS | Consider JSS (if substantive methodology) |\n\nBioinformatics packages (genomics, proteomics) usually belong on Bioconductor instead of CRAN, which has its own submission process.\n\nPresent the assessment and confirm the plan before proceeding.\n\n### Phase 2: CRAN Readiness\n\nRun `\u002Fpub-pipeline:cran-audit`. If the package is not ready: present the gap report, fix automatable issues, guide manual fixes, re-audit. Skip to Phase 3 if already on CRAN.\n\n**Submission steps** (when ready):\n1. `usethis::use_version(\"minor\")` to bump the version (commit pending changes first; it prompts otherwise).\n2. `devtools::check(args = \"--as-cran\")` for the final check.\n3. Other platforms: `devtools::check_win_devel()` (win-builder) and `rhub::rhub_check()` (R-hub v2; one-time `rhub::rhub_setup()`; `rhub::rc_submit()` for non-GitHub repos).\n4. **Submit (user runs this)**: `devtools::submit_cran()` asks interactive confirmation questions that the Bash tool cannot answer. Hand it to the user to type in the prompt:\n   ```\n   ! Rscript -e 'devtools::submit_cran()'\n   ```\n   or to run in an interactive R session. Then they confirm via the emailed link.\n5. After acceptance: `usethis::use_github_release()`, then `usethis::use_dev_version()`.\n\n**If CRAN rejects**: read the email carefully, fix every identified issue (not a subset), re-run `devtools::check(args = \"--as-cran\")`, note the fixes in `cran-comments.md`, and resubmit. Do not resubmit more than once a week unless CRAN asks.\n\n### Phase 3: JOSS Readiness\n\nRun `\u002Fpub-pipeline:joss-audit`. Common gaps: under 6 months of public history, no `CONTRIBUTING.md`, no `paper.md`. If there is no paper, go to Phase 4.\n\n### Phase 4: Draft JOSS Paper\n\nRun `\u002Fpub-pipeline:joss-draft`. Then present the draft, iterate on feedback, re-run `\u002Fpub-pipeline:joss-audit` for a full checklist review, and commit the paper to the repository.\n\n### Phase 5: JOSS Submission\n\n1. **Pre-submission**: package installable (ideally on CRAN), `paper.md` and `paper.bib` committed, audit passes, ORCID for all authors.\n2. **Submit** at https:\u002F\u002Fjoss.theoj.org\u002Fpapers\u002Fnew with the repository URL; wait for the pre-review issue.\n3. **During review** (typically 4-12 weeks): respond promptly, make requested changes, re-run the audit.\n4. **Post-acceptance**: tag a release; archive it on Zenodo (enable the Zenodo GitHub integration for the repository, publish a GitHub release with `gh release create`, copy the deposit DOI); post the version and archive DOI in the review issue. JOSS then assigns the paper DOI via Crossref.\n\n### Phase 6: JSS Consideration (Optional)\n\n**Appropriate when** the package implements novel statistical methodology with substantive mathematical content, the paper would be 20-50 pages of methods plus software description, and the audience is academic statisticians.\n\n**Not appropriate when** the package is primarily a software tool (JOSS covers it), the mathematics is textbook material, or the paper would just be a longer JOSS paper.\n\nIf appropriate: JSS uses the `rticles::jss_article` format, is indexed in Web of Science, and reviews take 6-18 months. The `papermill:writer` agent can draft long-form academic papers.\n\n## Decision Helpers\n\n| Criterion | Minimum for CRAN | Minimum for JOSS |\n|-----------|-----------------|-----------------|\n| License | OSI-approved | OSI-approved |\n| Tests | Pass R CMD check | Automated test suite |\n| Docs | Man pages for exports | README, examples, API docs |\n| History | Any | 6+ months public, sustained |\n| Users | Not required | Research impact evidence |\n| Paper | Not required | 750-1750 word paper.md |\n\n| Stage | Duration |\n|-------|----------|\n| CRAN prep and audit | 1-3 days |\n| CRAN review | 1-7 days (usually 1-2) |\n| JOSS prep and paper | 1-2 days |\n| JOSS review | 4-12 weeks |\n| JSS prep and paper | 2-4 weeks |\n| JSS review | 6-18 months |\n\n## Reference Files\n\n- **`${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fcran-reference.md`**: CRAN Repository Policy, submission workflow, common rejections\n- **`${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fjoss-reference.md`**: JOSS requirements, reviewer checklist, paper format\n\n## Important Notes\n\n- Never submit to JOSS before the package is installable (ideally on CRAN).\n- CRAN and JOSS are complementary: CRAN for distribution, JOSS for citation.\n- The user controls the pace: present options, don't push.\n",{"name":5,"description":7,"argument-hint":24},"[package path]","main","f6f3133da90d79585262853f985437619b96f30d","pub-pipeline\u002Fskills\u002Fr-publish","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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Abdulqudduz\u002Fclaude-anvil --skill r-publish",{"tool":38,"command":39},"bunx","bunx skills add Abdulqudduz\u002Fclaude-anvil --skill r-publish",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Abdulqudduz\u002Fclaude-anvil --skill r-publish","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fpub-pipeline\u002Fskills\u002Fr-publish\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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",[],[]]