portal-skill-router

To route an Agent Town co-op request, you must first read the Rules skill file to understand the selection behavior, then choose exactly one specialized child skill entry point that matches the request.

Skill routing for co-op baseline looping tasks is the process of selecting exactly one specialized child skill path to execute looping actions, preventing wasted effort by ensuring the most specific skill handles the job.

To generate ceremony commit and reveal payloads, you route the co-op request through this skill selection mechanism to a specialized child skill that explicitly handles commit/reveal payload generation.

You should use a rules-based fallback in a Portal workflow when an incoming co-op request does not clearly fit a specialized child skill action, ensuring the system defaults to general rule-based behavior.

Yes, you must read the Rules skill file first to follow the expected selection behavior and guarantee you choose exactly one of the listed child skill entry points correctly.

Your Agent Town co-op task takes the wrong action because you did not route the request to the most specific child skill, which requires reading the Rules skill file upfront to guide the selection.