skrills

🥈Silver

Skrills automates skill coordination between Codex, Copilot, and Claude Code. It validates, analyzes, and syncs skills, subagents, commands, and configurations across multiple CLIs. Operations teams use it to maintain consistency and streamline workflows.

5980Updated 1mo ago

Intermediate30min to implementautomation

Saves ~240 min per use

Quick InstallView Source

git clone https://github.com/athola/skrills.git

Works with:

Claude

Overview

About This Skill

How to Use

1. **Prepare Your Environment**: Ensure Codex, Copilot, and Claude Code are installed and accessible. Create a `.skrills.json` file in your project root with your skill configurations. 2. **Run Validation**: Execute `skrills validate --skills [SKILL_NAME]` to check for syntax errors or missing dependencies. 3. **Analyze Dependencies**: Use `skrills analyze --skills [SKILL_NAME] --output graph` to generate a dependency graph and identify potential conflicts. 4. **Sync Configurations**: Run `skrills sync --skills [SKILL_NAME] --targets codex,copilot,claude` to push consistent configurations across all tools. 5. **Review and Deploy**: Check the generated report and deploy the synced configurations to your team’s workflows. Tip: Use `skrills monitor --interval 5m` to track real-time sync status.

Setup & Installation

Quick Install

No install command available. Check the GitHub repository for manual installation instructions.

Alternative Install (Git Clone)

git clone https://github.com/athola/skrills

Requirements

Claude Code or compatible AI agent
Works with: Claude

Quick Start Guide

Install the Skill

Copy the install command above and run it in your terminal.

Open Your AI Agent

Launch Claude Code, Cursor, or your preferred AI coding agent.

Try It Out

Use the prompt template or examples below to test the skill.

Customize

Adapt the skill to your specific use case and workflow.

Usage Examples

Prompt Template

Act as a Skrills automation coordinator. For the following [SKILL_NAME], validate its configuration, analyze its dependencies, and sync it across Codex, Copilot, and Claude Code. Ensure consistency in [CONFIGURATION_PARAMETERS] and resolve any conflicts. Output a report with: 1) Validation status, 2) Dependency graph, 3) Sync actions taken, and 4) Next steps for the operations team.

Example Output

### Skrills Automation Report: `code-review-assistant`

**Validation Status:** ✅ All configurations validated successfully across Codex, Copilot, and Claude Code. No syntax errors or deprecated commands detected.

**Dependency Graph:**
- `code-review-assistant` (v2.1.3) depends on:
  - `eslint` (v8.56.0) for linting
  - `prettier` (v3.2.5) for formatting
  - `jest` (v29.7.0) for testing
  - `codex-cli` (v1.4.2) for CLI integration

**Sync Actions Taken:**
1. Updated `prettier` config in Copilot to match Codex and Claude Code.
2. Resolved a conflict in `jest` configuration where Copilot had an outdated version; synced to v29.7.0.
3. Added missing `codex-cli` dependency to Copilot’s environment.
4. Generated a unified `.skrills.json` file for all three tools with consistent settings.

**Next Steps for Operations Team:**
- Deploy the updated `code-review-assistant` to production after testing in staging.
- Monitor the `eslint` and `prettier` logs for 48 hours to ensure no runtime conflicts.
- Schedule a team sync to review any new skills added to the workflow.

**Conflicts Resolved:** 1 (Jest version mismatch).
**Skills Synced:** 4 (code-review-assistant, eslint, prettier, jest).
**Time Saved:** ~45 minutes (manual sync would have taken ~1.5 hours).