enumerate

Enumerate scanner scope items and update coverage manifest with commit hash.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Enumerate Scanner Scope skill creates or updates a manifest that tracks every item in a scanner's scope, enabling consistent progress tracking across sessions.

Core Features & Use Cases

  • Generate an initial coverage manifest by enumerating all items in the scanner's scope.
  • Detect changes across re-enumerations and update the manifest accordingly.
  • Ensure deterministic ordering of manifest entries (alphabetical by path) to simplify diffs and audits.
  • Record the target repository commit hash and per-item statuses for traceability.
  • Use case: audit a scanner's scope to confirm all in-scope items are accounted for and ready for scanning.

Quick Start

Enumerate the items in the specified scanner path to create or refresh its coverage manifest.

Frequently Asked Questions about enumerate

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

FAQPage Schema
How do I generate a scanner coverage manifest to track audit progress?

A scanner coverage manifest tracks every item within a scanner's scope for consistent progress auditing across sessions. It records per-item statuses, the repository commit hash, and progress metrics to ensure all in-scope items are accounted for.

How do I create an initial coverage manifest for a scanner path?

Provide the scanner definition path and the Skill extracts its scope to enumerate all in-scope items. It then writes or updates the manifest at state/coverage/{scanner-id-dashed}.yaml with the item list, commit hash, and progress metrics.

How does the manifest update process handle changes across re-enumerations?

During re-enumeration, the Skill compares newly enumerated items with the existing manifest and updates item statuses accordingly. It maintains deterministic alphabetical ordering by path to simplify diffs and audits during the coverage update.

Do I need a specific scanner definition format to enumerate scope items?

You need a valid scanner definition located at the provided path so the Skill can extract its scope. The Skill reads this definition to identify boundaries and enumerate all applicable items for the coverage manifest.

What is the best way to audit a scanner's scope for completeness?

The best way to audit a scanner's scope for completeness is to generate a coverage manifest. This process records all in-scope items and their statuses, confirming every item is accounted for and ready for scanning.