finding

Structure security findings with vulnerability, impact, and remediation details.

63|8|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/JoranHonig/grimoire --skill finding-joranhonig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finding
Source: https://github.com/JoranHonig/grimoire/tree/main/skills/finding
Command: npx skills add https://github.com/JoranHonig/grimoire --skill finding-joranhonig

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill helps security researchers and teams understand and apply consistent conventions for security findings, including structure, format, and best practices, enabling faster reviews and reliable reporting.

Core Features & Use Cases

  • Teaches the standard structure of findings, including required frontmatter fields and sections, so readers can understand the issue without external context.
  • Encapsulates best practices for title construction, severity rationale, context references, and remediation guidance to improve report quality and consistency.
  • Useful for drafting new findings, reviewing existing documents, and training teams in standardized security reporting.

Quick Start

Draft a minimal finding with the required frontmatter and sections using the /finding workflow.

Frequently Asked Questions about finding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What structure should a security finding follow to be self-contained for review?

A security finding should include required frontmatter and sections articulating the vulnerability, impact, and remediation. This structure ensures the issue is understood without external context and is ready for dedup or report integration.

How do I standardize security findings across manual and automated sources?

You standardize security findings by applying consistent conventions for title construction, severity rationale, and context references across sources. This produces concise, well-formatted documents ready for reliable reporting.

What are the best practices for writing security finding titles and severity rationale?

Best practices for security findings involve constructing precise titles and providing clear severity rationale. Focusing on self-contained findings with reproducible steps and validated references improves report quality and consistency.

How do I draft a minimal security finding with markdown for quick reporting?

To draft a minimal security finding, use the /finding workflow to generate the required frontmatter and sections. This produces a concise, well-formatted markdown document ready for immediate review or dedup.

Can I use this approach to train teams in standardized security reporting?

Yes, you can use these structured security finding conventions to train teams in standardized reporting. It teaches the required frontmatter, sections, and best practices needed for faster reviews and reliable documentation.