Auto Invoke Router
PassAudited by ClawScan on May 4, 2026.
Overview
This instruction-only skill is coherent and purpose-aligned, but it writes persistent routing configuration that can affect future skill selection.
Before installing, be comfortable with the skill reading installed skill frontmatter and updating AGENTS.md. Back up or inspect AGENTS.md, review ambiguous triggers, and consider writing router.yml first if you want a manual approval step.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may enumerate installed skill metadata on the local machine.
The skill uses local shell discovery to locate installed skill files. This is central to its purpose and scoped to SKILL.md files, but users should run it only in the intended environment.
find ~/.openclaw/skills "$OPENCLAW_SYSTEM_SKILLS" -name "SKILL.md" 2>/dev/null
Run it from the intended workspace and review the discovered skill list before relying on the generated routing.
Future conversations may invoke skills based on the generated routing, including any ambiguous or incorrect trigger mappings.
AGENTS.md is persistent agent context/configuration. Replacing its routing section can affect future skill selection, and manual edits in that section may be overwritten.
The output is written into `AGENTS.md` as a `## Skill Routing` section... If a `## Skill Routing` section already exists, replace it in full
Inspect the generated Skill Routing section, keep custom rules outside the regenerated block, and use the standalone router.yml option if you want to review before changing AGENTS.md.