> ## Documentation Index > Fetch the complete documentation index at: https://docs.getthread.com/llms.txt > Use this file to discover all available pages before exploring further. # Skill Director > Read one deciding field on a ticket, such as a deployment method or alert source, and load exactly one matching saved sub-skill to do the work, so one Flow can drive several specialist skills. Runs asAgent Build it with Agent Builder: add the action to a Flow, choose Prompt the Agent, and paste this in. It runs unattended on a matching ticket event. You can also run it yourself in Super Magic while you prove it out.Works withThreadRole[Service & Ops Manager](https://docs.getthread.com/start-here/roles/service-ops-manager), [Technician](https://docs.getthread.com/start-here/roles/technician)OutcomeTime & Cost Savings (Capacity), Staff EnablementCategory[Automation & Flows](https://docs.getthread.com/skill-library/automation-and-flows/overview) · [View source ↗](https://github.com/Thread-Magic/super-magic-skills/blob/main/skills/automation-and-flows/skill-director/SKILL.md) **When to use:** You have built two or more specialist skills that do the same job differently depending on one fact about the ticket (a standard, Autopilot or Mac deployment; a backup, RMM or EDR alert; a client on contract or off). You want one Flow and one entry point that reads the ticket, picks the right specialist, and hands off, instead of a Flow per variant with overlapping filters. **Run it:** on one ticket · or as a Flow (for example when a ticket moves to a review or pending-close status). Run the Flow with Agent Builder's Run a Skill mode pointed at this director, so the saved sub-skills it names can be loaded. Replace the routing table with your own labels and saved skill names. Unlike the intake orchestrator, which runs every skill in order, a director runs exactly one. ## Prompt ``` You are a director. You do not do the work yourself: you read one deciding fact on this ticket, load the one saved skill that handles that case, and follow it. 1. FIND THE INPUT. Read the whole ticket, including every note and time entry. If the work depends on a form or checklist the tech fills in (for example a note that starts with a fixed heading such as "This is a mandatory compliance form"), find it. If the input the sub-skills need is missing, stop and tell the tech what to add. Never invent answers. 2. READ THE DECIDING FIELD. Look for the labelled line that decides the route, in the form, any note or time entry, or what the tech told you. A checkbox or drop-down only counts as chosen when it shows a selected value, not "Not Completed" or blank. "N/A" is a valid answer for lines that do not apply. 3. ROUTE. Load exactly one saved skill by its exact name and follow it fully: - "