scan

Run audit scanners against ODD repositories and document findings with Gate 9 citations.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/opendatadiscovery/odd-team --skill scan-opendatadiscovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan
Source: https://github.com/opendatadiscovery/odd-team/tree/main/.claude/skills/scan
Command: npx skills add https://github.com/opendatadiscovery/odd-team --skill scan-opendatadiscovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates running an audit scanner against ODD repositories to discover and document findings with Gate 9 citations.

Core Features & Use Cases

  • Orchestrates loading scanner definitions, enumerating targets from a coverage manifest, and emitting structured findings.
  • Maintains deduplication by cross-referencing existing findings across scanners and updating enrichment sections.
  • Keeps navigation, progress, and manifest artifacts in sync for reproducible scans.

Quick Start

Run the scan command with a scanner path to begin auditing the target repository.

Frequently Asked Questions about scan

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

FAQPage Schema
How do I automate an audit scanner against a repository?

To automate a repository audit scanner, this Skill loads scanner definitions, selects unscanned items from a coverage manifest, emits structured findings, and updates navigation and progress manifests.

What is the best way to deduplicate audit findings across multiple scanners?

Deduplicating audit findings is handled by cross-referencing existing findings across scanners and updating enrichment sections to maintain a clean, reproducible scan history.

How does a coverage manifest track progress during repository navigation and scanning?

A coverage manifest tracks progress by selecting unscanned items as targets, updating their status after scanning, and keeping navigation and progress metadata in sync for reproducible scans.

Can I cite source of truth sources for every finding generated during an audit scan?

Yes, citing source of truth sources for every finding generated during an audit scan is a core requirement satisfied by emitting structured findings with Gate 9 citations.

What is needed to start orchestrating ODD repo audits with automated scans?

To start orchestrating ODD repo audits, run the scan command with a scanner path to begin auditing the target repository and generating structured findings.