Damoov AI Skills and Plugin

Damoov provides a public AI skills repository for teams that want to speed up mobile SDK, backend API, platform management, analytics, and testing work with AI coding agents.

Repository: Mobile-Telematics/damoov-telematics-skills

The repository contains:

A self-hosted damoov-telematics plugin for Codex, Claude Code, Cursor, and compatible plugin-aware agents.
Standalone skills that can be installed manually into agents that support SKILL.md folders.
Reference files with Damoov-specific API details, SDK setup rules, endpoint names, request/response fields, testing flows, and safety constraints.

These skills are not a replacement for Damoov documentation. They are operational guidance for AI agents: they help an agent choose the correct Damoov integration path, avoid common API and SDK mistakes, and validate the result inside a customer codebase.

Why use the Damoov AI skills

For product and business teams, the skills reduce integration risk and make onboarding more predictable. They encode the main Damoov integration flows: mobile SDK setup, secure backend registration, DeviceToken handoff, DataHub-driven setup, user management, trips/statistics APIs, and test validation.

For developers, the skills give an AI coding agent Damoov-specific context before it edits code. This helps prevent generic implementation mistakes such as exposing InstanceKey in a mobile app, using outdated SDK method names, mixing Admin JWT and User JWT flows, or calling the wrong version of trips/statistics endpoints.

Recommended use cases:

New Damoov SDK integration in Android, iOS, Flutter, or React Native apps.
Backend-owned DeviceToken registration and secure User JWT issuance.
Admin API work for users, Applications, Instances, trips, scores, and statistics.
Integration review before production launch.
Test DeviceToken creation and end-to-end validation.
Migration or troubleshooting when trips, permissions, RTLD, or tracking modes do not work as expected.

Plugin vs standalone skills

Use the plugin when your AI tool supports plugin marketplaces. The plugin installs the complete Damoov skill set as one package and keeps the recommended entrypoint available.

Use standalone skills when your agent supports local SKILL.md folders but does not support plugins, or when your organization vendors skills directly into a project repository.

Recommended path:

Install the damoov-telematics plugin when possible.
Start every broad request with damoov-telematics-skill.
Let the orchestrator route to the correct target skill.
Use direct skills only when you already know the exact area: Android, iOS, Flutter, React Native, backend registration, user management, product management, trips/statistics, or testing.

Included skills

Skill	Area	Use when
`damoov-telematics-skill`	Orchestration	You want one customer-facing entrypoint that routes Damoov work to the right skill or skill sequence. Start here for broad requests.
`android-telematics-sdk-integration-skill`	Mobile SDK	Integrating, migrating, reviewing, or debugging native Android Kotlin apps, including Gradle/Maven setup, permissions, lifecycle, tracking modes, future tags, and SDK API migration.
`ios-telematics-sdk-integration-skill`	Mobile SDK	Integrating, migrating, reviewing, or debugging native iOS Swift apps, including SPM setup, `RPEntry`, lifecycle forwarding, background modes, permissions, tracking modes, and tags.
`flutter-telematics-sdk-integration-skill`	Mobile SDK	Integrating the Damoov Flutter plugin, including `pubspec.yaml`, Dart `TrackingApi`, Android host setup, iOS host setup, permission wizard wiring, tracking flows, and validation.
`react-native-telematics-sdk-integration-skill`	Mobile SDK	Integrating the `react-native-telematics` plugin, including TypeScript API usage, Android/iOS host setup, bridge behavior, permission wizard wiring, tracking flows, and validation.
`damoov-backend-registration-skill`	Backend	Implementing production DeviceToken registration, `InstanceKey` secrecy, hierarchy resolution, Admin JWT lifecycle, and secure User JWT issuance.
`damoov-user-management-skill`	Backend APIs	Finding, updating, deleting, or moving Damoov users, and managing service flags such as `EnableTracking`, `EnableLogging`, and `EnableRealTimeLocation`.
`damoov-product-management-skill`	Platform APIs	Creating, reading, updating, or deleting Damoov Applications and Instances with Admin JWT, including destructive-operation safeguards.
`damoov-trips-statistics-skill`	Analytics APIs	Fetching trips, trip details, safety scores, eco scores, driving statistics, daily breakdowns, consolidated indicators, and user-scoped/admin-scoped analytics.
`damoov-integration-testing-skill`	Testing	Creating test DeviceTokens through DataHub UI, direct registration, or JWT-driven hierarchy lookup, then validating the integration end to end.

Common integration routes

Use damoov-telematics-skill for any broad task. The orchestrator chooses the right route:

