oneworks-model-serviceslisted

Use this skill when a user wants to add, update, or troubleshoot OneWorks `modelServices`. ## Writeback Rules - Put account-level API keys and secrets in global config by default. - Use project or user config only when the user explicitly asks for an override. - Do not copy values from merged config back into a source file unless you know the target source. - Never show API keys, secrets, tokens, or passwords in the final answer. - If the selected provider is known, prefer built-in defaults for `provider`, `homepageUrl`, `apiBaseUrl`, models, icons, and management capabilities. Only write override fields when the user asks for an override. ## Config Shape Use `modelServices.<serviceKey>` with these common fields: - `provider`: built-in provider id. - `title`: display name. - `description`: short display description. - `apiKey`: service API key or secret. - `apiBaseUrl`: only needed for custom services or explicit overrides. - `models`: only needed for custom services or explicit overrides. - `billing`: optional metadata for billing kind, key kind, quota unit, quota windows, and allowed use. - `codingPlan`: optional metadata for plan links, protocol base URLs, regions, default models, and restrictions. - `homepageUrl`: only needed to override the provider portal. - `management.enabled`: enables model/balance/status/secret helper actions when available. - `management.apiKey`: optional separate management API key; otherwise reuse `apiKey` when supported. ## Coding Plan and