us15-shared-skill

Synchronize the us15-shared-skill across original and newly detected agents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fyodoriv/agentbrew --skill us15-shared-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: us15-shared-skill
Source: https://github.com/fyodoriv/agentbrew/tree/main/real-e2e/fixtures/us15-add-new-agent/shared-skills/us15-shared-skill
Command: npx skills add https://github.com/fyodoriv/agentbrew --skill us15-shared-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixture that validates skill syncing across original and newly added agents.

Core Features & Use Cases

  • Validates cross-agent skill propagation when a new agent is detected.
  • Ensures drift detection does not regress existing skills across agents.
  • Use Case: In a multi-agent setup, verify that the us15-shared-skill is present on both the original and the newly added agent.

Quick Start

Initialize the test environment and trigger a re-detection to verify the shared skill sync across agents.

Frequently Asked Questions about us15-shared-skill

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

FAQPage Schema
How do I sync a shared skill across original and newly added agents?

To sync a shared skill across agents, you need a fixture that triggers safe re-detection and non-destructive propagation. This ensures the skill exists on both original and newly detected agents without causing drift in multi-agent environments.

What is skill drift in a multi-agent environment?

Skill drift occurs when shared skills become inconsistent across original and newly added agents. Validating cross-agent skill propagation prevents this regression by ensuring deterministic synchronization of the skill during ongoing maintenance.

Can I validate cross-agent skill propagation without disrupting existing agents?

Yes, you can validate cross-agent skill propagation non-destructively. The synchronization fixture implements safe re-detection to ensure drift detection does not regress or disrupt existing skills across your original agents.

When do I need to run e2e validation for agent skill synchronization?

You need e2e validation for agent skill synchronization during onboarding and ongoing maintenance whenever a new agent is detected. This verifies that the shared skill propagates correctly to prevent configuration drift.

What is the best way to verify a skill exists on both original and newly detected agents?

The best way to verify a skill exists on both original and newly detected agents is to initialize a test environment and trigger a re-detection. This fixture validates cross-agent skill propagation deterministically.