executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
rollout-and-toolsUse when modifying verl rollout engines, multi-turn agent loops, function tools, tool schemas, rollout traces, or generation-server flows.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task touches verl rollout behavior rather than trainer optimizer policy: rollout backend config, async generation servers, multi-turn agent loops, tool calling, function-tool schema authoring, tokenization sanity checks, trace output, or rollout visualization.
@function_tool, BaseTool, schema loading, and tool dispatch, read Tooling API.actor_rollout_ref.rollout.multi_turn.function_tool_path, run validate_function_tool.py.actor_rollout_ref.rollout.mode=async; sync rollout mode is removed.actor_rollout_ref.rollout.multi_turn.enable=True plus actor_rollout_ref.rollout.agent.default_agent_loop=tool_agent for built-in tool-calling loops.fn(**parameters) calls; use native BaseTool tools for lifecycle, per-trajectory state, sandbox resources, or tools_kwargs.tokenization_sanity_check_mode=strict until the model chat template has been validated; use ignore_strippable only for whitespace-only template drift.ToolAgentLoop._call_tool error-handling tests, Qwen3 parser safety tests, and vLLM CLI argument parsing tests.ToolResponse instead of crashing the loop.