working-with-evidence-plugins

Select evidence plugins and discover their schemas for Fianu compliance controls.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When designing compliance controls on the Fianu platform, agents must pick the right evidence plugin and understand the exact shape of that plugin's evidence output before writing Rego rules. Choosing the wrong plugin or referencing nonexistent schema fields produces controls that cannot evaluate policy correctly. ## Core Features & Use Cases - Plugin Catalog Lookup: Maps evidence types (SAST, SCA, container scanning, SBOM, signature, DAST, IaC, testing, deployment, pipeline, code review, access control) to candidate plugins via a categorized reference catalog. - Schema Discovery: Queries GET /controls/:entity_key/schemas?producer={pluginPath} to retrieve the field paths and types available in a plugin's evidence output for Rego rule authoring. - Fallback Guidance: Recommends API-sourced controls when no plugin covers the required evidence, and handles edge cases like plugins present in the catalog but not enabled in the target tenant. - Use Case: Given a requirement for container image vulnerability evidence, consult the catalog to shortlist Prisma, Wiz, Trivy, or Lacework, then run schema discovery on each candidate and pick the plugin whose fields best cover the requirement. ## Quick Start Ask the agent to pick an evidence plugin for a new control requiring dependency vulnerability scanning and show the schema fields available for its Rego rule.

Frequently Asked Questions about working-with-evidence-plugins

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

FAQPage Schema
How do I choose an evidence plugin for a Fianu control?▼

Identify the requirement's evidence type, map it to a plugin category in the catalog, then run schema discovery on each candidate plugin. Prefer the plugin whose schema fields cover the requirement with the fewest gaps.

How do I discover a plugin's evidence schema in Fianu?▼

Call GET /controls/:entity_key/schemas?producer={pluginPath} after choosing a candidate plugin. The response lists the field paths and types in the plugin's evidence output, which Rego rules reference as input.detail fields.

What evidence types do Fianu plugins cover?▼

The catalog covers SAST, SCA, container scanning, SBOM, signature verification, DAST, IaC scanning, testing, deployment records, CI/CD pipeline execution, code review, and access control. Example plugins include Sonarqube, Snyk, Trivy, Sigstore, and Checkov.

What if no plugin covers my control's evidence requirement?▼

Recommend an API-sourced control instead of a plugin-sourced one. The control subscribes to an api event source as a custom integration, as described in the platform best practices for choosing sources.

Why does schema discovery return empty for a cataloged plugin?▼

The catalog reflects what fianu-plugins ships, not what a tenant has enabled. An empty or 404 response means the plugin is not deployed in the target environment; escalate to a human or recommend enabling the plugin.