← IMEILookupCONTENT HISTORY

Update to IMEILookup

Snapshot Nov 5, 2026 · 06:11 UTC · version 1.0.3

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save IMEILookup and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when the user asks what checks are available, wants to compare prices or coverage, or you need to select a compatible service before ordering.",
  "included_files": [],
  "name": "browse-services",
  "skill_md_contents": "---\nname: browse-services\ndescription: Use when the user asks what checks are available, wants to compare prices or coverage, or you need to select a compatible service before ordering.\n---\n\n# Browsing and selecting services\n\nThe user does not need an exact service name or ID. Resolve their intended check from the request and conversation, then use `list_services` to retrieve the catalogue.\n\n## Retrieving the catalogue\n\nCall `list_services` with `page=0` (0-based) and `size=200` by default. Check the returned total and follow pagination when needed before claiming the catalogue or price comparison is complete. A single page is sufficient when it contains every available service. There is no search parameter.\n\nUse the returned `id`, `title`, `price`, `time`, `limit`, `allowedIdentifiers`, and `sample` fields. `sample` is an illustrative example of output fields.\n\n## Selecting a service\n\n- Match the user's requested outcome and selection criteria to a compatible service.\n- Compare compatibility, coverage, and current price using descriptions and samples.\n- Use `allowedIdentifiers` to check whether a service accepts IMEI, serial number, or MEID. Determine brand coverage from the returned service title, description, and sample where explicit. Identifier support alone does not establish brand coverage.\n- Missing or empty metadata means \"unknown\", not \"universal\". Do not claim planned metadata is available before the live response includes it.\n- `sample` shows possible output fields; it is not a fresh device result.\n\n## Delegated vs ambiguous requests\n\n- \"Cheapest suitable Apple service\" → choose the cheapest compatible service and explain its coverage.\n- \"Check this phone\" → ask a short clarifying question about which check is wanted.\n- Ask only when the request or compatibility remains genuinely unresolved.\n\n## Notes\n\n- Model, model number, warranty, GSMA Blocklist, SIM-lock, carrier, FMI, and MDM coverage vary by service and identifier. Never assume a service supports every field.\n- Do not add paid services to fill missing fields without the user's authorization.\n"
}

SHA-256 of public snapshot: 37647f8d4d7851018ec0e2ba0fc96364fb93e6795af67676203cd5ec7ecdd434