update-agent-guidance

Categorize and route agent guidance updates across org-wide and repository-specific files.

1|Updated Jul 7, 2022
One-click install
npx skills add https://github.com/chiubaka/circleci-orb --skill update-agent-guidance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-agent-guidance
Source: https://github.com/chiubaka/circleci-orb/tree/main/org/agents/skills/update-agent-guidance
Command: npx skills add https://github.com/chiubaka/circleci-orb --skill update-agent-guidance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Streamlines the process of updating agent guidance documents, ensuring that org-wide and repo-specific changes are properly categorized and applied.

Core Features & Use Cases

  • Org-wide vs. Repo-level Changes: Routes updates to org guidance files or local overrides, maintaining clarity in org-level and repo-specific guidance.
  • Bootstrap and Verification: Offers automated re-syncing and verification commands for managed outputs after org-level edits.
  • Workflow Coordinator: Manages coordination for streamlining and rule classification of org/agents/AGENTS.org.md guidance.

Quick Start

Update org-wide guidance for agent behavior and then re-sync with the org/agents/scripts/bootstrap-agents-md.sh script.

Frequently Asked Questions about update-agent-guidance

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

FAQPage Schema
How do I automate agent guidance updates for org-wide and repo-specific changes?

Automating agent guidance updates involves routing organizational policy changes to org-wide guidance files and local implementation changes to repository-specific overrides. This categorization ensures updates are properly applied and maintains clarity between org-level and repo-specific guidance.

What is the best way to sync org-level edits with local agent guidance files?

Syncing org-level edits with local agent guidance files is done through automated re-syncing and verification commands. After updating org-wide guidance, running the bootstrap script re-syncs managed outputs to ensure local repository files reflect the latest organizational policy changes.

How does routing work for org-wide versus repository-specific agent guidance documentation?

Routing for agent guidance documentation works by categorizing updates and directing them to either org guidance files or local repository overrides. This differentiation ensures organizational policy updates and local implementation changes are applied to the correct scope without overriding each other.

Do I need a command-line interface to manage agent guidance updates?

A command-line interface is required to manage agent guidance updates. The automated categorization, routing, and bootstrap verification processes are executed via command-line scripts, which also require knowledge of your local directory structure to correctly apply repo-specific changes.

When do I need to run verification commands for agent guidance outputs?

Verification commands for agent guidance outputs are needed after making org-level edits to ensure managed outputs are properly synced. Running the bootstrap and verification process confirms that repository-specific overrides remain consistent with the updated organizational guidance policies.