[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M737Q997HT1JA469S78RH360":3,"skill-same:01M737Q997HT1JA469S78RH360":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},"01M737Q997HT1JA469S78RH360","configure-mcp-server",null,"Configure MCP (Model Context Protocol) servers for Claude Code and Claude Desktop. Covers mcptools setup, Hugging Face integration, WSL path handling, and multi-client configuration. Use when setting up Claude Code to connect to R via mcptools, configuring Claude Desktop with MCP servers, adding Hugging Face or other remote MCP servers, or troubleshooting MCP connectivity between clients and servers.","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\u002Fconfigure-mcp-server\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: configure-mcp-server\nlocale: caveman-lite\nsource_locale: en\nsource_commit: 82c77053\ntranslator: \"Julius Brussee homage — caveman\"\ntranslation_date: \"2026-04-19\"\ndescription: >\n  Configure MCP (Model Context Protocol) servers for Claude Code and\n  Claude Desktop. Covers mcptools setup, Hugging Face integration,\n  WSL path handling, and multi-client configuration. Use when setting up\n  Claude Code to connect to R via mcptools, configuring Claude Desktop\n  with MCP servers, adding Hugging Face or other remote MCP servers, or\n  troubleshooting MCP connectivity between clients and servers.\nlicense: MIT\nallowed-tools: Read Write Edit Bash Grep Glob\nmetadata:\n  author: Philipp Thoss\n  version: \"1.0\"\n  domain: mcp-integration\n  complexity: intermediate\n  language: multi\n  tags: mcp, claude-code, claude-desktop, mcptools, configuration\n---\n\n# Configure MCP Server\n\nSet up MCP server connections for Claude Code (WSL) and Claude Desktop (Windows).\n\n## When to Use\n\n- Setting up Claude Code to connect to R via mcptools\n- Configuring Claude Desktop with MCP servers\n- Adding Hugging Face or other remote MCP servers\n- Troubleshooting MCP connectivity between tools\n\n## Inputs\n\n- **Required**: MCP server type (mcptools, Hugging Face, custom)\n- **Required**: Client (Claude Code, Claude Desktop, or both)\n- **Optional**: Authentication tokens\n- **Optional**: Custom server implementation\n\n## Procedure\n\n### Step 1: Install MCP Server Packages\n\n**For R (mcptools)**:\n\n```r\ninstall.packages(\"remotes\")\nremotes::install_github(\"posit-dev\u002Fmcptools\")\n```\n\n**For Hugging Face**:\n\n```bash\nnpm install -g mcp-remote\n```\n\n**Got:** `mcptools` installs from GitHub and loads in R without errors. `mcp-remote` is available globally via `which mcp-remote` or `npm list -g mcp-remote`.\n\n**If fail:** For `mcptools`, ensure `remotes` is installed first. If GitHub rate-limits the install, set a `GITHUB_PAT` in `~\u002F.Renviron`. For `mcp-remote`, verify Node.js and npm are installed and on PATH.\n\n### Step 2: Configure Claude Code (WSL)\n\n**R mcptools server**:\n\n```bash\nclaude mcp add r-mcptools stdio \\\n  \"\u002Fmnt\u002Fc\u002FProgram Files\u002FR\u002FR-4.5.0\u002Fbin\u002FRscript.exe\" \\\n  -- -e \"mcptools::mcp_server()\"\n```\n\n**Hugging Face server**:\n\n```bash\nclaude mcp add hf-mcp-server \\\n  -e HF_TOKEN=your_token_here \\\n  -- mcp-remote https:\u002F\u002Fhuggingface.co\u002Fmcp\n```\n\n**Verify configuration**:\n\n```bash\nclaude mcp list\nclaude mcp get r-mcptools\n```\n\n**Got:** `claude mcp list` shows both `r-mcptools` and `hf-mcp-server` (or whichever servers were added). `claude mcp get r-mcptools` displays the correct command and arguments.\n\n**If fail:** If the server does not appear in the list, verify `~\u002F.claude.json` contains the correct entry. If the `claude` command is not found, add it to PATH: `export PATH=\"$HOME\u002F.claude\u002Flocal\u002Fnode_modules\u002F.bin:$PATH\"`.\n\n### Step 3: Configure Claude Desktop (Windows)\n\nEdit `%APPDATA%\\Claude\\claude_desktop_config.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"r-mcptools\": {\n      \"command\": \"C:\\\\PROGRA~1\\\\R\\\\R-45~1.0\\\\bin\\\\x64\\\\Rscript.exe\",\n      \"args\": [\"-e\", \"mcptools::mcp_server()\"]\n    },\n    \"hf-mcp-server\": {\n      \"command\": \"mcp-remote\",\n      \"args\": [\"https:\u002F\u002Fhuggingface.co\u002Fmcp\"],\n      \"env\": {\n        \"HF_TOKEN\": \"your_token_here\"\n      }\n    }\n  }\n}\n```\n\n**Important**: Use 8.3 short paths for Windows directories with spaces (`PROGRA~1` not `Program Files`). Use environment variables for tokens, not `--header` arguments.\n\n**Got:** The JSON config file at `%APPDATA%\\Claude\\claude_desktop_config.json` is valid JSON with the correct server entries. Claude Desktop shows MCP server indicators after restart.\n\n**If fail:** Validate the JSON with a linter (e.g., `jq . \u003C config.json`). Use 8.3 short paths (`PROGRA~1`) if Windows path spaces cause parsing errors. Ensure Claude Desktop is fully restarted (not merely minimized).\n\n### Step 4: Configure R Session for MCP\n\nAdd to project `.Rprofile`:\n\n```r\nif (requireNamespace(\"mcptools\", quietly = TRUE)) {\n  mcptools::mcp_session()\n}\n```\n\nThis starts the MCP session automatically when opening the project in RStudio.\n\n**Got:** The `.Rprofile` file conditionally starts `mcptools::mcp_session()` when the project is opened in RStudio, making MCP tools available automatically.\n\n**If fail:** If `mcptools` is not found at session start, verify it is installed in the library that RStudio uses (check `.libPaths()`). If using renv, ensure mcptools is in the renv library.\n\n### Step 5: Verify Connections\n\n**Test R MCP from WSL**:\n\n```bash\n\"\u002Fmnt\u002Fc\u002FProgram Files\u002FR\u002FR-4.5.0\u002Fbin\u002FRscript.exe\" -e \"mcptools::mcp_server()\"\n```\n\n**Test from within Claude Code**:\n\nStart Claude Code and use MCP tools — they should appear in the tool list.\n\n**Test Claude Desktop**:\n\nRestart Claude Desktop after configuration changes. Check for MCP server indicators in the UI.\n\n**Got:** Running Rscript with `mcptools::mcp_server()` produces output without errors. MCP tools appear in the Claude Code tool list during an active session. Claude Desktop shows server status after restart.\n\n**If fail:** If the Rscript command fails, check the full path is correct (`ls \"\u002Fmnt\u002Fc\u002FProgram Files\u002FR\u002F\"` to verify R version). If tools don't appear in Claude Code, restart the session. For Claude Desktop, check firewall settings.\n\n### Step 6: Multi-Server Configuration\n\nBoth Claude Code and Claude Desktop support multiple MCP servers simultaneously:\n\n```bash\n# Claude Code: add multiple servers\nclaude mcp add r-mcptools stdio \"\u002Fpath\u002Fto\u002FRscript.exe\" -- -e \"mcptools::mcp_server()\"\nclaude mcp add hf-mcp-server -e HF_TOKEN=token -- mcp-remote https:\u002F\u002Fhuggingface.co\u002Fmcp\nclaude mcp add custom-server stdio \"\u002Fpath\u002Fto\u002Fserver\" -- --port 3001\n```\n\n**Got:** Multiple MCP servers configured and accessible simultaneously. `claude mcp list` shows all servers. Each server's tools are available in the same Claude Code session.\n\n**If fail:** If servers conflict, check that each has a unique name in the configuration. If one server blocks others, verify servers use non-blocking I\u002FO (stdio transport handles this automatically).\n\n## Validation\n\n- [ ] `claude mcp list` shows all configured servers\n- [ ] R MCP server responds to tool calls\n- [ ] Hugging Face MCP server authenticates and responds\n- [ ] Both Claude Code and Claude Desktop can connect (if both configured)\n- [ ] MCP tools appear in the tool list during sessions\n\n## Pitfalls\n\n- **Windows path spaces**: Use 8.3 short names or quote paths correctly. Different tools parse paths differently.\n- **Token in command args**: On Windows, `--header \"Authorization: Bearer token\"` fails due to parsing. Use environment variables instead.\n- **Confusing Claude Code and Claude Desktop configs**: These are separate tools with separate config files (`~\u002F.claude.json` vs `%APPDATA%\\Claude\\`)\n- **npx vs global install**: `npx mcp-remote` may fail in Claude Desktop context. Install globally with `npm install -g mcp-remote`.\n- **mcptools version**: Ensure mcptools is up to date. It requires the `ellmer` package as a dependency.\n\n## Related Skills\n\n- `build-custom-mcp-server` - creating your own MCP server\n- `troubleshoot-mcp-connection` - debugging connection issues\n- `setup-wsl-dev-environment` - WSL setup prerequisite\n","# Configure MCP Server\n\nSet up MCP server connections for Claude Code (WSL) and Claude Desktop (Windows).\n\n## When to Use\n\n- Setting up Claude Code to connect to R via mcptools\n- Configuring Claude Desktop with MCP servers\n- Adding Hugging Face or other remote MCP servers\n- Troubleshooting MCP connectivity between tools\n\n## Inputs\n\n- **Required**: MCP server type (mcptools, Hugging Face, custom)\n- **Required**: Client (Claude Code, Claude Desktop, or both)\n- **Optional**: Authentication tokens\n- **Optional**: Custom server implementation\n\n## Procedure\n\n### Step 1: Install MCP Server Packages\n\n**For R (mcptools)**:\n\n```r\ninstall.packages(\"remotes\")\nremotes::install_github(\"posit-dev\u002Fmcptools\")\n```\n\n**For Hugging Face**:\n\n```bash\nnpm install -g mcp-remote\n```\n\n**Got:** `mcptools` installs from GitHub and loads in R without errors. `mcp-remote` is available globally via `which mcp-remote` or `npm list -g mcp-remote`.\n\n**If fail:** For `mcptools`, ensure `remotes` is installed first. If GitHub rate-limits the install, set a `GITHUB_PAT` in `~\u002F.Renviron`. For `mcp-remote`, verify Node.js and npm are installed and on PATH.\n\n### Step 2: Configure Claude Code (WSL)\n\n**R mcptools server**:\n\n```bash\nclaude mcp add r-mcptools stdio \\\n  \"\u002Fmnt\u002Fc\u002FProgram Files\u002FR\u002FR-4.5.0\u002Fbin\u002FRscript.exe\" \\\n  -- -e \"mcptools::mcp_server()\"\n```\n\n**Hugging Face server**:\n\n```bash\nclaude mcp add hf-mcp-server \\\n  -e HF_TOKEN=your_token_here \\\n  -- mcp-remote https:\u002F\u002Fhuggingface.co\u002Fmcp\n```\n\n**Verify configuration**:\n\n```bash\nclaude mcp list\nclaude mcp get r-mcptools\n```\n\n**Got:** `claude mcp list` shows both `r-mcptools` and `hf-mcp-server` (or whichever servers were added). `claude mcp get r-mcptools` displays the correct command and arguments.\n\n**If fail:** If the server does not appear in the list, verify `~\u002F.claude.json` contains the correct entry. If the `claude` command is not found, add it to PATH: `export PATH=\"$HOME\u002F.claude\u002Flocal\u002Fnode_modules\u002F.bin:$PATH\"`.\n\n### Step 3: Configure Claude Desktop (Windows)\n\nEdit `%APPDATA%\\Claude\\claude_desktop_config.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"r-mcptools\": {\n      \"command\": \"C:\\\\PROGRA~1\\\\R\\\\R-45~1.0\\\\bin\\\\x64\\\\Rscript.exe\",\n      \"args\": [\"-e\", \"mcptools::mcp_server()\"]\n    },\n    \"hf-mcp-server\": {\n      \"command\": \"mcp-remote\",\n      \"args\": [\"https:\u002F\u002Fhuggingface.co\u002Fmcp\"],\n      \"env\": {\n        \"HF_TOKEN\": \"your_token_here\"\n      }\n    }\n  }\n}\n```\n\n**Important**: Use 8.3 short paths for Windows directories with spaces (`PROGRA~1` not `Program Files`). Use environment variables for tokens, not `--header` arguments.\n\n**Got:** The JSON config file at `%APPDATA%\\Claude\\claude_desktop_config.json` is valid JSON with the correct server entries. Claude Desktop shows MCP server indicators after restart.\n\n**If fail:** Validate the JSON with a linter (e.g., `jq . \u003C config.json`). Use 8.3 short paths (`PROGRA~1`) if Windows path spaces cause parsing errors. Ensure Claude Desktop is fully restarted (not merely minimized).\n\n### Step 4: Configure R Session for MCP\n\nAdd to project `.Rprofile`:\n\n```r\nif (requireNamespace(\"mcptools\", quietly = TRUE)) {\n  mcptools::mcp_session()\n}\n```\n\nThis starts the MCP session automatically when opening the project in RStudio.\n\n**Got:** The `.Rprofile` file conditionally starts `mcptools::mcp_session()` when the project is opened in RStudio, making MCP tools available automatically.\n\n**If fail:** If `mcptools` is not found at session start, verify it is installed in the library that RStudio uses (check `.libPaths()`). If using renv, ensure mcptools is in the renv library.\n\n### Step 5: Verify Connections\n\n**Test R MCP from WSL**:\n\n```bash\n\"\u002Fmnt\u002Fc\u002FProgram Files\u002FR\u002FR-4.5.0\u002Fbin\u002FRscript.exe\" -e \"mcptools::mcp_server()\"\n```\n\n**Test from within Claude Code**:\n\nStart Claude Code and use MCP tools — they should appear in the tool list.\n\n**Test Claude Desktop**:\n\nRestart Claude Desktop after configuration changes. Check for MCP server indicators in the UI.\n\n**Got:** Running Rscript with `mcptools::mcp_server()` produces output without errors. MCP tools appear in the Claude Code tool list during an active session. Claude Desktop shows server status after restart.\n\n**If fail:** If the Rscript command fails, check the full path is correct (`ls \"\u002Fmnt\u002Fc\u002FProgram Files\u002FR\u002F\"` to verify R version). If tools don't appear in Claude Code, restart the session. For Claude Desktop, check firewall settings.\n\n### Step 6: Multi-Server Configuration\n\nBoth Claude Code and Claude Desktop support multiple MCP servers simultaneously:\n\n```bash\n# Claude Code: add multiple servers\nclaude mcp add r-mcptools stdio \"\u002Fpath\u002Fto\u002FRscript.exe\" -- -e \"mcptools::mcp_server()\"\nclaude mcp add hf-mcp-server -e HF_TOKEN=token -- mcp-remote https:\u002F\u002Fhuggingface.co\u002Fmcp\nclaude mcp add custom-server stdio \"\u002Fpath\u002Fto\u002Fserver\" -- --port 3001\n```\n\n**Got:** Multiple MCP servers configured and accessible simultaneously. `claude mcp list` shows all servers. Each server's tools are available in the same Claude Code session.\n\n**If fail:** If servers conflict, check that each has a unique name in the configuration. If one server blocks others, verify servers use non-blocking I\u002FO (stdio transport handles this automatically).\n\n## Validation\n\n- [ ] `claude mcp list` shows all configured servers\n- [ ] R MCP server responds to tool calls\n- [ ] Hugging Face MCP server authenticates and responds\n- [ ] Both Claude Code and Claude Desktop can connect (if both configured)\n- [ ] MCP tools appear in the tool list during sessions\n\n## Pitfalls\n\n- **Windows path spaces**: Use 8.3 short names or quote paths correctly. Different tools parse paths differently.\n- **Token in command args**: On Windows, `--header \"Authorization: Bearer token\"` fails due to parsing. Use environment variables instead.\n- **Confusing Claude Code and Claude Desktop configs**: These are separate tools with separate config files (`~\u002F.claude.json` vs `%APPDATA%\\Claude\\`)\n- **npx vs global install**: `npx mcp-remote` may fail in Claude Desktop context. Install globally with `npm install -g mcp-remote`.\n- **mcptools version**: Ensure mcptools is up to date. It requires the `ellmer` package as a dependency.\n\n## Related Skills\n\n- `build-custom-mcp-server` - creating your own MCP server\n- `troubleshoot-mcp-connection` - debugging connection issues\n- `setup-wsl-dev-environment` - WSL setup prerequisite\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},"mcp, claude-code, claude-desktop, mcptools, configuration","Philipp Thoss","mcp-integration","1.0","multi","intermediate","Julius Brussee homage — caveman","Configure MCP (Model Context Protocol) servers for Claude Code and Claude Desktop. Covers mcptools setup, Hugging Face integration, WSL path handling, and multi-client configuration. Use when setting up Claude Code to connect to R via mcptools, configuring Claude Desktop with MCP servers, adding Hugging Face or other remote MCP servers, or troubleshooting MCP connectivity between clients and servers.\n","Read Write Edit Bash Grep Glob","82c77053","en","2026-04-19","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fconfigure-mcp-server",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 configure-mcp-server",{"tool":51,"command":52},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill configure-mcp-server",{"tool":54,"command":55},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill configure-mcp-server","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fconfigure-mcp-server\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",[],[]]