[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FDK44YB0KXET8MXRCB5T2H":3,"skill-same:01M7FDK44YB0KXET8MXRCB5T2H":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},"01M7FDK44YB0KXET8MXRCB5T2H","cran-audit",null,"Audit an R package against CRAN Repository Policy and submission requirements. Produces a gap report with Critical (must fix), Warnings (should fix), and pass\u002Ffail assessment per requirement type. Offers automated fixes where possible.","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\u002Fcran-audit\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: cran-audit\ndescription: >-\n  Audit an R package against CRAN Repository Policy and submission\n  requirements. Produces a gap report with Critical (must fix), Warnings\n  (should fix), and pass\u002Ffail assessment per requirement type. Offers\n  automated fixes where possible.\nargument-hint: \"[package path]\"\n---\n\n# CRAN Submission Audit\n\nAudit an R package against CRAN Repository Policy requirements and produce a structured gap report. This skill evaluates package structure, DESCRIPTION metadata, documentation, code quality, and test coverage against the full CRAN checklist.\n\n## Workflow\n\n### 1. Locate the Package\n\nIdentify the R package to audit. Look for `DESCRIPTION` file in the current working directory or a specified path. If no R package is found, ask the user which package to audit.\n\n### 1b. Load User Config\n\nRead `.claude\u002Fpub-pipeline.local.md` if it exists (Read tool). Extract author metadata and package context from YAML frontmatter. If the file is missing, inform the user and offer to create one from the template at `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fuser-config-template.md`.\n\n### 1c. Verify Dependency Availability\n\nBefore running the full audit, check that all dependencies are available on CRAN (Bash tool):\n\n1. Parse `Imports`, `Depends`, and `LinkingTo` fields from `DESCRIPTION`\n2. For each dependency that is not a base or recommended package, verify it exists on CRAN:\n```bash\nRscript -e 'ap \u003C- available.packages(); cat(\"PKG_NAME\" %in% rownames(ap))'\n```\n3. For dependencies with version requirements (e.g., `pkg (>= 2.0)`), verify the requirement is satisfiable:\n```bash\nRscript -e 'ap \u003C- available.packages(); cat(ap[\"PKG_NAME\", \"Version\"])'\n```\nCompare the available version against the minimum required version.\n\nIf any dependency is **not on CRAN**, flag it as a **hard blocker** in the gap report and stop here: the package cannot pass `R CMD check --as-cran` until all dependencies are available. Recommend the user publish the missing dependency first or switch to a CRAN-available alternative.\n\n### 2. Gather Package State\n\nRun these checks in parallel where possible:\n\n**Regenerate documentation** (Bash tool):\nRun `Rscript -e 'devtools::document()'` to ensure NAMESPACE and `man\u002F` files are current before auditing them. This prevents false negatives from stale roxygen output.\n\n**Package metadata** (Read tool):\n- Read `DESCRIPTION`: check all required fields\n- Read `NAMESPACE`: verify auto-generation by roxygen2\n- Read `LICENSE` or `LICENSE.md`: verify OSI-approved license\n- Check for `NEWS.md`, `cran-comments.md`, `README.md`\n\n**Code quality** (Grep\u002FGlob tools):\n- Search for `q()` calls in R code\n- Search for `.Internal()`, `:::` accessing base internals\n- Search for writes outside `tempdir()` \u002F `tools::R_user_dir()`\n- Check that Suggested packages are used conditionally (`if (requireNamespace(...))`)\n- Verify no binary executables in source\n- Search for `options()` or `par()` calls that don't restore state via `on.exit()` or `withr`\n- Run `urlchecker::url_check()` to verify all URLs are valid and HTTPS\n\n**Documentation** (Grep\u002FGlob tools):\n- Check all exported functions have `@returns` roxygen tag\n- Check all exported functions have `@examples` roxygen tag\n- Verify `man\u002F` directory exists with `.Rd` files\n\n**R CMD check** (Bash tool):\n```bash\ncd \u002Fpath\u002Fto\u002Fpackage && Rscript -e 'devtools::check(args = \"--as-cran\")'\n```\n\n**Test coverage** (Bash tool):\n```bash\ncd \u002Fpath\u002Fto\u002Fpackage && Rscript -e 'covr::package_coverage()'\n```\n\n### 3. Evaluate Against Checklist\n\nScore each item from the CRAN checklist as PASS, FAIL, or WARN. Consult the full checklist in `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fcran-reference.md` for detailed requirements.\n\nKey categories to evaluate:\n\n| Category | Key Checks |\n|----------|-----------|\n| **DESCRIPTION** | Title case, no period, informative Description, Authors@R with roles, valid License |\n| **Dependencies** | Imports from CRAN\u002FBioconductor only, conditional Suggests usage |\n| **Code behavior** | No q(), no .Internal, no writing outside tempdir, no global env modification |\n| **Documentation** | All exports have @returns and @examples, vignettes build |\n| **Examples** | `\\dontrun{}` only for truly non-runnable code; prefer `\\donttest{}` for slow examples (still run by `--as-cran` since R 4.0.0, so they must pass) |\n| **Side effects** | `options()`\u002F`par()` restored via `on.exit()` or `withr`; no persistent state changes |\n| **Size** | Tarball ideally \u003C10MB (\"if possible\"), data and docs each \u003C5MB as a general rule, examples run in seconds |\n| **Cross-platform** | Portable code, no OS-specific assumptions |\n| **Testing** | R CMD check clean (0E\u002F0W), notes explained |\n| **URLs** | All URLs valid and using HTTPS |\n\n### 4. Produce Gap Report\n\nFormat the report as:\n\n```markdown\n# CRAN Audit Report: {package name} v{version}\n\n## Summary\n- **Status**: READY \u002F NEEDS WORK \u002F NOT READY\n- **Score**: X\u002FY checks passed\n- **Blockers**: N critical issues\n\n## Critical (Must Fix)\n1. [Issue description] ([file:line]): [how to fix]\n\n## Warnings (Should Fix)\n1. [Issue description] ([file:line]): [recommendation]\n\n## Passed\n- [Check name] ✓\n\n## R CMD Check Results\n[Paste relevant output]\n\n## Recommended Next Steps\n1. [Ordered list of actions]\n```\n\n### 5. Offer to Fix\n\nAfter presenting the report, offer to fix issues that can be automated:\n- Add missing `@returns` tags\n- Add `cran-comments.md` if missing\n- Fix Title\u002FDescription formatting\n- Add conditional `requireNamespace()` checks\n- Create `NEWS.md` if missing\n- Replace `\\dontrun{}` with `\\donttest{}` where appropriate\n\n## Reference Files\n\nFor the complete CRAN policy checklist and submission workflow, consult:\n- **`${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fcran-reference.md`**: Full CRAN Repository Policy reference with pre-submission checklist, submission workflow, and common rejection reasons\n\n## Important Notes\n\n- NAMESPACE is auto-generated by roxygen2: never edit manually. Run `devtools::document()` after any roxygen changes.\n- `R CMD check --as-cran` is the gold standard. If it passes with 0E\u002F0W\u002F0N, the package is very likely to be accepted.\n- First-time submissions face heightened scrutiny. The Description field is especially important.\n- CRAN reviewers are volunteers. Respect their time by fixing all automated issues before submission.\n","# CRAN Submission Audit\n\nAudit an R package against CRAN Repository Policy requirements and produce a structured gap report. This skill evaluates package structure, DESCRIPTION metadata, documentation, code quality, and test coverage against the full CRAN checklist.\n\n## Workflow\n\n### 1. Locate the Package\n\nIdentify the R package to audit. Look for `DESCRIPTION` file in the current working directory or a specified path. If no R package is found, ask the user which package to audit.\n\n### 1b. Load User Config\n\nRead `.claude\u002Fpub-pipeline.local.md` if it exists (Read tool). Extract author metadata and package context from YAML frontmatter. If the file is missing, inform the user and offer to create one from the template at `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fuser-config-template.md`.\n\n### 1c. Verify Dependency Availability\n\nBefore running the full audit, check that all dependencies are available on CRAN (Bash tool):\n\n1. Parse `Imports`, `Depends`, and `LinkingTo` fields from `DESCRIPTION`\n2. For each dependency that is not a base or recommended package, verify it exists on CRAN:\n```bash\nRscript -e 'ap \u003C- available.packages(); cat(\"PKG_NAME\" %in% rownames(ap))'\n```\n3. For dependencies with version requirements (e.g., `pkg (>= 2.0)`), verify the requirement is satisfiable:\n```bash\nRscript -e 'ap \u003C- available.packages(); cat(ap[\"PKG_NAME\", \"Version\"])'\n```\nCompare the available version against the minimum required version.\n\nIf any dependency is **not on CRAN**, flag it as a **hard blocker** in the gap report and stop here: the package cannot pass `R CMD check --as-cran` until all dependencies are available. Recommend the user publish the missing dependency first or switch to a CRAN-available alternative.\n\n### 2. Gather Package State\n\nRun these checks in parallel where possible:\n\n**Regenerate documentation** (Bash tool):\nRun `Rscript -e 'devtools::document()'` to ensure NAMESPACE and `man\u002F` files are current before auditing them. This prevents false negatives from stale roxygen output.\n\n**Package metadata** (Read tool):\n- Read `DESCRIPTION`: check all required fields\n- Read `NAMESPACE`: verify auto-generation by roxygen2\n- Read `LICENSE` or `LICENSE.md`: verify OSI-approved license\n- Check for `NEWS.md`, `cran-comments.md`, `README.md`\n\n**Code quality** (Grep\u002FGlob tools):\n- Search for `q()` calls in R code\n- Search for `.Internal()`, `:::` accessing base internals\n- Search for writes outside `tempdir()` \u002F `tools::R_user_dir()`\n- Check that Suggested packages are used conditionally (`if (requireNamespace(...))`)\n- Verify no binary executables in source\n- Search for `options()` or `par()` calls that don't restore state via `on.exit()` or `withr`\n- Run `urlchecker::url_check()` to verify all URLs are valid and HTTPS\n\n**Documentation** (Grep\u002FGlob tools):\n- Check all exported functions have `@returns` roxygen tag\n- Check all exported functions have `@examples` roxygen tag\n- Verify `man\u002F` directory exists with `.Rd` files\n\n**R CMD check** (Bash tool):\n```bash\ncd \u002Fpath\u002Fto\u002Fpackage && Rscript -e 'devtools::check(args = \"--as-cran\")'\n```\n\n**Test coverage** (Bash tool):\n```bash\ncd \u002Fpath\u002Fto\u002Fpackage && Rscript -e 'covr::package_coverage()'\n```\n\n### 3. Evaluate Against Checklist\n\nScore each item from the CRAN checklist as PASS, FAIL, or WARN. Consult the full checklist in `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fcran-reference.md` for detailed requirements.\n\nKey categories to evaluate:\n\n| Category | Key Checks |\n|----------|-----------|\n| **DESCRIPTION** | Title case, no period, informative Description, Authors@R with roles, valid License |\n| **Dependencies** | Imports from CRAN\u002FBioconductor only, conditional Suggests usage |\n| **Code behavior** | No q(), no .Internal, no writing outside tempdir, no global env modification |\n| **Documentation** | All exports have @returns and @examples, vignettes build |\n| **Examples** | `\\dontrun{}` only for truly non-runnable code; prefer `\\donttest{}` for slow examples (still run by `--as-cran` since R 4.0.0, so they must pass) |\n| **Side effects** | `options()`\u002F`par()` restored via `on.exit()` or `withr`; no persistent state changes |\n| **Size** | Tarball ideally \u003C10MB (\"if possible\"), data and docs each \u003C5MB as a general rule, examples run in seconds |\n| **Cross-platform** | Portable code, no OS-specific assumptions |\n| **Testing** | R CMD check clean (0E\u002F0W), notes explained |\n| **URLs** | All URLs valid and using HTTPS |\n\n### 4. Produce Gap Report\n\nFormat the report as:\n\n```markdown\n# CRAN Audit Report: {package name} v{version}\n\n## Summary\n- **Status**: READY \u002F NEEDS WORK \u002F NOT READY\n- **Score**: X\u002FY checks passed\n- **Blockers**: N critical issues\n\n## Critical (Must Fix)\n1. [Issue description] ([file:line]): [how to fix]\n\n## Warnings (Should Fix)\n1. [Issue description] ([file:line]): [recommendation]\n\n## Passed\n- [Check name] ✓\n\n## R CMD Check Results\n[Paste relevant output]\n\n## Recommended Next Steps\n1. [Ordered list of actions]\n```\n\n### 5. Offer to Fix\n\nAfter presenting the report, offer to fix issues that can be automated:\n- Add missing `@returns` tags\n- Add `cran-comments.md` if missing\n- Fix Title\u002FDescription formatting\n- Add conditional `requireNamespace()` checks\n- Create `NEWS.md` if missing\n- Replace `\\dontrun{}` with `\\donttest{}` where appropriate\n\n## Reference Files\n\nFor the complete CRAN policy checklist and submission workflow, consult:\n- **`${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fcran-reference.md`**: Full CRAN Repository Policy reference with pre-submission checklist, submission workflow, and common rejection reasons\n\n## Important Notes\n\n- NAMESPACE is auto-generated by roxygen2: never edit manually. Run `devtools::document()` after any roxygen changes.\n- `R CMD check --as-cran` is the gold standard. If it passes with 0E\u002F0W\u002F0N, the package is very likely to be accepted.\n- First-time submissions face heightened scrutiny. The Description field is especially important.\n- CRAN reviewers are volunteers. Respect their time by fixing all automated issues before submission.\n",{"name":5,"description":7,"argument-hint":24},"[package path]","main","f6f3133da90d79585262853f985437619b96f30d","pub-pipeline\u002Fskills\u002Fcran-audit","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 cran-audit",{"tool":38,"command":39},"bunx","bunx skills add Abdulqudduz\u002Fclaude-anvil --skill cran-audit",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Abdulqudduz\u002Fclaude-anvil --skill cran-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAbdulqudduz\u002Fclaude-anvil\u002Fblob\u002Fmain\u002Fpub-pipeline\u002Fskills\u002Fcran-audit\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",[],[]]