metadata

Fetch repository metadata and write it to report.json.

Updated May 20, 2026

Search Tags:#api #repository #metadata #network #lookup #scans

Ready to run

npx skills add https://github.com/lukehinds/scrutineer-attest-test --skill metadata-lukehinds

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: metadata
Source: https://github.com/lukehinds/scrutineer-attest-test/tree/main/skills/metadata
Command: npx skills add https://github.com/lukehinds/scrutineer-attest-test --skill metadata-lukehinds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically fetch and store high-level repository metadata to populate scan records and keep repository context up to date.

Core Features & Use Cases

Retrieve fields such as full_name, owner, description, default_branch, languages, license, stars, forks, archived, pushed_at, html_url, and icon_url and write them to report.json.
Use this data to initialize repository context for new scans or refresh metadata after upstream changes.
Supports mapping outputs to a predefined schema used by downstream parsers.

Quick Start

Read the context.json to obtain repository.url and perform the metadata lookup to populate report.json.

Frequently Asked Questions about metadata

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

FAQPage Schema

How do I fetch repository metadata for scans?▼

Fetch repository metadata by reading the repository URL from context.json and performing a network lookup to populate report.json. This retrieves fields like full_name, owner, description, default_branch, and languages for scan initialization.

How do I refresh repository metadata after upstream changes?▼

Refresh repository metadata after upstream changes by running the skill lookup again to overwrite report.json. This updates fields like stars, forks, pushed_at, and license with the latest upstream repository data.

Can I use this skill to initialize repository context for new scans?▼

Yes, you can initialize repository context for new scans by retrieving metadata fields such as default_branch, languages, and license. The skill maps these outputs to a predefined schema used by downstream parsers.

What repository fields are mapped by this metadata lookup?▼

The metadata lookup maps full_name, owner, description, default_branch, languages, license, stars, forks, archived, pushed_at, html_url, and icon_url according to the provided schema for downstream scan processing.

Does this skill require any dependencies to fetch repository metadata?▼

No external dependencies are required to fetch repository metadata. The skill operates independently by performing an API network lookup based on the repository URL found in context.json to generate the report.

Why do I need to fetch repo metadata before scanning?▼

Fetching repo metadata before scanning populates scan records with high-level context such as archived status and pushed_at timestamps. This ensures downstream parsers have accurate repository context for processing.