skills.rest
ArabelaTso
ArabelaTsoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-boundary-reporter

Analyze Isabelle, Coq, and Dafny artifacts to report verified and unverified components.

142|14|Updated Feb 14, 2026
Search Tags:#formal verification#coq#isabelle#code auditing#trust boundary#dafny#proof analysis
One-click install
npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill verification-boundary-reporter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-boundary-reporter
Source: https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/verification-boundary-reporter
Command: npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill verification-boundary-reporter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill clarifies the exact boundaries of formal verification within your codebase, identifying what is proven, what is assumed, and what remains unverified.

Core Features & Use Cases

  • Verification Auditing: Precisely document the scope and limitations of formal proofs.
  • Trust Boundary Analysis: Clearly delineate between verified code, assumptions, and the trusted computing base (TCB).
  • Use Case: When presenting a formally verified system, use this Skill to generate a report that explicitly lists all axioms, assumptions, and external dependencies, providing a clear picture of the system's trustworthiness.

Quick Start

Analyze the provided Isabelle/HOL artifacts to generate a verification boundary report.

Frequently Asked Questions about verification-boundary-reporter

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

FAQPage Schema
How do I audit formal verification coverage in Coq or Isabelle?▼

Trust boundary analysis explicitly delineates between verified code, underlying assumptions, and the trusted computing base elements. It identifies what is proven, what is assumed, and what remains unverified in formal verification artifacts.

Can I use Dafny proof artifacts to document the trusted computing base?▼

To generate a verification boundary report, analyze formal verification artifacts from systems like Isabelle, Coq, or Dafny. The resulting report explicitly lists all axioms, verified components, and unverified code for auditing purposes.

What is the best way to list unverified code and axioms in formal proofs?▼

When presenting a formally verified system, you should explicitly list all axioms, assumptions, and external dependencies. This delineates the trust boundaries and provides a clear picture of the system's overall trustworthiness.

Does verification boundary reporting work for assessing proof limitations?▼

Yes, verification boundary reporting works for assessing proof limitations by precisely documenting the scope of formal proofs. It explicitly lists assumptions, axioms, and trusted computing base elements to clarify what remains unverified.

Related Skills

Explore More Software Engineering Skills→
ArabelaTsoArabelaTso
142

verified-spec-code-mapper

Map formal specifications to verified code components in Markdown reports.

Community
Advanced
aist-ai-sastaist-ai-sast

aist-security-check

Audit changed files for security risks and produce remediation findings.

Official
Advanced
jeffrey-dot-lijeffrey-dot-li
2

fill-sorry

Prove specified sorry'd lemmas iteratively in Lean using LSP tools.

Community
Advanced
jeffrey-dot-lijeffrey-dot-li
2

refactor

Refactor existing Lean proofs for brevity, clarity, and documentation.

Community
Intermediate