-21risk-automation SKILL.md skillA
-21risk-automation from composiohq/awesome-claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add composiohq/awesome-claude-skills/-21risk-automation@git:20260219.2790447Pins git:20260219.2790447 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- composiohq/awesome-claude-skills
- Path
composio-skills/-21risk-automation/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260219.2790447, committed Feb 19, 2026
- Size
- 2,914 bytes
- Repository stars
- 79,837
- License
- none declared
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 21risk Automation via Rube MCP
Automate 21risk operations through Composio's 21risk toolkit via Rube MCP.
**Toolkit docs**: [composio.dev/toolkits/_21risk](https://composio.dev/toolkits/_21risk)
## Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active 21risk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `_21risk`
- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
## Setup
**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `_21risk`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows
## Tool Discovery
Always discover available tools before executing workflows:
```
RUBE_SEARCH_TOOLS
queries: [{use_case: "21risk operations", known_fields: ""}]
session: {generate_id: true}
```
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
## Core Workflow Pattern
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qwbmka6hhmwa4g6s/eeacdabb1e844f3f52d66d3899e22c648052f0ff2ff5a16c07d3afca16bd3730.json
Then /plugin install 21risk-automation@markdownregistry-qwbmka6hhmwa4g6s in Claude Code. It installs git:20260219.2790447, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add composiohq/awesome-claude-skills/-21risk-automation@sha256:eeacdabb1e844f3fThe line at the top of this page pins the label git:20260219.2790447, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qwbmka6hhmwa4g6s)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in composiohq/awesome-claude-skills/-21risk-automation since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of -21risk-automation from somewhere else? Ask it: where did my -21risk-automation come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Feb 19, 2026.
Watch this file (sign in, one email per new version)
Copies
1 file in 1 other repository holds the exact bytes of one of this file's versions, each committed after this file had them: it holds the newest version.
A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/-21risk-automation/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2914 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
composiohq/awesome-claude-skills · 79,837 stars · license none declared · pushed 2026-09-18 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_qwbmka6hhmwa4g6s GET https://markdownregistry.com/api/v1/resolve?ref=composiohq/awesome-claude-skills/-21risk-automation GET https://markdownregistry.com/api/v1/blob/eeacdabb1e844f3f52d66d3899e22c648052f0ff2ff5a16c07d3afca16bd3730
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from composiohq/awesome-claude-skills
Every file in composiohq/awesome-claude-skills