Create and manage markdown vulnerability pattern checks for code flaw detection.
npx skills add https://github.com/JoranHonig/grimoire --skill checks-joranhonig
Please help me install this Agent Skill. Skill: checks Source: https://github.com/JoranHonig/grimoire/tree/main/skills/checks Command: npx skills add https://github.com/JoranHonig/grimoire --skill checks-joranhonig
This skill should be used when the user says "create a check", "write a check", "add a check", "apply checks", "run checks", "/checks", "vulnerability pattern", "detection check", "check for common bugs", "scan with checks", or wants to create, apply, or manage simple vulnerability pattern files that agents use to find flaws. Checks are the simplest unit of agentic vulnerability detection — markdown files describing what to look for and how to assess matches.
Create, apply, and manage vulnerability pattern checks — simple markdown files that describe what to look for in a codebase and how to assess matches. Manage a scalable library of checks with scripts for indexing and validation. Use cases include detecting common bugs, guiding agent reasoning, and ensuring consistency across audits.
Create, index, and apply vulnerability pattern checks within grimoire/spells/checks/ to start scanning a codebase.
High-intent search queries and answers about installing and using this skill.
Vulnerability pattern checks are simple markdown files describing what to look for and how to assess matches. You create them by defining frontmatter with a name and description, then store them within the grimoire/spells/checks/ directory to scan your codebase for common bugs.
Vulnerability detection checks are markdown files that describe specific code flaws to find and how to evaluate them. They guide code review by providing the simplest unit of agentic vulnerability detection, ensuring consistency across audits by directing agent reasoning during scans.
You validate and index markdown vulnerability checks using the index-checks.sh and validate-check.sh scripts. These scripts coordinate indexing and enforce metadata consistency, ensuring that frontmatter properly defines required name and description fields for each check file.
Yes, vulnerability checks can be applied across multiple programming languages. The checks are markdown-based pattern files that describe what to look for in a codebase, allowing you to select and apply applicable checks to detect flaws regardless of the target language.
The best way to manage a scalable library of vulnerability checks is to store them as markdown files in grimoire/spells/checks/ and use the provided indexing and validation scripts. This approach enforces metadata consistency and allows you to select applicable checks for target codebases easily.
Vulnerability checks require frontmatter metadata because the validate-check.sh script enforces it to maintain consistency. The frontmatter must define both a name and description for the check, ensuring the markdown pattern files are properly indexed and can be selected for codebase scans.
chambear2809Render and validate Splunk SmartStore index lifecycle configuration templates.
jeremylongshoreScan codebases, dependencies, and configurations for security vulnerabilities and CVEs.
JoranHonigRemove contents of the librarian cache directory after user confirmation.
sovriumIdentify security vulnerabilities in codebases via static analysis.
