guild-audit

Audit Guild plugin scripts for SHA256 hashes, source provenance, and access patterns.

6|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/lookatitude/guild --skill guild-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guild-audit
Source: https://github.com/lookatitude/guild/tree/main/skills/meta/audit
Command: npx skills add https://github.com/lookatitude/guild --skill guild-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a static audit of Guild plugin scripts, enumerating SHA256 hashes, source provenance, and access patterns to detect egress and filesystem writes.

Core Features & Use Cases

  • Audit executable artifacts shipped with the plugin (hooks, tooling scripts, optional MCP servers) for safety and compliance.
  • Generate a dated report listing file hashes, declared tool access, network and filesystem activity, and writes outside the .guild directory.
  • Use Case: Maintain secure, auditable plugin deployments by verifying integrity and access restrictions before upgrading or installing.

Quick Start

Run the /guild:audit command to generate the latest static report of all audited scripts and MCP servers.

Frequently Asked Questions about guild-audit

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

FAQPage Schema
How do I check Guild plugin scripts for network access and filesystem writes?

You can statically audit Guild plugin scripts to detect network egress and filesystem writes outside the .guild directory. This process enumerates source provenance and SHA256 hashes for executable artifacts to produce a dated compliance report.

What is a static audit of Guild plugin hooks and tooling scripts?

A static audit of Guild plugin scripts is a safety analysis that enumerates SHA256 hashes, source provenance, and access patterns. It inspects executable artifacts like hooks, tooling scripts, and optional MCP servers to detect egress and filesystem writes.

How do I verify the integrity of Guild plugin executable artifacts before installing?

To verify Guild plugin integrity before installing, you generate a static audit report that specifies SHA256 hashes for all shipped executable artifacts. This report also details declared tool access and source provenance for compliance verification.

Can I audit optional MCP servers shipped with Guild plugins for filesystem restrictions?

Yes, you can audit optional MCP servers shipped with Guild plugins. The audit enforces meta-skill filesystem restrictions by detecting writes outside the .guild directory and reviewing network and filesystem activity for all executable artifacts.

What limitations apply when auditing Guild plugin scripts for egress and writes?

The static audit is limited to analyzing executable artifacts shipped with the Guild plugin, including hooks, tooling scripts, and MCP servers. It enforces filesystem restrictions specifically for writes outside the .guild directory and detects declared network activity.