---
title: AI skills for Android - Android
description: Use AI coding assistants to integrate, upgrade, and configure the Contentsquare Android SDK with downloadable AI skills
lastUpdated: 12 May 2026
source_url:
  html: https://docs.contentsquare.com/en/csq-sdk-android/experience-analytics/using-agent-skills/
  md: https://docs.contentsquare.com/en/csq-sdk-android/experience-analytics/using-agent-skills/index.md
---

> Documentation index: https://docs.contentsquare.com/llms.txt
> Use this file to discover all available pages before exploring further.

Use AI skills to let your AI coding assistant — GitHub Copilot, Cursor, Claude Code, or any compatible tool — handle Android SDK setup, version migration, and feature implementation.

[Download Android AI skills ](https://docs.contentsquare.com/skills/android/contentsquare-android-sdk.zip)contentsquare-android-sdk.zip

## Contentsquare AI skills Beta

Contentsquare provides **AI agent skills** for its SDK — structured files that enable AI coding assistants such as GitHub Copilot, Cursor, and Claude Code to integrate, upgrade, and configure the SDK with full awareness of the API surface, migration paths, and platform constraints.

## Installation

Copy the appropriate skill directory into your project. Place it in the location your AI assistant uses for context discovery:

| Assistant | Recommended location |
| - | - |
| GitHub Copilot | `.github/skills/` or `.agents/skills/` |
| Cursor | `.cursor/rules/` or project root |
| Claude Code | `.claude/skills/` or project root |
| Any (generic) | `.agents/skills/` |

No further configuration is required. The assistant discovers the skill automatically based on its metadata when a relevant task is requested. You can verify if the skill is discoverable by prompting your AI agent *"Which skills are available for you to use"*.

## How to use

Once the skill is present in your project, interact with your assistant using natural language. There is no need to reference filenames or paths explicitly.

### Integrate the SDK

> *"Integrate Contentsquare in this application."*

The assistant adds the dependency, configures initialization, sets up screen tracking, and scaffolds a privacy consent flow — all in accordance with Contentsquare best practices.

### Migrate between versions

> *"Upgrade Contentsquare to the latest version."*
>
> *"Migrate from 4.1.x to 4.2.x."*

The assistant loads the applicable migration playbook and applies the required changes, including API renames, removed fields, and deprecated method replacements.

### Implement specific features

> *"Track this button tap as a custom event."*
>
> *"Disable Session Replay auto-start and only collect the checkout flow."*

The assistant has full knowledge of the API surface and generates correct, idiomatic code for the target platform.

## Design principles

These skills are intentionally conservative:

* **Privacy by default.** The assistant never auto opts-in users. Consent management is always delegated to your implementation.
* **No fabricated identifiers.** If a data source ID or environment ID is not provided, the assistant prompts for one rather than assuming a value.

## Keeping skills up to date

Skills are versioned alongside SDK releases. When upgrading the SDK, replace the skill directory with the version corresponding to your new SDK release to keep documentation accurate.

## Troubleshooting

**The assistant does not recognize Contentsquare.** Confirm that the skill directory is in a path your assistant scans for context files. If unsure, place it at the project root. Restart the assistant session if it caches workspace state at startup.

**The assistant modifies the skill files.** Instruct the assistant to *use* the skill as a reference, not to edit it. Skill files are documentation artifacts — updates are distributed with SDK releases.

**The assistant produces outdated code.** The installed skill may correspond to an older SDK version. Replace it with the latest version from the current SDK release.