skills.rest
openSUSE
openSUSEOFFICIAL
Explore all skills by this author →
Website𝕏@openSUSEGitHub

cavil-refine

Classify unresolved Cavil license snippets into patterns, ignores, globs, or notes.

63|9|Updated Oct 17, 2018
Search Tags:#pattern matching#legal compliance#spdx#sbom#license review#cavil
One-click install
npx skills add https://github.com/openSUSE/cavil --skill cavil-refine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cavil-refine
Source: https://github.com/openSUSE/cavil/tree/main/examples/skills/cavil-refine
Command: npx skills add https://github.com/openSUSE/cavil --skill cavil-refine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you clean up unresolved license matches in Cavil by deciding whether each snippet should become a reusable license pattern, a safe ignore, a globbed exclusion, a missing-license escalation, or a note.

Core Features & Use Cases

  • License Patterning: Capture SPDX tags, license declarations, and full legal texts so Cavil can resolve the same wording across future package scans.
  • Noise Filtering: Ignore log lines, build metadata, code comments, and other text that only looks license-like but is not legally meaningful.
  • Coverage Expansion: Use globs for fixture-heavy or catalog-style directories, and escalate unknown-but-real licenses to the missing-license queue when Cavil lacks the identifier.
  • Use Case: A package report contains dozens of unresolved snippets spread across README files, bundled notices, and test data; this Skill turns them into the right mix of patterns, ignores, and follow-up actions.

Quick Start

Ask the skill to review the unresolved Cavil snippets and return the correct action for each one, using reusable patterns for real license text and safe ignores for non-license noise.

Frequently Asked Questions about cavil-refine

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

FAQPage Schema
How do I resolve unresolved license snippets in an SBOM package scan?▼

You can resolve unresolved license snippets by classifying each match into a reusable pattern, ignore, glob, missing-license report, or note to clean up SBOM package scans accurately.

What is the best way to filter non-license noise from legal compliance checks?▼

Filtering non-license noise from legal compliance checks involves ignoring log lines, build metadata, and code comments that look license-like but lack legal meaning to ensure accurate SPDX tagging.

How do I create reusable license patterns for future package scans?▼

Create reusable license patterns by capturing SPDX tags, license declarations, and full legal texts so future package scans automatically resolve identical wording across mixed source trees.

When should I use globs or escalate missing licenses during a license review?▼

Use globs for fixture-heavy or catalog-style directories during license review, and escalate unknown-but-real licenses to the missing-license queue when Cavil lacks the correct SPDX identifier.

Do I need to capture the whole document to identify full legal texts for SPDX compliance?▼

Yes, SPDX compliance requires whole-document capture for full legal texts to accurately separate license wording from non-license noise and ensure correct license identification.

Why does my Cavil license review show unresolved matches in bundled notices?▼

Unresolved matches in bundled notices appear because Cavil cannot automatically classify mixed snippets; you must manually categorize them as patterns, ignores, or missing-license reports.

Related Skills

Explore More Legal & Compliance Skills→
openSUSEopenSUSE
63

cavil-review-note

Review Cavil package reports and create concise legal triage notes.

Official
Advanced
x402agentx402agent

sbom

Generate CycloneDX SBOMs for OpenShell projects and export CSV reports with resolved licenses.

Community
Advanced
Sir-chawakornSir-chawakorn
9

audit-license-compliance

Audit open-source license compliance across transitive dependency trees and classify copyleft exposure.

Community
Advanced
opendatahub-ioopendatahub-io
36

license-checker

Assess Python package license compatibility using SPDX data.

Official
Basic