skills.rest
OpenLitterMap
OpenLitterMapOFFICIAL
Explore all skills by this author →
Website𝕏@OpenLitterMapGitHub

mobile-shim

Consolidate v3 mobile API endpoints and enforce v5 CLO tag format.

132|42|Updated Aug 19, 2020
Search Tags:#security#mobile-api#v3-endpoints#tagging-format#sanctum-auth#endpoint-migration#clo-format
One-click install
npx skills add https://github.com/OpenLitterMap/openlittermap-web --skill mobile-shim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mobile-shim
Source: https://github.com/OpenLitterMap/openlittermap-web/tree/main/.ai/skills/mobile-shim
Command: npx skills add https://github.com/OpenLitterMap/openlittermap-web --skill mobile-shim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Mobile Shim consolidates v3 mobile API access, removing outdated v1/v2/v4 endpoints and standardizing the v5 CLO tag format, reducing integration complexity for mobile clients.

Core Features & Use Cases

  • Consolidated v3 mobile endpoints: authentication, uploads, tag management, and user data access.
  • Enforces v5 CLO tag format for consistent data exchange across apps.
  • Use Case: Mobile apps migrate to v3/v5 and rely on a single, stable API surface with predictable responses.

Quick Start

Configure and verify the v3 mobile API surface using the v5 CLO tag format.

Frequently Asked Questions about mobile-shim

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

FAQPage Schema
How do I consolidate mobile API endpoints to a single stable surface?▼

You can consolidate mobile API endpoints by migrating to v3, which removes legacy v1, v2, and v4 paths to provide a single, stable API surface for mobile clients. This reduces integration complexity and ensures predictable API responses.

What is the v5 CLO tag format for mobile API payloads?▼

The v5 CLO tag format is the standardized data exchange structure enforced on mobile API payloads. It provides a consistent tagging workflow across mobile applications, ensuring data uploaded through v3 endpoints adheres to strict formatting rules.

Do I need Sanctum token authentication for mobile API v3 endpoints?▼

Yes, Sanctum token authentication is required for mobile API v3 endpoints. The mobile API surface enforces Sanctum-based token authentication to secure access to authentication, uploads, tag management, and user data.

How do I migrate mobile clients from legacy API paths to v3?▼

Migrate mobile clients to the v3 API surface by removing outdated v1, v2, and v4 endpoint integrations and adopting the consolidated v3 endpoints. This process enforces the v5 CLO tag format for all data payloads during migration.

Are legacy mobile API endpoints still supported after v3 migration?▼

No, legacy v1, v2, and v4 mobile API endpoints are removed during the v3 consolidation. The mobile API surface eliminates outdated paths to reduce integration complexity and enforce a single, stable connection point for mobile clients.

Can I manage mobile app tags using the v3 API surface?▼

Yes, the consolidated v3 mobile API endpoints include tag management functionality. Mobile apps can manage tags through this single stable surface, provided the payloads adhere to the enforced v5 CLO tag format.

Related Skills

Explore More Software Engineering Skills→
OpenLitterMapOpenLitterMap
132

api-endpoints

Document REST API routes and auth guards for SPA and mobile clients.

Official
Advanced
lifeodysseylifeodyssey
1

google-a2ui

Translate agent intentions into declarative A2UI component payloads for web and mobile clients.

Community
Intermediate
OpenLitterMapOpenLitterMap
132

photo-pipeline

Orchestrate OpenLitterMap photo uploads through tagging, verification, and XP generation.

Official
Advanced
transilienceaitransilienceai
462

web-application-mapping

Coordinate web-application reconnaissance to identify attack surfaces.

Official
Basic