caro.security.update SKILL.md skillA
caro.security.update from wildcard/caro is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wildcard/caro/caro.security.update@git:20260423.8aea70dPins git:20260423.8aea70d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wildcard/caro
- Path
.claude/skills/caro.security.update/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260423.8aea70d, committed Apr 23, 2026
- Size
- 7,414 bytes
- Repository stars
- 40
- License
- AGPL-3.0
Maintainer skill to draft a CVE rule YAML via Nimble for a specific CVE, fill pattern + test_cases, and open a PR. Used off-cycle when a 0day lands between weekly cron runs.
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
# caro.security.update Skill **Purpose**: Manually trigger the Nimble CVE authoring pipeline for a single CVE (or a batch) outside the weekly cron window. Use this when a high-severity 0day is disclosed and protection shouldn't wait until Monday 09:00 UTC. **Spec**: `specs/010-nimble-cve-pipeline/` **Companion workflow**: `.github/workflows/cve-rule-sync.yml` **Orchestrator script**: `scripts/nimble-cve-sync.ts` --- ## When to Use - A CVE or 0day lands with CVSS ≥ 7.0 and a plausible shell-invocation vector - The weekly cron won't run for > 24h and the exposure window matters - You want to re-author an existing rule after the advisory was amended - You are reviewing an auto-drafted PR and want to fill the `TODO_NIMBLE_AUTHORED` placeholder without leaving the CLI **Do not use** for: - Non-shell CVEs (daemons, kernels, libraries without a shell attack surface) - User-local custom rules — that's Dogma tier-3 (`~/.caro/rules/`) - Generic pattern additions not tied to a CVE — use `safety-pattern-developer` instead --- ## Prerequisites - Maintainer access to `wildcard/caro` - Working `gh` CLI auth - `scripts/node_modules/` installed (`cd scripts && npm ci`) …
Read the whole file at its exact version.
How to install
mdr add wildcard/caro/caro.security.update@sha256:dab64af34b0bdf9dThe line at the top of this page pins the label git:20260423.8aea70d, 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_z5uipqkkrizxdafh)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Apr 23, 2026.
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 (7414 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
wildcard/caro · 40 stars · license AGPL-3.0 · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_z5uipqkkrizxdafh GET https://markdownregistry.com/api/v1/resolve?ref=wildcard/caro/caro.security.update GET https://markdownregistry.com/api/v1/blob/dab64af34b0bdf9dd23636cc187312571d775a8070461289c5a0ac5767fffbb6
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.