Scenario	Skill sequence
New production mobile integration with backend-owned DeviceToken	Backend registration -> target mobile SDK skill -> integration testing
Mobile-only SDK setup when a valid DeviceToken already exists	Target mobile SDK skill -> integration testing
End-to-end proof of a new integration	Integration testing -> target mobile SDK skill -> trips/statistics if analytics are required
Backend endpoint for DeviceToken registration and User JWT issuance	Backend registration
Backend endpoint to find or update a user flag such as `EnableTracking`	User management
Create test Application/Instance and register test users	Product management -> integration testing
User analytics endpoints for trips, scores, or statistics	Trips/statistics
RTD/RTLD enablement	User management -> target mobile SDK skill, plus DataHub Application-level RTD enablement
"No trips", "No Data", or emulator/simulator trip not detected	Integration testing GPS simulation guidance -> target mobile SDK skill

If the request is ambiguous, the orchestrator asks the smallest necessary routing question, for example:

Which mobile stack is this: Android, iOS, Flutter, or React Native?

Install the plugin in Codex

Codex installs plugins from a configured marketplace. The Damoov repository contains a marketplace definition at .agents/plugins/marketplace.json.

Install from GitHub:

codex plugin marketplace add Mobile-Telematics/damoov-telematics-skills
codex plugin add damoov-telematics@damoov-telematics

Optional: pin a branch, tag, or commit:

codex plugin marketplace add Mobile-Telematics/damoov-telematics-skills --ref main
codex plugin add damoov-telematics@damoov-telematics

Verify installation:

codex plugin list

Update marketplace snapshots after Damoov publishes a new version:

codex plugin marketplace upgrade

Remove the plugin if needed:

codex plugin remove damoov-telematics@damoov-telematics

After installation, start with:

Use $damoov-telematics-skill to route this Damoov integration task.

Example:

Use $damoov-telematics-skill to integrate Damoov into this Flutter app and tell me what backend data I need.

Install the plugin in Claude Code

Claude Code uses the marketplace definition at .claude-plugin/marketplace.json.

Inside Claude Code:

/plugin marketplace add Mobile-Telematics/damoov-telematics-skills
/plugin install damoov-telematics@damoov-telematics

After installation, plugin skills are namespaced:

/damoov-telematics:damoov-telematics-skill

Example:

/damoov-telematics:damoov-telematics-skill Review this repository and tell me whether the mobile SDK, backend registration, and trips APIs are wired correctly.

Install the plugin in Cursor

Cursor uses the marketplace definition at .cursor-plugin/marketplace.json.

For team distribution, import the repository as a team marketplace:

Dashboard -> Settings -> Plugins -> Import
Repository URL: https://github.com/Mobile-Telematics/damoov-telematics-skills

After installation, ask Cursor to use the Damoov orchestrator:

Use $damoov-telematics-skill to route this Damoov integration task.

Install standalone skills

Use this fallback when your agent supports skills but not plugins, or when you want project-level skills without installing the full plugin.

Set the repository value:

DAMOOV_REPO="Mobile-Telematics/damoov-telematics-skills"

List available skills:

npx skills add "$DAMOOV_REPO" --list

Install all skills for Codex:

npx skills add "$DAMOOV_REPO" --skill '*' --agent codex -y

Install all skills for Claude Code:

npx skills add "$DAMOOV_REPO" --skill '*' --agent claude-code -y

Install all skills for every supported local agent:

npx skills add "$DAMOOV_REPO" --skill '*' --agent '*' -y

Install one skill only:

npx skills add "$DAMOOV_REPO" --skill damoov-telematics-skill --agent codex -y
npx skills add "$DAMOOV_REPO" --skill android-telematics-sdk-integration-skill --agent codex -y
npx skills add "$DAMOOV_REPO" --skill ios-telematics-sdk-integration-skill --agent codex -y
npx skills add "$DAMOOV_REPO" --skill flutter-telematics-sdk-integration-skill --agent codex -y
npx skills add "$DAMOOV_REPO" --skill react-native-telematics-sdk-integration-skill --agent codex -y
npx skills add "$DAMOOV_REPO" --skill damoov-backend-registration-skill --agent codex -y
npx skills add "$DAMOOV_REPO" --skill damoov-user-management-skill --agent codex -y
npx skills add "$DAMOOV_REPO" --skill damoov-product-management-skill --agent codex -y
npx skills add "$DAMOOV_REPO" --skill damoov-trips-statistics-skill --agent codex -y
npx skills add "$DAMOOV_REPO" --skill damoov-integration-testing-skill --agent codex -y

Install from a local clone:

git clone https://github.com/Mobile-Telematics/damoov-telematics-skills.git
cd damoov-telematics-skills
npx skills add . --skill '*' --agent codex -y

