evidence

Collects and stores timestamped compliance evidence snapshots for audits in cloud environments.

7|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kkmookhey/shasta --skill evidence-kkmookhey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evidence
Source: https://github.com/kkmookhey/shasta/tree/main/.claude/skills/evidence
Command: npx skills add https://github.com/kkmookhey/shasta --skill evidence-kkmookhey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collects and stores point-in-time compliance evidence snapshots to build a reliable audit trail for SOC 2, ISO 27001 and related frameworks.

Core Features & Use Cases

  • Timestamped evidence collection during cloud scans to support audits.
  • Generates a structured inventory of artifact types and provenance for auditors.
  • Provides repeatable monthly evidence capture to maintain a consistent audit trail.

Quick Start

Run the evidence collection workflow using the configured Python command to collect and save all evidence files for a scan.

Frequently Asked Questions about evidence

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

FAQPage Schema
Can I use this to generate audit trails for ISO 27001 and HIPAA in cloud environments?

The evidence collection process executes a full cloud scan to capture and save timestamped audit artifacts, generating a structured inventory of artifact types and provenance for auditors.

Do I need a shasta.config.json file to run the evidence collection workflow?

You can set up repeatable monthly evidence capture by running the configured Python command on demand, which executes the full scan and persists the artifact records automatically.

What is the best way to build a structured inventory of artifact types for auditors?

Yes, the evidence collection workflow integrates with shasta.config.json to determine the python_cmd and execute the full scan plus evidence collection to generate and persist artifact records.

Why does my evidence collection workflow need a configured python_cmd?

The best way to build a structured inventory of artifact types for auditors is to run a full cloud scan that automatically generates and persists provenance records for each captured artifact.

Why does my evidence collection workflow need a configured python_cmd?

The workflow needs a configured python_cmd specified in shasta.config.json to properly execute the full scan and evidence collection process for generating and persisting artifact records.