the-sentinel

Audit Agenthood member files for consistency and drift against The Oracle's template.

2|Updated May 23, 2026
One-click install
npx skills add https://github.com/fworks-tech/agenthood --skill the-sentinel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: the-sentinel
Source: https://github.com/fworks-tech/agenthood/tree/main/members/the-sentinel
Command: npx skills add https://github.com/fworks-tech/agenthood --skill the-sentinel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Sentinel protects Agenthood's integrity by auditing member files for internal consistency, detecting cross-member contradictions, verifying lane ownership, and preventing structural drift relative to The Oracle's canonical template.

Core Features & Use Cases

  • Cross-member contradiction detection between member rules and responsibilities.
  • Internal consistency audits that align Process, Red Flags, Rationalizations, and When to Use.
  • Lane overlap detection and a lane map to ensure distinct ownership of domains.
  • Structural drift prevention by comparing member files to The Oracle's canonical template.
  • Staleness detection to flag references that have become obsolete or superseded.

Quick Start

Run the sentinel audit at the repository root to perform a full integrity check across all member files.

Frequently Asked Questions about the-sentinel

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

FAQPage Schema
How do I audit member files for internal consistency and drift?

To audit member files for internal consistency and drift, you run an integrity check against a canonical template. This detects contradictions, lane overlaps, and structural drift across member documents during creation, updates, or governance reviews.

What is document drift detection and when do I need it?

Document drift detection identifies when member files deviate from a canonical template over time. You need it during new member creation, member updates, or periodic governance reviews to catch obsolete references and structural inconsistencies.

How do I detect cross-member contradictions in governance documents?

Detecting cross-member contradictions involves auditing member files for overlapping lanes and conflicting rules. The audit checks Red Flags alignment, Process-Verification consistency, and When-to-Use versus Process to ensure distinct domain ownership.

Can I use a template audit for periodic governance reviews?

Yes, you can use a template audit for periodic governance reviews. It compares member files against a canonical template to verify structure, detect staleness in references, and ensure cross-member rules remain aligned without contradictions.

What is the best way to prevent structural drift in member documentation?

Preventing structural drift in member documentation requires comparing files against a canonical template during creation and updates. This approach catches misaligned Red Flags, Process-Verification mismatches, and lane overlaps before they compromise document integrity.

What are the limitations of automated consistency audits for member files?

Automated consistency audits for member files are limited to detecting structural drift, lane overlaps, and template misalignment. They do not resolve the contradictions found; they only flag issues in Red Flags alignment, Process-Verification, and When-to-Use sections for manual review.