[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73D5BXRQVBAQYN911TYX9SA":3,"skill-same:01M73D5BXRQVBAQYN911TYX9SA":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M73D5BXRQVBAQYN911TYX9SA","write-claude-md",null,"Create an effective CLAUDE.md file that provides project-specific instructions to AI coding assistants. Covers structure, common sections, do\u002Fdon't patterns, and integration with MCP servers and agent definitions. Use when starting a new project where AI assistants will be used, improving AI behavior on an existing project, documenting project conventions and constraints, or integrating MCP servers or agent definitions into a project workflow.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-claude-md\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: write-claude-md\nlocale: caveman-lite\nsource_locale: en\nsource_commit: 82c77053\ntranslator: \"Julius Brussee homage — caveman\"\ntranslation_date: \"2026-05-03\"\ndescription: >\n  Create an effective CLAUDE.md file that provides project-specific\n  instructions to AI coding assistants. Covers structure, common\n  sections, do\u002Fdon't patterns, and integration with MCP servers\n  and agent definitions. Use when starting a new project where AI\n  assistants will be used, improving AI behavior on an existing project,\n  documenting project conventions and constraints, or integrating MCP\n  servers or agent definitions into a project workflow.\nlicense: MIT\nallowed-tools: Read Write Edit Bash Grep Glob\nmetadata:\n  author: Philipp Thoss\n  version: \"1.0\"\n  domain: general\n  complexity: basic\n  language: multi\n  tags: claude-md, ai-assistant, project-config, documentation\n---\n\n# Write CLAUDE.md\n\nCreate a CLAUDE.md file that gives AI assistants effective project-specific context.\n\n## When to Use\n\n- Starting a new project where AI assistants will be used\n- Improving AI assistant behavior on an existing project\n- Documenting project conventions, workflows, and constraints\n- Integrating MCP servers or agent definitions into a project\n\n## Inputs\n\n- **Required**: Project type and technology stack\n- **Required**: Key conventions and constraints\n- **Optional**: MCP server configurations\n- **Optional**: Author and contributor information\n- **Optional**: Security and confidentiality requirements\n\n## Procedure\n\n### Step 1: Create Basic CLAUDE.md\n\nPlace `CLAUDE.md` in the project root:\n\n```markdown\n# Project Name\n\nBrief description of what this project is and its purpose.\n\n## Quick Start\n\nEssential commands for working on this project:\n\n```bash\n# Install dependencies\nnpm install  # or renv::restore() for R\n\n# Run tests\nnpm test     # or devtools::test() for R\n\n# Build\nnpm run build  # or devtools::check() for R\n```\n\n## Architecture\n\nKey architectural decisions and patterns used in this project.\n\n## Conventions\n\n- Always use descriptive variable names\n- Follow [language-specific style guide]\n- Write tests for all new functionality\n```\n\n**Got:** A `CLAUDE.md` file exists in the project root with at minimum a project description, quick start commands, architecture overview, and conventions section.\n\n**If fail:** If unsure what to include, start with the Quick Start section containing the three most important commands (install, test, build). The file can be expanded incrementally as the project evolves.\n\n### Step 2: Add Technology-Specific Sections\n\n**For R packages**:\n\n```markdown\n## Development Workflow\n\n```r\ndevtools::load_all()    # Load for development\ndevtools::document()    # Regenerate docs\ndevtools::test()        # Run tests\ndevtools::check()       # Full package check\n```\n\n## Package Structure\n\n- `R\u002F` - Source code (one function per file)\n- `tests\u002Ftestthat\u002F` - Tests mirror R\u002F structure\n- `vignettes\u002F` - Long-form documentation\n- `man\u002F` - Generated by roxygen2 (do not edit manually)\n\n## Critical Files (Do Not Delete)\n\n- `.Rprofile` - Session configuration\n- `.Renviron` - Environment variables (git-ignored)\n- `renv.lock` - Locked dependencies\n```\n\n**For Node.js\u002FTypeScript**:\n\n```markdown\n## Stack\n\n- Next.js 15 with App Router\n- TypeScript strict mode\n- Tailwind CSS for styling\n- Vercel for deployment\n\n## Conventions\n\n- Use `@\u002F` import alias for src\u002F directory\n- Server Components by default, `\"use client\"` only when needed\n- API routes in `src\u002Fapp\u002Fapi\u002F`\n```\n\n**Got:** Technology-specific sections are added that match the project's actual stack — R package structure for R projects, Node.js stack details for web projects, etc. Commands and paths reference the real project layout.\n\n**If fail:** If the project uses an unfamiliar stack, inspect `package.json`, `DESCRIPTION`, `Cargo.toml`, or equivalent to identify the technology and add the corresponding section.\n\n### Step 3: Add MCP Server Information\n\n```markdown\n## Available MCP Servers\n\n### r-mcptools (R Integration)\n- **Purpose**: Connect to R\u002FRStudio sessions\n- **Status**: Configured\n- **Configuration**: `claude mcp add r-mcptools stdio \"Rscript.exe\" -- -e \"mcptools::mcp_server()\"`\n\n### hf-mcp-server (Hugging Face)\n- **Purpose**: AI\u002FML model and dataset access\n- **Status**: Configured\n- **Configuration**: `claude mcp add hf-mcp-server -e HF_TOKEN=token -- mcp-remote https:\u002F\u002Fhuggingface.co\u002Fmcp`\n```\n\n**Got:** Each configured MCP server has a subsection documenting its purpose, status (configured\u002Favailable\u002Fnot configured), and the command used to add it. No actual tokens or secrets are included.\n\n**If fail:** If MCP servers are not yet configured, document them as \"Available\" with setup instructions rather than \"Configured.\" Use placeholder values like `your_token_here` for any credentials.\n\n### Step 4: Add Author Information\n\n```markdown\n## Author Information\n\n### Standard Package Authorship\n- **Name**: Author Name\n- **Email**: author@example.com\n- **ORCID**: 0000-0000-0000-0000\n- **GitHub**: username\n```\n\n**Got:** Author information section includes name, email, ORCID (for academic\u002Fresearch projects), and GitHub username. For R packages, the format matches DESCRIPTION file requirements.\n\n**If fail:** If author information is sensitive or should not be public, use the organization name instead of personal details, or omit the section entirely for internal-only projects.\n\n### Step 5: Add Security Guidelines\n\n```markdown\n## Security & Confidentiality\n\n- Never commit `.Renviron`, `.env`, or files containing tokens\n- Use placeholder values in documentation: `YOUR_TOKEN_HERE`\n- Environment variables for all secrets\n- Git-ignored: `.Renviron`, `.env`, `credentials.json`\n```\n\n**Got:** Security section lists files that must never be committed, placeholder conventions for documentation, and confirms that `.gitignore` covers all sensitive files.\n\n**If fail:** If unsure which files are sensitive, run `grep -rn \"sk-\\|ghp_\\|password\" .` to scan for exposed secrets. Any file containing real credentials should be added to `.gitignore` and mentioned in this section.\n\n### Step 6: Reference Skills and Guides\n\n```markdown\n## Development Best Practices References\n@agent-almanac\u002Fskills\u002Fwrite-testthat-tests\u002FSKILL.md\n@agent-almanac\u002Fskills\u002Fsubmit-to-cran\u002FSKILL.md\n```\n\n**Got:** Relevant skills and guides are referenced using `@` paths, giving AI assistants access to detailed procedures for common tasks in the project.\n\n**If fail:** If the referenced skills or guides do not exist at the specified paths, verify the paths or remove the references. Broken `@` references provide no value and may confuse the assistant.\n\n### Step 7: Add Quality and Status Information\n\n```markdown\n## Quality Status\n\n- R CMD check: 0 errors, 0 warnings, 1 note\n- Test coverage: 85%\n- Tests: 200+ passing\n- Vignettes: 3 (rated 9\u002F10)\n```\n\n**Got:** Quality metrics section reflects the current state of the project with accurate numbers for check results, test coverage, test count, and documentation status.\n\n**If fail:** If metrics are not yet available (new project), add placeholder entries with \"TBD\" and update them as the project matures. Do not fabricate numbers.\n\n## Validation\n\n- [ ] CLAUDE.md is in project root\n- [ ] Quick start commands are accurate and work\n- [ ] Architecture section reflects actual project structure\n- [ ] No sensitive information (tokens, passwords, private paths)\n- [ ] MCP server configurations are current\n- [ ] Referenced files and paths exist\n\n## Pitfalls\n\n- **Stale information**: Update CLAUDE.md when project structure changes\n- **Too much detail**: Keep it concise. Link to detailed guides rather than duplicating content.\n- **Sensitive data**: Never include actual tokens or credentials. Use placeholders.\n- **Conflicting instructions**: Ensure CLAUDE.md doesn't contradict other config files\n- **Missing from `.Rbuildignore`**: For R packages, add `^CLAUDE\\\\.md$` to `.Rbuildignore`\n\n## Examples\n\nPattern observed across successful projects:\n\n1. **putior** (829 lines): Comprehensive CLAUDE.md with quality metrics, 20 accomplishments, MCP integration details, and development workflow\n2. **Simple project** (20 lines): Just quick start commands and key conventions\n\nScale the CLAUDE.md to match project complexity.\n\n## Related Skills\n\n- `create-r-package` - CLAUDE.md as part of package setup\n- `configure-mcp-server` - MCP configuration referenced in CLAUDE.md\n- `security-audit-codebase` - verify no secrets in CLAUDE.md\n","# Write CLAUDE.md\n\nCreate a CLAUDE.md file that gives AI assistants effective project-specific context.\n\n## When to Use\n\n- Starting a new project where AI assistants will be used\n- Improving AI assistant behavior on an existing project\n- Documenting project conventions, workflows, and constraints\n- Integrating MCP servers or agent definitions into a project\n\n## Inputs\n\n- **Required**: Project type and technology stack\n- **Required**: Key conventions and constraints\n- **Optional**: MCP server configurations\n- **Optional**: Author and contributor information\n- **Optional**: Security and confidentiality requirements\n\n## Procedure\n\n### Step 1: Create Basic CLAUDE.md\n\nPlace `CLAUDE.md` in the project root:\n\n```markdown\n# Project Name\n\nBrief description of what this project is and its purpose.\n\n## Quick Start\n\nEssential commands for working on this project:\n\n```bash\n# Install dependencies\nnpm install  # or renv::restore() for R\n\n# Run tests\nnpm test     # or devtools::test() for R\n\n# Build\nnpm run build  # or devtools::check() for R\n```\n\n## Architecture\n\nKey architectural decisions and patterns used in this project.\n\n## Conventions\n\n- Always use descriptive variable names\n- Follow [language-specific style guide]\n- Write tests for all new functionality\n```\n\n**Got:** A `CLAUDE.md` file exists in the project root with at minimum a project description, quick start commands, architecture overview, and conventions section.\n\n**If fail:** If unsure what to include, start with the Quick Start section containing the three most important commands (install, test, build). The file can be expanded incrementally as the project evolves.\n\n### Step 2: Add Technology-Specific Sections\n\n**For R packages**:\n\n```markdown\n## Development Workflow\n\n```r\ndevtools::load_all()    # Load for development\ndevtools::document()    # Regenerate docs\ndevtools::test()        # Run tests\ndevtools::check()       # Full package check\n```\n\n## Package Structure\n\n- `R\u002F` - Source code (one function per file)\n- `tests\u002Ftestthat\u002F` - Tests mirror R\u002F structure\n- `vignettes\u002F` - Long-form documentation\n- `man\u002F` - Generated by roxygen2 (do not edit manually)\n\n## Critical Files (Do Not Delete)\n\n- `.Rprofile` - Session configuration\n- `.Renviron` - Environment variables (git-ignored)\n- `renv.lock` - Locked dependencies\n```\n\n**For Node.js\u002FTypeScript**:\n\n```markdown\n## Stack\n\n- Next.js 15 with App Router\n- TypeScript strict mode\n- Tailwind CSS for styling\n- Vercel for deployment\n\n## Conventions\n\n- Use `@\u002F` import alias for src\u002F directory\n- Server Components by default, `\"use client\"` only when needed\n- API routes in `src\u002Fapp\u002Fapi\u002F`\n```\n\n**Got:** Technology-specific sections are added that match the project's actual stack — R package structure for R projects, Node.js stack details for web projects, etc. Commands and paths reference the real project layout.\n\n**If fail:** If the project uses an unfamiliar stack, inspect `package.json`, `DESCRIPTION`, `Cargo.toml`, or equivalent to identify the technology and add the corresponding section.\n\n### Step 3: Add MCP Server Information\n\n```markdown\n## Available MCP Servers\n\n### r-mcptools (R Integration)\n- **Purpose**: Connect to R\u002FRStudio sessions\n- **Status**: Configured\n- **Configuration**: `claude mcp add r-mcptools stdio \"Rscript.exe\" -- -e \"mcptools::mcp_server()\"`\n\n### hf-mcp-server (Hugging Face)\n- **Purpose**: AI\u002FML model and dataset access\n- **Status**: Configured\n- **Configuration**: `claude mcp add hf-mcp-server -e HF_TOKEN=token -- mcp-remote https:\u002F\u002Fhuggingface.co\u002Fmcp`\n```\n\n**Got:** Each configured MCP server has a subsection documenting its purpose, status (configured\u002Favailable\u002Fnot configured), and the command used to add it. No actual tokens or secrets are included.\n\n**If fail:** If MCP servers are not yet configured, document them as \"Available\" with setup instructions rather than \"Configured.\" Use placeholder values like `your_token_here` for any credentials.\n\n### Step 4: Add Author Information\n\n```markdown\n## Author Information\n\n### Standard Package Authorship\n- **Name**: Author Name\n- **Email**: author@example.com\n- **ORCID**: 0000-0000-0000-0000\n- **GitHub**: username\n```\n\n**Got:** Author information section includes name, email, ORCID (for academic\u002Fresearch projects), and GitHub username. For R packages, the format matches DESCRIPTION file requirements.\n\n**If fail:** If author information is sensitive or should not be public, use the organization name instead of personal details, or omit the section entirely for internal-only projects.\n\n### Step 5: Add Security Guidelines\n\n```markdown\n## Security & Confidentiality\n\n- Never commit `.Renviron`, `.env`, or files containing tokens\n- Use placeholder values in documentation: `YOUR_TOKEN_HERE`\n- Environment variables for all secrets\n- Git-ignored: `.Renviron`, `.env`, `credentials.json`\n```\n\n**Got:** Security section lists files that must never be committed, placeholder conventions for documentation, and confirms that `.gitignore` covers all sensitive files.\n\n**If fail:** If unsure which files are sensitive, run `grep -rn \"sk-\\|ghp_\\|password\" .` to scan for exposed secrets. Any file containing real credentials should be added to `.gitignore` and mentioned in this section.\n\n### Step 6: Reference Skills and Guides\n\n```markdown\n## Development Best Practices References\n@agent-almanac\u002Fskills\u002Fwrite-testthat-tests\u002FSKILL.md\n@agent-almanac\u002Fskills\u002Fsubmit-to-cran\u002FSKILL.md\n```\n\n**Got:** Relevant skills and guides are referenced using `@` paths, giving AI assistants access to detailed procedures for common tasks in the project.\n\n**If fail:** If the referenced skills or guides do not exist at the specified paths, verify the paths or remove the references. Broken `@` references provide no value and may confuse the assistant.\n\n### Step 7: Add Quality and Status Information\n\n```markdown\n## Quality Status\n\n- R CMD check: 0 errors, 0 warnings, 1 note\n- Test coverage: 85%\n- Tests: 200+ passing\n- Vignettes: 3 (rated 9\u002F10)\n```\n\n**Got:** Quality metrics section reflects the current state of the project with accurate numbers for check results, test coverage, test count, and documentation status.\n\n**If fail:** If metrics are not yet available (new project), add placeholder entries with \"TBD\" and update them as the project matures. Do not fabricate numbers.\n\n## Validation\n\n- [ ] CLAUDE.md is in project root\n- [ ] Quick start commands are accurate and work\n- [ ] Architecture section reflects actual project structure\n- [ ] No sensitive information (tokens, passwords, private paths)\n- [ ] MCP server configurations are current\n- [ ] Referenced files and paths exist\n\n## Pitfalls\n\n- **Stale information**: Update CLAUDE.md when project structure changes\n- **Too much detail**: Keep it concise. Link to detailed guides rather than duplicating content.\n- **Sensitive data**: Never include actual tokens or credentials. Use placeholders.\n- **Conflicting instructions**: Ensure CLAUDE.md doesn't contradict other config files\n- **Missing from `.Rbuildignore`**: For R packages, add `^CLAUDE\\\\.md$` to `.Rbuildignore`\n\n## Examples\n\nPattern observed across successful projects:\n\n1. **putior** (829 lines): Comprehensive CLAUDE.md with quality metrics, 20 accomplishments, MCP integration details, and development workflow\n2. **Simple project** (20 lines): Just quick start commands and key conventions\n\nScale the CLAUDE.md to match project complexity.\n\n## Related Skills\n\n- `create-r-package` - CLAUDE.md as part of package setup\n- `configure-mcp-server` - MCP configuration referenced in CLAUDE.md\n- `security-audit-codebase` - verify no secrets in CLAUDE.md\n",{"name":5,"locale":23,"license":14,"metadata":24,"translator":31,"description":32,"allowed-tools":33,"source_commit":34,"source_locale":35,"translation_date":36},"caveman-lite",{"tags":25,"author":26,"domain":27,"version":28,"language":29,"complexity":30},"claude-md, ai-assistant, project-config, documentation","Philipp Thoss","general","1.0","multi","basic","Julius Brussee homage — caveman","Create an effective CLAUDE.md file that provides project-specific instructions to AI coding assistants. Covers structure, common sections, do\u002Fdon't patterns, and integration with MCP servers and agent definitions. Use when starting a new project where AI assistants will be used, improving AI behavior on an existing project, documenting project conventions and constraints, or integrating MCP servers or agent definitions into a project workflow.\n","Read Write Edit Bash Grep Glob","82c77053","en","2026-05-03","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fwrite-claude-md",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add roohe\u002Fagentic-super-skills --skill write-claude-md",{"tool":51,"command":52},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill write-claude-md",{"tool":54,"command":55},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill write-claude-md","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-claude-md\u002FSKILL.md",true,[],[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]