evidence-hygiene

Sanitize, label, and store operational evidence such as screenshots, HAR files, logs, and release artifacts.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill evidence-hygiene-ravenslight2010
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evidence-hygiene
Source: https://github.com/ravenslight2010/Production-run-calculator/tree/main/.agents/skills/evidence-hygiene
Command: npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill evidence-hygiene-ravenslight2010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operational evidence like screenshots, HAR captures, logs, and test reports often contains credentials, personal data, or production records that create new security exposure when shared or stored. This Skill ensures evidence supports release, security, and incident decisions without leaking secrets or misrepresenting development results as production proof. ## Core Features & Use Cases - Classification and Sanitization: Classify artifacts by environment, data class, and audience, then mask passwords, tokens, cookies, authorization headers, signed URLs, and personal data before retention. - Artifact-Specific Handling: Apply tailored rules for screenshots, HAR/network captures, logs, browser traces, reports, and integrity hashes, including SHA-256 verification of retained ZIP inventory reports. - Provenance and Review: Record capture time, environment, revision, producing workflow, and sanitization performed, with a review checklist that blocks fixture evidence from being presented as production proof. - Use Case: During a release review, a HAR file from a production login test contains cookies and Authorization headers. The Skill strips the credentials, summarizes the sanitized requests, records provenance, and stores only what the release workflow needs. ## Quick Start Ask the assistant to sanitize and label the attached HAR file and screenshots from a production test before adding them to the release report.

Frequently Asked Questions about evidence-hygiene

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

FAQPage Schema
How do I sanitize a HAR file before sharing it?

Remove cookies, authorization headers, tokens, request bodies, sensitive query values, and response payloads from the HAR capture. Prefer retaining a short sanitized request summary rather than the full raw file.

How to handle screenshots containing credentials or personal data?

Crop screenshots to the relevant surface and mask identities, account data, browser chrome, and URLs with sensitive queries. Never paste secret values into filenames, report titles, or metadata.

Can development screenshots be used as production release evidence?

No. Development or fixture evidence must never be presented as production proof. Label the actual environment and gather revision-bound production evidence through the owning release workflow instead.

What information should evidence provenance include?

Record capture time, environment, revision or build identity (or explicitly unknown), the command or user flow that produced it, whether data was fixture or production, sanitization performed, and unresolved gaps.

When is it safe to delete test traces and evidence?

Retain evidence required by the owning release workflow until verification completes, then remove unnecessary sensitive intermediates. Deletion is destructive, so obtain approval before removing user-provided evidence unless deletion was already requested.