straymark-audit-execute

Execute Charter audits in an auditor-side CLI and write schema-compliant reports.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/StrangeDaysTech/arborist-cli --skill straymark-audit-execute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: straymark-audit-execute
Source: https://github.com/StrangeDaysTech/arborist-cli/tree/main/.gemini/skills/straymark-audit-execute
Command: npx skills add https://github.com/StrangeDaysTech/arborist-cli --skill straymark-audit-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps auditors produce consistent, evidence-backed security/quality findings by executing the resolved Charter prompt inside an auditor-side CLI and writing the standardized audit report.

Core Features & Use Cases

  • Resolves the correct audit prompt by reading the canonical audit-prompt file for a specified Charter ID or auto-selecting the single pending prompt for the current model.
  • Performs the audit with tool use while enforcing read-only behavior and requiring every finding to cite the exact path:line of files actually opened.
  • Writes a model-scoped, schema-compliant report to the canonical report-<model-slug>.md path so a later review step can consolidate results.

Quick Start

Invoke /straymark-audit-execute CHARTER-NN from your auditor-side CLI to generate the audit report for that Charter.

Frequently Asked Questions about straymark-audit-execute

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

FAQPage Schema
How do I run an automated security audit that enforces read-only file access?

Run a read-only security audit by invoking the audit execution from an auditor-side CLI, which consumes a resolved Charter audit-prompt and strictly enforces read-only behavior during the tool-using review process.

How to generate a schema-based audit report with evidence citations?

Generate a schema-based audit report by executing the audit prompt, requiring every finding to cite exact path:line evidence from actual file reads, and writing the final output to a canonical report path following audit-output.schema.v0.json.

What is a Charter audit and when do I need evidence-citation in path:line format?

A Charter audit is a standardized security review process that requires evidence-citation in path:line format, ensuring every finding references exact lines from actual file reads to prevent fabricated results.

Can I run parallel audits across multiple model families using the same Charter?

Yes, you can run parallel audits across multiple model families by auto-selecting pending prompts per auditor model slug, generating model-scoped reports for each, and later consolidating them via a review skill.

Does the audit execution tool support multi-CLI audit cycles?

Yes, the audit execution supports multi-CLI audit cycles by allowing operators to run multiple model families in parallel, each writing a model-scoped report to a canonical report path for later consolidation.