Safety-first tooling for managing changes in the orchestrator subsystem.

Install

mkdir -p .claude/skills/orchestrator-fuze210699 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17181" && unzip -o skill.zip -d .claude/skills/orchestrator-fuze210699 && rm skill.zip

Installs to .claude/skills/orchestrator-fuze210699

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

orchestrator — an agent skill by fuze210699.
44 chars · catalog descriptionno explicit “when” trigger
Beginner

Key capabilities

  • Check blast radius of a symbol
  • See all callers and callees of a symbol
  • Verify scope of changes before committing
  • Find all references to a symbol
  • Check edit safety of a symbol
  • Text search across files

How it works

The skill uses `mcp_milens` tools to analyze code dependencies and changes, providing information about symbol impact and edit safety.

Inputs & outputs

You give it
symbol name and repository root
You get back
blast radius report, list of callers/callees, or change scope verification

When to use orchestrator

  • Check blast radius before edit
  • Find symbol references
  • Verify change safety

About this skill

<!-- Generated by milens — safe to delete/regenerate -->

Orchestrator

Working with this area

When working with code in orchestrator/, follow these mandatory safety rules:

Before editing any symbol in this area:

  1. Call mcp_milens_impact({target: "<symbol>", repo: "<workspaceRoot>"}) — check blast radius
  2. If depth-1 dependents > 5 → STOP and warn before proceeding
  3. Call mcp_milens_context({name: "<symbol>", repo: "<workspaceRoot>"}) — see all callers/callees

Before committing changes in this area:

  1. Call mcp_milens_detect_changes({repo: "<workspaceRoot>"}) — verify scope
  2. If unexpected files changed → STOP and report

Key tools for this area:

TaskTool
Find all referencesmcp_milens_context
Check edit safetymcp_milens_edit_check
Text search across filesmcp_milens_grep
See file symbolsmcp_milens_get_file_symbols

Edit-safety enforcement

A PreToolUse hook (warn mode by default) reminds you if no milens safety check (impact/context/overview/guard_edit_check/edit_check/smart_context) was called before an Edit/Write/MultiEdit. Opt-in strict deny mode is available via milens hooks guard-set-mode --mode strict. Both modes consume the check after one edit. See .milens/hook-state/config.json. Known caveat: the underlying PreToolUse deny mechanism has at least one reliability issue (https://github.com/anthropics/claude-code/issues/4362).

Overview

Contains 23 symbols (7 exported) across 2 files.

Key Symbols

  • Orchestrator [class] (src/orchestrator/orchestrator.ts:46) — 6 refs
  • OrchestratorReport [interface] (src/orchestrator/reporter.ts:4) — 5 refs
  • formatReport [function] (src/orchestrator/reporter.ts:17) — 4 refs
  • OrchestratorConfig [interface] (src/orchestrator/orchestrator.ts:20) — 2 refs
  • ImpactSnapshot [interface] (src/orchestrator/orchestrator.ts:28) — 2 refs
  • ReportOptions [interface] (src/orchestrator/reporter.ts:13) — 2 refs
  • ImpactDiff [interface] (src/orchestrator/orchestrator.ts:35) — 1 refs

Entry Points

  • Orchestrator [class] — 6 incoming references
  • OrchestratorReport [interface] — 5 incoming references
  • formatReport [function] — 4 incoming references
  • snapshot [method] — 3 incoming references
  • run [method] — 3 incoming references

Dependencies

  • store: Database, findSymbolByName, findUpstream, getTestCoverageGaps, findDeadCode
  • analyzer: reviewPr, ReviewResult, SymbolRisk
  • root: CodeSymbol

Used By

  • root: Orchestrator, subscribe, runAndFormat
  • server: Orchestrator, loadSnapshots, snapshot, persistSnapshots, compare, runAndFormat
  • test: Orchestrator, formatReport, OrchestratorReport, subscribe, run, snapshot, compare, cancel (+3 more)

Files

  • src/orchestrator/orchestrator.ts
  • src/orchestrator/reporter.ts

When not to use it

  • When working outside the orchestrator/ directory
  • When not editing sensitive code

Limitations

  • Strictly applies to code within the orchestrator/ directory
  • PreToolUse hook has at least one reliability issue
  • Requires specific `mcp_milens` tools for analysis

How it compares

This skill enforces specific pre-check requirements and uses dedicated tools for impact analysis, unlike manual code changes that might overlook dependencies.

Compared to similar skills

orchestrator side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
orchestrator (this skill)01moNo flagsBeginner
deepwiki-rs259moReviewIntermediate
technology-stack33moNo flagsIntermediate
vercel-reference-architecture31moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

deepwiki-rs

sopaco

AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.

25170

technology-stack

ag-grid

Technology choices and architectural constraints for AG Grid. Use when choosing technologies, adding dependencies, or understanding zero-dependency requirements.

321

vercel-reference-architecture

jeremylongshore

Implement Vercel reference architecture with best-practice project layout. Use when designing new Vercel integrations, reviewing project structure, or establishing architecture standards for Vercel applications. Trigger with phrases like "vercel architecture", "vercel best practices", "vercel project structure", "how to organize vercel", "vercel layout".

31

obsidian-reference-architecture

jeremylongshore

Implement Obsidian reference architecture with best-practice project layout. Use when designing new plugins, reviewing project structure, or establishing architecture standards for Obsidian development. Trigger with phrases like "obsidian architecture", "obsidian project structure", "obsidian best practices", "organize obsidian plugin".

11

project-principles

vm0-ai

Core architectural and code quality principles that guide all development decisions in the vm0 project

11

tldr-code

parcadei

Token-efficient code analysis via 5-layer stack (AST, Call Graph, CFG, DFG, PDG). 95% token savings.

10

Search skills

Search the agent skills registry