finding

Log proactive discovery findings into classified Markdown reports and trackers.

3|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/fluxforgeai/ARTEMIS --skill finding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finding
Source: https://github.com/fluxforgeai/ARTEMIS/tree/main/.claude/skills/finding
Command: npx skills add https://github.com/fluxforgeai/ARTEMIS --skill finding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures proactive discoveries from analysis, reviews, or inspections and converts them into neutral, factual finding reports and structured trackers so issues are recorded, classified, and handed off to downstream workflows.

Core Features & Use Cases

  • Structured Reporting: Produce a Markdown finding report written to docs/findings/{YYYY-MM-DD_HHMM}_{name}.md using the provided template and required sections.
  • Classification & Severity: Classify each finding by type (Defect, Vulnerability, Debt, Gap, Drift) and severity (Critical, High, Medium, Low) with rationale.
  • Tracker Management: Create or update Findings Tracker files (*_FINDINGS_TRACKER.md), assign stable F-numbers, and generate recommended next-step tasks for downstream skills.
  • Use Case: During a code review or security scan, log an authorization gap as a Finding and bootstrap a tracker so investigators can take the next pipeline step.

Quick Start

Use the finding skill by issuing a concise, factual description, for example: /finding Missing companyId filter in invoices WHERE clause --authorization gap.

Frequently Asked Questions about finding

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

FAQPage Schema
How do I log code review findings into a structured Markdown report?

To log code review findings into a structured Markdown report, provide a concise factual description of the discovery. The system generates a Markdown report under docs/findings/ using a standard template with required sections for neutral, factual recording.

What is a findings tracker and how does it classify audit discoveries?

A findings tracker is a persistent record that classifies audit discoveries by type, such as Defect or Vulnerability, and severity, ranging from Critical to Low. It assigns stable F-numbers to each finding for tracking and downstream workflow handoff.

Can I use this to create a persistent tracker for security scan vulnerabilities?

Yes, you can use this to create a persistent tracker for security scan vulnerabilities. It captures proactive discoveries from security scans, classifies them by severity, and creates or updates a FINDINGS_TRACKER.md file to bootstrap investigations.

What is the best way to document technical debt and gaps during an inspection?

The best way to document technical debt and gaps during an inspection is to log them as factual discoveries. This process classifies the finding as Debt or Gap, assigns severity with rationale, and records it in a structured Markdown report.

Does the findings tracker generate next-step tasks for downstream pipelines?

Yes, the findings tracker generates recommended next-step tasks for downstream pipelines. When creating or updating tracker entries, it assigns stable F-numbers and bootstraps recommended actions to hand off issues to investigators.