orchestrator

Orchestrate codebase assimilation through scan, extract, generate, update, and cleanup phases.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/datorresb/vibecoding-starter --skill orchestrator-datorresb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/datorresb/vibecoding-starter/tree/main/.claude/skills/assimilation/orchestrator
Command: npx skills add https://github.com/datorresb/vibecoding-starter --skill orchestrator-datorresb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates all phases of the assimilation pipeline to scan a repository, extract patterns, generate SKILL.md entries, and update the agents documentation, eliminating the need for manual, error-prone orchestration.

Core Features & Use Cases

  • Automated orchestration: Manage Phase 1: Scan, Phase 2: Extract, Phase 3: Generate, Phase 4: Update, and Phase 5: Cleanup with robust error handling and a final summary.
  • Automates skill extraction: Streamlines generating SKILL.md entries from analyzed patterns and updates AGENTS.md accordingly.
  • Use Case: Run assimilation on a complete repository to produce a ready-to-use skill catalog for CLAUDE/agent pipelines.

Quick Start

Use the orchestrator to assimilate a repository by executing the orchestration workflow on the target codebase. The process will scan for entry points, extract patterns, generate SKILL.md files, and update AGENTS.md. After completion, review the generated SKILL.md files under .github/skills/ and .claude/skills/ and the summary report.

Frequently Asked Questions about orchestrator

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

FAQPage Schema
How do I automate codebase assimilation to generate SKILL.md entries and update AGENTS.md?

Codebase assimilation is automated by coordinating scan, extract, generate, update, and cleanup phases in strict order to produce SKILL.md files and adapt AGENTS.md. The orchestrator manages the full pipeline end-to-end and outputs a final summary with artifacts for review.

What is the pipeline for extracting patterns from a repository to build a skill catalog?

The pipeline for extracting patterns runs five phases: scanning the repository for entry points, extracting patterns, generating SKILL.md files, updating AGENTS.md, and cleaning up. This enforces strict phase order with robust error handling to build a ready-to-use skill catalog.

Can I run assimilation on a complete repository without manual orchestration?

Yes, you can run assimilation on a complete repository without manual orchestration. The process eliminates error-prone manual steps by automating the workflow from scanning entry points to generating SKILL.md files and adapting AGENTS.md automatically.

Where are the generated SKILL.md files stored after the assimilation workflow completes?

Generated SKILL.md files are stored under the .github/skills/ and .claude/skills/ directories after assimilation completes. The orchestrator outputs these artifacts alongside a final summary report for you to review the extracted patterns.

How does the orchestrator handle errors during the scan, extract, and generate phases?

The orchestrator handles errors gracefully during scan, extract, generate, update, and cleanup phases to prevent pipeline failures. It enforces strict phase order and outputs a final summary report detailing the assimilation results and any encountered issues.

Do I need any dependencies or external components to coordinate the assimilation workflow?

No dependencies or external components are required to coordinate the assimilation workflow. The orchestrator operates independently to manage the scan, extract, generate, update, and cleanup phases for your repository without needing additional packages.