Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
eSIM
Implement and troubleshoot eSIM across consumer activation, carrier integration, and RSP development.
skill openclawclawhub Free
Implement and troubleshoot eSIM across consumer activation, carrier integration, and RSP development.
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Critical Distinction
Consumer RSP (SGP.22) and M2M RSP (SGP.02) are completely different architectures β not interchangeable, verify which applies before starting
Platform API Restrictions
Apple eSIM APIs require carrier entitlements β third-party apps cannot access without carrier partnership agreement Android carrier privilege APIs require signing certificate match β must be signed with carrier's certificate No public API exists for arbitrary eSIM provisioning β apps suggesting otherwise will fail App Store/Play Store review
Activation Code Traps
Format is LPA:1$SMDP+address$MatchingId β parse carefully, some codes omit optional parts $1 suffix means confirmation code required β flow differs, timeout is shorter Codes are often one-time use β SM-DP+ rejects reused MatchingId, must generate new code QR code is just encoding β the activation code content is what matters
Certification Requirements
GSMA SAS (Security Accreditation Scheme) mandatory for production SM-DP+ β cannot go live without it Use test eUICCs during development β production EIDs must not touch test environments GSMA TS.48 defines RSP test cases β certification testing follows this spec Entitlement server is separate from RSP β iOS carrier features require additional integration beyond profile provisioning
Consumer-Facing Pitfalls
QR codes expire β typically 24-72 hours, carrier-dependent, users panic when "invalid" Deleting profile is permanent on device β must request new activation code from carrier, no local recovery Device lock status matters β locked devices reject profiles from non-native carriers Regional variants of same phone model may lack eSIM hardware β verify before promising compatibility Profile transfer between devices almost never works β expect new activation per device
Carrier Integration Reality
MVNOs rarely operate own SM-DP+ β use MNO's infrastructure or aggregators (G+D, IDEMIA, Thales) Business agreements required before technical integration β ES2+ access isn't self-service Number porting complicates eSIM activation β may require physical SIM first depending on carrier process
Troubleshooting Specifics
"Profile already exists" error β delete existing profile before retry, or request new MatchingId from SM-DP+ Download fails mid-process β ES9+ requires stable HTTPS, retry on better connection, not a code issue Profile installed but no service β verify profile is enabled AND set as active line, restart radio
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md