chore(skills): name InternalToolConfig beside ToolConfig in the response-type guidance

Author: waleedlatif1

.agents/skills/add-integration/SKILL.md

@@ -92,7 +92,7 @@ export interface {Service}{Action}Response extends ToolResponse {
 }
 ```
 
-Declare one response interface per tool, imported by that tool's `ToolConfig<Params, Response>`. Never add an umbrella `{Service}Response` union: nothing imports it.
+Declare one response interface per tool, imported by that tool's `ToolConfig<Params, Response>` (or `InternalToolConfig` for in-process work). Never add an umbrella `{Service}Response` union: nothing imports it.
 
 **Tool file pattern:** an external provider API uses `ToolConfig` with `request` (absolute `https://` URL, headers, body, `transformResponse`); same-process Sim work uses `InternalToolConfig` with `operation`. Both full templates, param visibility rules, and output typing live in `.agents/skills/add-tools/SKILL.md` — read it before writing the first tool.
 

.agents/skills/add-tools/SKILL.md

@@ -423,7 +423,7 @@ export interface {Service}{Action}Response extends ToolResponse {
 }
 ```
 
-Each response interface is imported by its tool's `ToolConfig<Params, Response>`. Never add an umbrella `{Service}Response` union of them: nothing imports it.
+Each response interface is imported by its tool's config: `ToolConfig<Params, Response>` for an external API, `InternalToolConfig<Params, Response>` for in-process work. Never add an umbrella `{Service}Response` union of them: nothing imports it.
 
 ## Index.ts Barrel Export Pattern