Park Audit

Identify high-risk assumptions, unsafe releases, and missing evidence in an enclosure.

20|3|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/sigridjineth/clawpark --skill park-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Park Audit
Source: https://github.com/sigridjineth/clawpark/tree/main/integrations/openclaw-marketplace-examples/park-audit-skill
Command: npx skills add https://github.com/sigridjineth/clawpark --skill park-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Park Audit identifies high-risk assumptions, unsafe releases, and missing evidence within a project enclosure, enabling teams to surface issues before they escalate.

Core Features & Use Cases

  • Identify the highest-risk assumption to focus remediation efforts.
  • Verify whether evidence is current and complete.
  • Capture and summarize audit findings for stakeholder review.

Quick Start

Run the Park Audit script to scan the current enclosure and produce an actionable audit summary.

Frequently Asked Questions about Park Audit

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

FAQPage Schema
How do I identify high-risk assumptions in a software deployment?

To identify high-risk assumptions in a software deployment, run a checklist-driven audit script that scans your project enclosure to surface unsafe releases and missing evidence. It produces an actionable summary for stakeholder review.

What is a checklist-driven compliance audit for project enclosures?

A checklist-driven compliance audit evaluates your project enclosure to verify whether safety and traceability evidence is current and complete. It identifies the highest-risk assumptions to focus remediation efforts before issues escalate.

How do I check for missing evidence in a workspace before a release?

You can check for missing evidence in a workspace by running a local Python audit script against the enclosure. This verifies whether governance evidence is complete and captures findings to review before an unsafe release escalates.

Can I use a Python script to audit software project safety and governance?

Yes, you can use a local Python script to audit software project safety and governance. The script applies a references checklist to evaluate your enclosure and summarize audit findings for stakeholder review.

What is the best way to capture audit findings for stakeholder review?

The best way to capture audit findings for stakeholder review is to run an automated script that scans for high-risk assumptions and missing evidence. It produces an actionable audit summary directly from your project enclosure.