Ra Qm Skills

What Ra Qm Skills is

Ra Qm Skills is a plugin published in the borghei/Claude-Skills repository on GitHub, which has about 834 stars. The repository describes itself as: “372 AI skills, 76 expert agents, and 867 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, and research. Installs on Claude Code, Cursor, Codex, Gemini, Copilot, and 6 other AI assistants.”

A plugin is a package that bundles skills, slash commands, subagents, hooks, and MCP connectors so they install together. Plugins are plain files with a manifest at .claude-plugin/plugin.json, and they work in both Claude Code and Claude Cowork.

Installing Ra Qm Skills adds everything it ships in one step. Connectors inside a plugin still need to be connected separately, and hooks and subagents only run in Cowork and Claude Code, not in regular chat.

How to install Ra Qm Skills

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

The repository does not declare an open-source license, so we list only the outline of the file here. Read the full text on GitHub.

• 📚 Table of Contents
• ⚡ Installation
• Whole domain (Claude Code plugin)
• Individual skills (any assistant)
• 🎯 Overview
• 🏗️ Skills Architecture
• Strategic Leadership Layer (2 Skills)
• Core Quality Management Layer (3 Skills)
• Risk & Security Management Layer (2 Skills)
• Regulatory Specialization Layer (2 Skills)
• Audit & Compliance Layer (3 Skills)
• 📦 Complete Skills Catalog
• 1. Senior Regulatory Affairs Manager (Head of Regulatory Affairs)
• 2. Senior Quality Manager Responsible Person (QMR)

Open plugin.json on GitHub

Before you install

• Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
• Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
• Try it in a test project or a copy of your files before pointing it at real work.
• Pin the version you tested, and review changes before updating.
• Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