harness-rules

Display applied security rules and latest block reasons from ai-harness logs.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/cano721/ai-harness --skill harness-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-rules
Source: https://github.com/cano721/ai-harness/tree/main/skills/harness-rules
Command: npx skills add https://github.com/cano721/ai-harness --skill harness-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Displays the currently applied security rules and the most recent blocking reason to help teams audit and adjust policy quickly.

Core Features & Use Cases

  • Global and team-specific rule visibility, including the latest block events.
  • Concise audit trail from logs and policy definitions to facilitate governance reviews.
  • Use Case: When a block occurs, review the rule, tool, and reason to determine remediation steps.

Quick Start

Ask Harness to display the currently active rules and the most recent block reason.

Frequently Asked Questions about harness-rules

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

FAQPage Schema
How do I check active security rules and recent block reasons in ai-harness?

To check active security rules and recent block reasons in ai-harness, review the categorized global, team, and guardrail rules summarized from config.yaml and lock-policy.yaml, alongside the latest block events fetched from logs.

Why does an ai-harness guardrail block my workflow?

An ai-harness guardrail blocks your workflow when an action violates defined security policies. You can identify the specific rule, tool, and exact blocking reason by reviewing the latest block events recorded in the logs directory.

How can I audit team-level lock policies from ai-harness logs?

You can audit team-level lock policies by reading templates/lock-policy.yaml and fetching recent block events from .ai-harness/logs/. This presents a categorized view of team-specific rules to support rapid governance reviews and remediation.

Does the harness-rules audit require external dependencies?

No, the harness-rules audit requires no external dependencies. It operates internally by reading .ai-harness/config.yaml, templates/lock-policy.yaml, and log files to display currently applied security rules and blocking reasons.

What is the best way to review ai-harness block events for remediation?

The best way to review ai-harness block events for remediation is to examine the summarized block reasons, associated tools, and triggered rules. This concise audit trail from logs and policy definitions helps determine the exact steps needed to resolve the block.

Can I view global and team-specific guardrail rules together?

Yes, you can view global and team-specific guardrail rules together. The tool presents a categorized view that summarizes global rules, team-level rules, and recent block events from policy definitions and logs in a single display.