How do I install the Heyeddi Orchestrator skill?

Run npx skillmds@latest add heyeddi-com/heyeddi-orchestrator-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Heyeddi Orchestrator safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Heyeddi Orchestrator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Heyeddi Orchestrator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Heyeddi Orchestrator?

HeyEddi-com (@heyeddi-com) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Heyeddi Orchestrator by heyeddi-com

Name: Heyeddi Orchestrator
Author: HeyEddi-com

Heyeddi Orchestrator

Discover HeyEddi skills, load the catalog, and suggest which @skills to invoke for the current task. Use at session start, ambiguous requests, multi-skill pipelines, or when the user asks what skills are available. Reads skill-routing.json from @heyeddi-intake when present.

HeyEddi-com Updated Sep 17, 2026

File contents

Skill Orchestrator

Routes work to the right HeyEddi skill — without loading every SKILL.md at once.

When to use

Session start on a HeyEddi project (.heyeddi/ present or greenfield app request)
User asks "what skills do we have?" or "which skill should handle this?"
Before a multi-step pipeline (intake → scaffold → design → handoff → QA)
After @heyeddi-intake — confirm skill-routing.json before downstream work

Limits (Cursor)

Cursor cannot inject all skill bodies automatically. This skill:

write_skills_index — scan once → .heyeddi/skills-index.json + skills-index.md
load_catalog — read the cached index (rescan with --refresh after skill installs)
suggest_skills — ranked matches from index entries (+ skill-routing.json when present)
You — read one chosen skill's SKILL.md, then invoke it

Pipeline

write_skills_index        → .heyeddi/skills-index.{json,md}  (session start / after installs)
read skills-index.md      → quick catalog without opening every SKILL.md
suggest_skills            → ranked @skills for this task
read one SKILL.md         → follow that skill's pipeline

If .heyeddi/docs/intake/skill-routing.json exists (from @heyeddi-intake), follow route order — suggestions surface it at score 100.

Instructions

Session start: write_skills_index --project-root <root> (or load_catalog --refresh — same effect)
Quick lookup: read .heyeddi/skills-index.md — no need to open every SKILL.md
suggest_skills --project-root <root> --user-prompt "<request>"
Or --prompt-file USER_PROMPT.md
Read one chosen skill's SKILL.md (path in index JSON), then invoke @skill-name
Re-run write_skills_index after npx skills add or hub skill updates
Greenfield with no .heyeddi/product.md → top suggestion often @heyeddi-intake

Tools

Script	Purpose
`write_skills_index.py`	Scan → `.heyeddi/skills-index.*`
`load_catalog.py`	Read index (or scan+write if missing)
`suggest_skills.py`	Rank skills from cached index

@heyeddi-intake — writes skill-routing.json
reference/skill-triggers.md — how per-skill reference/triggers.md works (fully agnostic scoring)

---name: heyeddi-orchestrator-3description: Discover HeyEddi skills, load the catalog, and suggest which @skills to invoke for the current task. Use at session start, ambiguous requests, multi-skill pipelines, or when the user asks what skills are available. Reads skill-routing.json from @heyeddi-intake when present.---# Skill OrchestratorRoutes work to the right HeyEddi skill — without loading every SKILL.md at once.## When to use- Session start on a HeyEddi project (`.heyeddi/` present or greenfield app request)- User asks "what skills do we have?" or "which skill should handle this?"- Before a multi-step pipeline (intake → scaffold → design → handoff → QA)- After `@heyeddi-intake` — confirm `skill-routing.json` before downstream work## Limits (Cursor)Cursor **cannot** inject all skill bodies automatically. This skill:1. **`write_skills_index`** — scan once → `.heyeddi/skills-index.json` + `skills-index.md`2. **`load_catalog`** — read the cached index (rescan with `--refresh` after skill installs)3. **`suggest_skills`** — ranked matches from index entries (+ `skill-routing.json` when present)4. **You** — read **one** chosen skill's `SKILL.md`, then invoke it## Pipeline```write_skills_index → .heyeddi/skills-index.{json,md} (session start / after installs)read skills-index.md → quick catalog without opening every SKILL.mdsuggest_skills → ranked @skills for this taskread one SKILL.md → follow that skill's pipeline```If `.heyeddi/docs/intake/skill-routing.json` exists (from `@heyeddi-intake`), **follow route order** — suggestions surface it at score 100.## Instructions1. **Session start:** `write_skills_index --project-root <root>` (or `load_catalog --refresh` — same effect)2. **Quick lookup:** read `.heyeddi/skills-index.md` — no need to open every SKILL.md3. `suggest_skills --project-root <root> --user-prompt "<request>"` Or `--prompt-file USER_PROMPT.md`4. Read **one** chosen skill's `SKILL.md` (path in index JSON), then invoke `@skill-name`5. Re-run `write_skills_index` after `npx skills add` or hub skill updates6. Greenfield with no `.heyeddi/product.md` → top suggestion often `@heyeddi-intake`## Tools| Script | Purpose ||--------|---------|| `write_skills_index.py` | Scan → `.heyeddi/skills-index.*` || `load_catalog.py` | Read index (or scan+write if missing) || `suggest_skills.py` | Rank skills from cached index |## Related- `@heyeddi-intake` — writes `skill-routing.json`- `reference/skill-triggers.md` — how per-skill `reference/triggers.md` works (fully agnostic scoring)

Frequently asked questions