working-with-asset-series

Query Fianu evidence attestations, violations, and gate checks across asset series dimensions.

1|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/fianulabs/fianu-skills --skill working-with-asset-series-fianulabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: working-with-asset-series
Source: https://github.com/fianulabs/fianu-skills/tree/main/skills/working-with-asset-series
Command: npx skills add https://github.com/fianulabs/fianu-skills --skill working-with-asset-series-fianulabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Evidence queries in Fianu are keyed on a series (digest, commit, tag, release, time period), and querying the wrong series returns empty results even when evidence exists. This Skill teaches how to target the correct series so attestations, violations, and findings are actually found. ## Core Features & Use Cases - Series Model Reference: Covers the full series catalog (digest/uri/commit/tag/release/timestamp/period_*), and disambiguates seriesName vs seriesCode vs seriesId vs seriesType. - Four Query Modes: Single-series snapshot and violations endpoints, cross-series association queries, series discovery via by-series, and the commit-scoped export endpoint returning full raw notes. - Use Case: A user asks why Artifact Signature or SBOM controls return empty for a commit. The Skill explains these controls land on the digest series, and directs using the by-series discovery endpoint or the export endpoint to locate the digest-keyed evidence. ## Quick Start Ask the agent to list all control results for an asset at a specific git commit, including failing violation details, using the Fianu attestations export endpoint.

Frequently Asked Questions about working-with-asset-series

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

FAQPage Schema
How do I query Fianu evidence for an asset at a specific commit?▼

Use GET /evidence/assets/:asset/attestations/snapshot?seriesId=<sha> for a single series, or GET /assets/:asset/attestations/export?commit=<sha> to get every control result at that commit with full raw notes, measured values, and violation rows.

Why do Artifact Signature, SBOM, or Artifact Version controls return empty results?▼

These build-info controls typically land on the digest series, not commit, because their plugins emit digests. Querying only the commit series misses them; use the by-series discovery endpoint or the export endpoint to find digest-keyed evidence.

What is the difference between seriesName, seriesCode, seriesId, and seriesType in Fianu?▼

seriesName is the catalog dimension (digest, commit, tag), seriesCode is its integer pair (2110-2122), and seriesId is the actual value like a SHA or digest. seriesType is either primary/association on stored evidence or branch/commit in batch snapshot requests.

How do cross-series association queries work in the Fianu snapshot endpoint?▼

Posting a non-empty associations array to the snapshot endpoint widens the query to evidence on any series linked to the same notes. Each additional association entry adds a conjunctive AND filter, so entries narrow results rather than union them.

Why does the attestations export endpoint return an empty attestations array?▼

The export endpoint expects a commit query parameter, not seriesId; passing seriesId is silently ignored and binds an empty string. It is also commit-series only, so digest-keyed evidence needs the snapshot or by-series endpoints instead.

What are the limitations of the Fianu batch snapshot endpoint?▼

Batch snapshot caps at 100 items, validates seriesType to branch or commit only, and never populates associations, so it cannot expand one series into another. Overview projection is rejected when any item uses last-N mode.