agent-detector

Solid

CRITICAL: MUST run for EVERY message. Detects agent, complexity, AND model automatically. Without this, tasks route to wrong agents and use wrong models, degrading quality and wasting tokens.

AI & Automation 24 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
47
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

> **AI-consumed reference.** Optimized for Claude to read during execution. > Human-readable explanation: see [docs/architecture/HIERARCHICAL_PLANNING.md](../../../docs/architecture/HIERARCHICAL_PLANNING.md) > or [docs/getting-started/](../../../docs/getting-started/) depending on topic. # Agent Detector **Runs FIRST for every message.** ## Complexity ```toon complexity[4]{level,criteria,approach}: Quick,"Single file / simple fix / clear scope","Direct implementation" Standard,"2-5 files / feature / some unknowns","Scout then implement" Deep,"6+ files / architecture / vague scope","run-orchestrator" Project,"Multi-feature / multi-session / weight ≥ 3 on bridge heuristic AND no active plan","/aura-frog:plan bootstrap then per-task /run anchored" ``` **Project (v3.7.2+):** Emitted when `rules/workflow/run-plan-bridge.md` triggers sum to weight ≥ 3 AND `.claude/plans/active.json` is absent. `run-orchestrator` Step 0 owns the user prompt (`plan` / `deep` / `details`) and the scratch-file handoff. Otherwise Quick/Standard/Deep classification is unchanged. ## Model Selection **Prefer the session model — inherit it.** The model the user launched with is the signal of their intent and budget; use it for all substantive work (Standard / Deep / architecture / planning / build / review). Do NOT force-upgrade to a named model (e.g. Opus) for "complex" — if the user wanted more capability they'd run it, and naming a model means a newer/stronger one is ignored. The only de...

Details

Author
nguyenthienthanh
Repository
nguyenthienthanh/aura-frog
Created
8 months ago
Last Updated
today
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

mkagent-detector

Detects task agent and complexity tier at Phase 0 orient. Invoked first in every workflow. Provider adapters select any model/runtime policy. NOT for runtime agent routing inside a single skill (see orchestration-rules.md).

15 Updated today
ngocsangyem
AI & Automation Listed

agent-or-workflow

Decides the architecture for an AI feature before it is built, whether the work should be a deterministic workflow, a workflow with a model at the judgment points, a single model call, a single agent with tools, or multi-agent. Use when someone is scoping or designing a new AI use case, asking whether it needs an agent, reviewing a PRD, ticket, or spec for an agent, or pushing back on a design that reaches for an agent where a workflow would do. Also covers Salesforce Agentforce designs, deciding whether a use case should be a Flow, a prompt template, an Agentforce topic with actions, or multiple agents. Reads the design input, extracts the deciding signals with evidence, runs a deterministic verdict, and writes an architecture decision record that biases toward the simplest thing that works.

0 Updated 1 weeks ago
hamidettefagh
AI & Automation Listed

subagent-delegation

Use BEFORE starting any multi-part task (research or comparisons across several sources, reading or summarizing long documents and transcripts, bulk updates across many items, audits, or checking a draft or numbers before they go out). Also use when about to spawn any subagent or worker, or when a task needs 3+ searches or tool calls. Routes gathering, reading, and bulk work to cheaper worker models, and escalates hard reasoning or a final check to a stronger model only when that actually helps.

0 Updated 6 days ago
alectivism