Update installed skills:

npx skills update -y

Update global skills:

npx skills update --global -y

Manual project installation

Use manual installation when your agent reads skill folders directly or when your organization vendors skills into a customer repository.

Keep the repository layout intact. Several skills reference shared files in sibling folders.

Codex project install:

SKILLS_SRC="$PWD/vendor/damoov-telematics-skills"
mkdir -p .agents/skills
ln -sfn "$SKILLS_SRC/skills" .agents/skills/damoov-telematics

Cursor project install:

SKILLS_SRC="$PWD/vendor/damoov-telematics-skills"
mkdir -p .cursor/skills
ln -sfn "$SKILLS_SRC/skills" .cursor/skills/damoov-telematics

Claude Code project install:

SKILLS_SRC="$PWD/vendor/damoov-telematics-skills"
mkdir -p .claude/skills
ln -sfn "$SKILLS_SRC/skills" .claude/skills/damoov-telematics

For other agents, use the equivalent project-level skills directory and symlink or copy the whole skills/ subtree so relative links continue to resolve.

How to use the skills

Start with the orchestrator for broad work:

Use $damoov-telematics-skill to integrate Damoov into this Android app. The backend should own DeviceToken registration.

Use a direct skill for a narrow task:

Use $damoov-backend-registration-skill to implement a backend endpoint that registers a Damoov user and stores the DeviceToken linked to my app user.

Use $damoov-user-management-skill to add an admin endpoint that finds a user by DeviceToken and updates EnableTracking.

Use $damoov-trips-statistics-skill to add backend endpoints for trips, safety scores, eco scores, and driving statistics.

Use $damoov-integration-testing-skill to create a repeatable test DeviceToken flow for this repository.

Ask the agent to state the selected route before editing code:

Use $damoov-telematics-skill. Before editing code, tell me which Damoov target skill or skill sequence you selected.

Ask the agent to cite the Damoov reference file it used when endpoint names, fields, or SDK methods matter:

Use $damoov-telematics-skill to implement trips analytics. Cite the Damoov skill reference file used for endpoint names, request fields, and response fields.

Recommended prompts by role

Product or business owner:

Use $damoov-telematics-skill to review our planned Damoov integration. Tell me which parts belong to mobile, backend, DataHub setup, and QA validation.

Mobile developer:

Use $damoov-telematics-skill to integrate Damoov SDK into this React Native app. DeviceToken comes from our backend login response. Primary flow is automatic tracking.

Backend developer:

Use $damoov-backend-registration-skill to implement production DeviceToken registration. InstanceKey must stay server-side, Admin JWT must be cached and refreshed, and mobile clients must only receive DeviceToken and User JWT when authenticated.

QA engineer:

Use $damoov-integration-testing-skill to create a test DeviceToken, validate it through the API, run a simulator/emulator trip if possible, and document the expected checks.

Data/API developer:

Use $damoov-trips-statistics-skill to add endpoints for trip list, trip details, safety score, eco score, and driving statistics for one DeviceToken.

Support engineer:

Use $damoov-telematics-skill to troubleshoot why this test user shows No Data after SDK integration. Check DeviceToken registration, mobile SDK setup, permissions, and simulator location flow.

Security and operational rules

Never commit real Damoov credentials or production identifiers into source code, docs, tests, prompts, logs, or skill files.

Use placeholders in examples:

<CompanyId>
<AppId>
<InstanceId>
<InstanceKey>
<DeviceToken>
<admin-jwt>
<user-jwt>

Important constraints encoded in the skills:

InstanceKey is an instance-level secret and must stay on the backend.
Mobile apps should receive a registered DeviceToken, then call the SDK identity method such as setDeviceID or setDeviceId.
Admin JWT and User JWT have different scopes. Do not use them interchangeably.
POST /v1/Auth/Login is rate-limited. Cache tokens and use refresh flows instead of repeated login calls.
User deletion is irreversible and removes associated telematics data. Require explicit confirmation before destructive operations.
Application and Instance deletion must respect user cleanup rules.
Trips/statistics endpoint versions and auth type matter. The skills route agents to the current documented patterns.
Test users should be created in dedicated test Applications or Instances, not production Instances.

Troubleshooting installation

If the plugin or skills do not appear in the agent:

Confirm the repository was added as a plugin marketplace or that skills were installed into the correct agent.
Confirm each installed skill folder contains SKILL.md.
Restart the agent if it does not hot-reload plugins or skills.
For manual installation, keep the full skills/ tree intact so cross-skill references resolve.
Use an explicit prompt: Use $damoov-telematics-skill ....
If generated code looks generic, ask the agent to name the Damoov skill it selected and cite the reference file it used.