eSIM

What This Skill Does

The eSIM skill for OpenClaw provides expert-level guidance, troubleshooting, and architectural support for the implementation of eSIM (Embedded SIM) technology. It bridges the gap between consumer-facing activations and complex backend carrier integrations. This skill assists developers and engineers in distinguishing between SGP.22 (Consumer RSP) and SGP.02 (M2M RSP) architectures, troubleshooting activation code parsing, and navigating the rigorous GSMA compliance landscape. Whether you are debugging an ES9+ download failure or architecture planning for an SM-DP+ integration, this skill serves as a technical consultant to ensure your provisioning flows adhere to industry standards and avoid common platform-specific pitfalls.

Installation

To integrate this skill into your environment, run the following command in your terminal:

clawhub install openclaw/skills/skills/ivangdavila/esim

Use Cases

• Development Support: Architecting RSP (Remote SIM Provisioning) flows for mobile apps or IoT devices while ensuring compliance with GSMA TS.48 specifications.
• Troubleshooting: Diagnosing common activation failures such as "Profile already exists" errors, mid-process download interruptions, or service-level connectivity issues after profile installation.
• Technical Consultation: Understanding the complex ecosystem of carrier entitlement servers, SM-DP+ infrastructure, and the contractual requirements for MNO/MVNO integrations.
• Operational Guidance: Assisting customer support teams in explaining eSIM constraints, such as the permanence of profile deletion and the requirement for fresh activation codes for device-to-device transfers.

Example Prompts

1. "My iOS app is failing to download an eSIM profile for some users with an ES9+ error, how do I debug the HTTPS handshake and verify the entitlement status?"
2. "Explain the key differences between SGP.22 and SGP.02 architectures for a developer building a new IoT device integration."
3. "Our users are receiving an 'Invalid Activation Code' error for an eSIM QR code that was generated yesterday. What are the common causes for this expiry issue?"

Tips & Limitations

• Platform Restrictions: Always verify if you have the necessary carrier entitlements before attempting to access Apple or Android eSIM APIs. Public APIs for arbitrary provisioning do not exist.
• Code Lifecycle: Activation codes are usually single-use. If a download fails, do not assume the code is still valid; request a new MatchingId from the SM-DP+.
• Security: Ensure all production environments use GSMA SAS-certified SM-DP+ systems. Never attempt to use production EIDs within test environments.
• Hardware Verification: Not all region-specific models of phones support eSIM. Always verify hardware compatibility before directing a user to perform an activation.