agent-conduct

Enforce product isolation and peer quality rules across squad agents.

2|3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/sytone/botnexus --skill agent-conduct-sytone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-conduct
Source: https://github.com/sytone/botnexus/tree/main/.copilot/skills/agent-conduct
Command: npx skills add https://github.com/sytone/botnexus --skill agent-conduct-sytone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Every squad agent must follow these two hard rules. They were previously duplicated in every charter. Now they live here as a shared skill, loaded once.

Core Features & Use Cases

  • Enforces the Product Isolation Rule to prevent hardcoded references to specific agent names in tests, CI configs, or product logic.
  • Enforces the Peer Quality Check to ensure changes are validated against the test suite and CI stability.
  • Anti-Patterns: Don't hardcode agent names; always run tests before finishing work; don't ignore pre-existing CI failures.

Quick Start

Review and apply the two hard rules across all squad agents to ensure consistent governance.

Frequently Asked Questions about agent-conduct

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

FAQPage Schema
How do I enforce coding standards across multiple AI agents in a squad?

To enforce coding standards across multiple agents, you apply a shared governance rule set that prevents hardcoded agent names in tests and CI workflows, ensuring configurations remain generic and parameterizable across all squads.

Why should tests and CI workflows not reference real agent names?

Tests and CI workflows should not reference real agent names to maintain product isolation, ensuring configurations remain generic, parameterizable, and free from squad-specific identifiers that break consistency across different environments.

How do I set up shared governance rules for team coordination in CI?

Set up shared governance rules for team coordination by loading a centralized skill once, which applies hard rules like the Product Isolation Rule and Peer Quality Check across all squad agents to validate changes against the test suite.

Can I use a single shared rule set instead of duplicating governance rules in every agent charter?

Yes, you can use a single shared rule set loaded once to replace duplicated governance rules in every agent charter, applying consistent anti-pattern guidance and quality checks across your entire multi-agent environment.

What happens if I ignore pre-existing CI failures during agent quality checks?

Ignoring pre-existing CI failures during agent quality checks violates the Peer Quality Check rule, which requires that all changes are validated against the test suite and CI stability before finishing work to ensure reliable outcomes.

How does the Peer Quality Check rule work for multi-agent environments?

The Peer Quality Check works by enforcing that all squad agents validate their changes against the test suite and CI stability before finishing work, preventing ignored pre-existing failures and ensuring reliable CI outcomes across the environment.