Graph Orchestrator
Use when a request has many similar subtasks (auditing every file in a repo, researching a list of companies, migrating a set of endpoints, reviewing a batch of documents), when a plan is about to be written as "first X, then Y, then Z" across more than about four steps, or when work spans 10+ files or sources. Also use when a previous attempt at a large task ran out of context, lost detail partway through, or produced a summary that thinned out toward the end, or when a plan ends in an irreversible action (mass send, deploy, delete) that needs gating.
Install
npx skills add VineeTagarwaL-code/graph-engineering --skill graph-orchestratorgit clone --depth 1 https://github.com/VineeTagarwaL-code/graph-engineering.git /tmp/graph-engineering
mkdir -p ~/.claude/skills
cp -r /tmp/graph-engineering/. ~/.claude/skills/graph-orchestratorPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Graph Orchestrator Most multi-step plans are written as chains because that's how people narrate work, not because the steps actually depend on each other. A chain of ten steps where only three real dependencies exist wastes time, and worse, it burns context linearly, so quality degrades toward the end. This skill turns a request into a dependency graph first, then executes it in phases. The graph is a *planning* artifact, but it also decides who executes each node: work you do inline, and work you dispatch to parallel subagents when the environment provides them. What the graph buys you is knowing which work can fan out, which must wait, where results need to be consolidated before they overflow, and which single node needs a human's sign-off. ## The core move: the dependency audit This is the part that matters most. Everything else follows from it. For every pair of steps you were about to sequence, ask one question: > **Does step B literally read the output of step A?** If B only needs the *same inputs* A had, they are independent. If B needs A's *result*, there's a real edge. People systematically over-connect. "Analyze the auth module and then analyze the payments module" has no edge. The word "then" is narration. "Analyze the auth module and then write a report on it" has a real edge. Work through the list explicitly rather than eyeballing it:
Details
- Skill name
graph-orchestrator- Repository
- VineeTagarwaL-code/graph-engineering
- License
- MIT
- Repo updated
- 23 July 2026
FAQ
What does the Graph Orchestrator skill do?
Use when a request has many similar subtasks (auditing every file in a repo, researching a list of companies, migrating a set of endpoints, reviewing a batch of documents), when a plan is about to be written as "first X, then Y, then Z" across more than about four steps, or when work spans 10+ files or sources. Also use when a previous attempt at a large task ran out of context, lost detail partway through, or produced a summary that thinned out toward the end, or when a plan ends in an irreversible action (mass send, deploy, delete) that needs gating.
How do I install the Graph Orchestrator skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add VineeTagarwaL-code/graph-engineering --skill graph-orchestrator. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Graph Orchestrator popular?
It lives in VineeTagarwaL-code/graph-engineering, which has 8 GitHub stars and 2 forks.
Related skills
Instant Site
8haoyiyin/instant-site
Build, deploy, update, and SEO-optimize static foreign trade independent sites using HTML/CSS/JS, DESIGN.md templates, Cloudflare Pages (Wrangler), and scheduled agent operations. Use for from-zero site generation, static deployment, scheduled content operations, SEO audits, and multi-site independent site operations.
Xcloud
8xCloudDev/xcloud-agent-skills
Deploy Git repositories, diagnose errors and slow sites, then manage servers, sites, SSL, backups, billing and teams. Nine capability skills; MCP-first with a read-only REST fallback, deployment previews and explicit approval for destructive or paid actions.
Docker
8wrsmith108/docker-claude-skill
Container-based development for isolated, reproducible environments. Use when running npm commands, installing packages, executing code, or managing project dependencies. Trigger phrases include "npm install", "run the build", "start the server", "install package", or any code execution request.
Gcd
9rochacbruno/gcd-claude-skill
Google Cloud Dedicated (GCD) and Cloud de Confiance (S3NS) sovereign cloud expert. Use when working with sovereign Google Cloud regions, or when the user mentions GCD, Google Cloud Dedicated, Cloud de Confiance, S3NS, sovereign cloud, universe domain, apis-berlin-build0.goog, s3nsapis.fr, u-germany-northeast1, u-france-east1, Trusted Partner Cloud, TPC, or data sovereignty requirements for Google Cloud workloads. Provides guidance on region-specific services, authentication, Terraform, networking, and key differences from public Google Cloud. Also use when asked to review a PR, code review, or
Legba
8legba-app/skills
Trigger on the keyword "legba" — e.g. "use legba to access/fetch this", "legba this URL", "route this through legba". Also use when a public target blocks datacenter IPs, is geo-restricted, sits behind a Cloudflare/anti-bot JS challenge, or needs a captcha, login code or 2FA that only a person can do — provisions a residential exit, or a browser on Legba's own infrastructure that the user can take over mid-task and hand back. Keywords - legba, residential proxy, datacenter block, geo-restricted, Cloudflare, Turnstile, DataDome, PerimeterX, captcha, 2FA, exit IP, recon, OSINT, hosted browser, h
Drawio AWS Reference
8patvillarroel/drawio-aws-reference
Produce AWS architecture diagrams as editable .drawio files using the AWS 2026 shape set (mxgraph.aws4 stencils), with verified stencil names and a validator. Use this whenever an AWS architecture diagram is requested, revised, or reviewed, including when the user only says "draw the architecture", "diagram this", "make me a schema", "hazme un diagrama", or hands over a design document that needs a visual. Also use it when converting a Mermaid sketch into a real draw.io file. Do not use it for non-AWS diagrams.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.