ClawHub

eSIM

v1.0.0

Implement and troubleshoot eSIM across consumer activation, carrier integration, and RSP development.

⭐ 2· 935·0 current·0 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The SKILL.md content (GSMA requirements, SM-DP+/RSP cautions, activation code format, troubleshooting) directly matches the name/description (implement and troubleshoot eSIM). Nothing in the manifest asks for unrelated access or credentials. Note: the skill source/homepage are missing (owner ID present), so provenance is unknown even though the technical content is coherent.
✓
Instruction Scope
The instructions are informational and operational guidance only; they do not tell the agent to read local files, access environment variables, call external endpoints, install tools, or transmit data. The guidance stays within the stated domain (consumer activation, carrier integration, RSP/test/certification).
✓
Install Mechanism
No install specification and no code files are present (instruction-only), so nothing will be written to disk or downloaded during install.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths. The content does reference platform entitlements and carrier certificates as external requirements, but it does not request or attempt to access them.
✓
Persistence & Privilege
Skill flags are default (always: false, model invocation allowed). The skill does not request persistent presence or system configuration changes.
Assessment
This skill is informational only and appears consistent with its stated purpose. Because it is instruction-only and requests no credentials or installs, it cannot on its own perform network or system actions. Before using it for production work: (1) verify the author/source because no homepage or repository is provided, (2) do not use production EIDs or credentials in test environments, and (3) ensure your organization has the required carrier agreements and GSMA SAS certification before following 'go-live' steps. If you plan to act on the guidance (e.g., integrate with SM-DP+ or entitlements), do so via known vendor tooling and authenticated channels rather than via ad-hoc scripts derived from this document.

Like a lobster shell, security has layers — review code before you run it.

latestvk978zhmez0rs63r4w1bp0j90ys80xvjx

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

📱 Clawdis
OSLinux · macOS · Windows

Comments