agentsclimarketplace

Automation tool router

Skill frankxai/starlight-automation-agent-skills/skills/automation-tool-router

Portable automation agent skills for the Starlight substrate — scheduling, pipelines, and fleet ops.

Install
npx -y skills add frankxai/starlight-automation-agent-skills --skill automation-tool-router

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Choose the best automation layer across native connectors, Codex automations, MCP tools, Make.com scenarios, n8n workflows, and Starlight swarm queues. Use when a user asks which tool to use, how to automate a workflow, whether Make or n8n is better, how MCP should fit, how future agents should remember tool choices, or how to route recurring work safely.

SKILL.md

2.2 KB, 426 tokens by cl100k_base, as published. Nobody here has run it

Automation Tool Router

Use this first when the work is about automation architecture or tool choice. Return a concrete owner, not a vague stack.

Routing Order

  1. Use the native connector when one exists for the target system.
  2. Use Codex automation for recurring reasoning, review, repo, inbox, or briefing work.
  3. Use MCP when an agent needs a typed, bounded tool or resource.
  4. Use Make.com for fast SaaS glue, forms, CRM updates, and simple approval chains.
  5. Use n8n for branchy technical workflows, private data flows, reusable templates, and self-hostable automation.
  6. Use a Starlight queue for cross-repo, multi-agent, eval-heavy, or handoff-heavy work.

Safety Gates

  • Require human approval before send, post, spend, delete, publish, invite, production deploy, or account-permission changes.
  • Dry-run first for migrations, workflow activation, bulk edits, and storage cleanup.
  • Fail closed on auth, schema, transport, webhook, or confidence errors.
  • Never print or commit secrets, live webhook URLs, customer data, inbox content, or private memory.
  • Public exports must use mock payloads and pass a sensitive-marker scan.

Decision Output

Return:

  • tool owner
  • why this tool wins
  • fallback tool
  • trigger/input
  • output contract
  • approval gate
  • validation step
  • where durable state belongs

Reference Routing

  • For Make.com scenario design, use make-com-operations.
  • For n8n workflow design or exported workflow review, use n8n-operations.
  • For MCP scopes, tool schemas, and server boundaries, use mcp-governance.
  • For recurring scheduled work in Codex, use codex-automation-operator.
  • For multi-agent queues and handoffs, use starlight-queen-queue.

Verification

For public artifacts, run scripts/scan_public_safety.py from the source repo when available. For installable bundles, run scripts/validate_skill_bundle.py.

Gives 0 of the 12 instructions most automation workflows skills give in 426 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-06

  • write conventional commit messagesin 36 of 745, across 35 files
  • delete branches after mergein 30 of 745, across 21 files
  • make atomic commitsin 25 of 745, across 15 files
  • write minimal code to pass testsin 22 of 745, across 10 files
  • run tests before committingin 21 of 745, across 13 files
  • re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
  • use try-catch for error handlingin 20 of 745, across 6 files
  • write tests before implementationin 20 of 745, across 8 files
  • configure branch protection rulesin 19 of 745, across 5 files
  • explain the why in commit messagesin 19 of 745, across 9 files
  • refactor code while tests remain greenin 19 of 745, across 6 files
  • Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

  • use native connectors when they exist
  • use Codex for recurring reasoning or review
  • use MCP for typed bounded agent tools
  • use Make.com for fast SaaS glue
  • use n8n for branchy technical workflows
  • use Starlight for cross-repo multi-agent work

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.