twilio-getting-started

Grounds Twilio .NET SDK integration in a generated map of operations, models, enums, and error types.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/apimatic/plugin-marketplace --skill twilio-getting-started-apimatic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: twilio-getting-started
Source: https://github.com/apimatic/plugin-marketplace/tree/main/plugins/twilio-sdk/skills/twilio-getting-started
Command: npx skills add https://github.com/apimatic/plugin-marketplace --skill twilio-getting-started-apimatic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI coding agents hallucinate SDK signatures, model shapes, and error types when integrating the Twilio .NET SDK, producing code that fails to compile or misuses the API. This Skill grounds every contract question in a generated SDK map so the agent answers from authoritative, version-pinned facts instead of memory. ## Core Features & Use Cases - SDK Identity & Setup: Provides the NuGet package name (AsadAli.TwilioSdk), root namespace, client/options classes, auth pattern, and environment configuration for the Twilio .NET SDK. - Bundled SDK Map: Ships a generated index (sdk-map.md plus map/ pages) covering 887 operations across 318 controllers, with exact C# signatures, must-pass-explicitly parameters, return types, error cases, enum values, and union accessors. - Guided Integration Workflow: Directs the agent to load companion skills (client initialization, authentication, calling endpoints, models, error handling, resilience, testing) at each integration step while confirming names against the map. - Use Case: A developer asks their agent to send an SMS via Twilio in C#. The agent looks up the exact operation signature and error type in the map, builds a contract sheet, and writes compiling integration code without guessing. ## Quick Start Ask your agent to integrate the Twilio .NET SDK into your C# project and have it follow this skill to look up operation signatures and error types from the bundled SDK map.

Frequently Asked Questions about twilio-getting-started

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate the Twilio .NET SDK in a C# project?▼

Install the AsadAli.TwilioSdk NuGet package version-less with dotnet add package, then construct a TwilioSdkClient with an HttpClient and TwilioSdkClientOptions. Set the AccountSidAuthToken credentials property and Environment on the options before constructing the client.

How do I find the exact C# signature for a Twilio API operation?▼

Open sdk-map.md and follow the link table to the controller's page under map/operations/. Each row lists the verbatim C# signature, must-pass-explicitly parameters, return type, and error case, so you never need to grep the SDK source.

Does the Twilio .NET SDK use typed errors or raw error responses?▼

Both. Of 887 operations, 29 are Case A throwing SdkException with a typed {Operation}Error exposing TryGet accessors, while 858 are Case B throwing SdkException<RawError> with StatusCode and ReadAsString/ReadAsJson methods. Each operation's map row states its case.

Why do I get CS0103 or CS0246 errors when using Twilio SDK models?▼

The SDK splits public types across separate child namespaces, and C# does not import child namespaces transitively. Add a separate using directive for each namespace; the SDK map lists each type's namespace in its row.

When should I clone the Twilio SDK source repository?▼

Clone only when the SDK map cannot answer a question, such as a map-sourced name failing to compile or needing a full method body. Clone shallowly from branch main into the system temp directory and open only the single file the map names.