agent-conduct

Enforce shared governance rules across squad agents via YAML frontmatter.

Updated Aug 23, 2026

Search Tags:#compliance #agent #governance #ci-cd #tests #peer-quality

Ready to run

npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill agent-conduct-carlossardo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-conduct
Source: https://github.com/CarlosSardo/nats-poc-simulator/tree/main/.copilot/skills/agent-conduct
Command: npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill agent-conduct-carlossardo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shared hard rules for all squad agents are centralized and consistently enforced, eliminating duplication and drift across charters.

Core Features & Use Cases

Centralized governance: two hard rules (Product Isolation Rule and Peer Quality Check) apply to all agents.
Consistency across squads: prevents hard-coded agent names in tests, CI configs, and product logic.
Ease of activation: loaded once and used by all activation workflows for charter creation and review.

Quick Start

Apply the agent-conduct governance checks to all squad agents during charter creation and peer review.

Frequently Asked Questions about agent-conduct

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

FAQPage Schema

How do I enforce consistent agent governance across multiple squads?▼

Agent governance is enforced by applying centralized hard rules to all squad agents, ensuring consistent behavior and naming practices while eliminating policy duplication and drift across charters.

What is the best way to prevent hardcoded agent names in CI configurations?▼

Preventing hardcoded agent names in CI configurations is achieved by enforcing the Product Isolation Rule during charter creation and peer review, ensuring product logic and tests remain decoupled from specific agent identities.

How do I standardize charter creation and review workflows for agents?▼

Charter creation and review workflows are standardized by loading a single governance skill that requires a YAML frontmatter with name, description, domain, and source, along with a structured body for activation.

Do I need a specific format to define shared compliance rules for squad agents?▼

Defining shared compliance rules requires a YAML frontmatter containing name, description, domain, and source fields, paired with a structured body that gets loaded once and used by all activation workflows.

How does the Peer Quality Check work for squad agent compliance?▼

The Peer Quality Check operates as a centralized hard rule applied during peer review, verifying that squad agents adhere to shared testing practices and preventing hardcoded agent names in product logic.

Why does agent behavior drift across different squad workflows?▼

Agent behavior drifts when shared hard rules are decentralized, making centralized governance necessary to unify naming conventions, testing practices, and product isolation across all charters and CI workflows.