Cometchat Android V6 Extensions

Organization

cometchat

cometchat-android-v6-extensions

Turn on CometChat Dashboard extensions in an Android v6 app — stickers, polls, collaborative whiteboard and document, message translation, link preview, thumbnail generation, message shortcuts — and know exactly where each one appears in the UI once enabled (mostly zero client code). Triggers: 'enable stickers android', 'add polls to my android chat', 'message translation android cometchat', 'link previews not showing', 'what extensions does the android ui kit support'.

Overview

Publisher	cometchat
Repository	`cometchat-skills`
Skill name	`cometchat-android-v6-extensions`
Stars	109
Forks	2
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by cometchat on GitHub. Read the source before you install it.

Installation

Install the Cometchat Android V6 Extensions AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/cometchat/cometchat-skills/tree/main/skills/cometchat-android-v6-extensions

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/cometchat/cometchat-skills.git /tmp/cometchat-skills
mkdir -p .claude/skills
cp -r /tmp/cometchat-skills/skills/cometchat-android-v6-extensions .claude/skills/cometchat-android-v6-extensions

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cometchat Android V6 Extensions in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cometchat Android V6 Extensions on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cometchat Android V6 Extensions is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Ground truth: features.android-v6.json (the extension entries + their enablement) + catalog android-v6.json + the live page /ui-kit/android/extensions (the manual — 8 built-ins) and each extension's /fundamentals/* page. Verify symbols against the catalog; fetch details from docs; never invent an extension.

Companion skills (read first)

cometchat-android-v6-core — install, credentials, initFromSettings → login → render, the fetch map. Assumed here, never repeated.
cometchat-android-v6-features — the general feature-lookup skill; come here for the Dashboard-extension slice specifically.

Use this skill when

"enable stickers/polls/whiteboard/document/translation/link preview/thumbnails", "add message shortcuts", "which extensions work with the Android UI Kit?", "I enabled it in the Dashboard but nothing shows up".

Prerequisites & install

Same kit + initFromSettings → login as core. No Gradle dependency and (for the 7 auto-rendered ones) no client code — the UI Kit detects an enabled extension after init+login and renders it in the right component.

The 8 built-ins — enable in Dashboard, appears here

Extension	Enable	Where it appears once enabled
Stickers	Dashboard → Extensions	Composer (sticker keyboard → `CometChatStickerKeyboard`; sent as `CometChatStickerBubble`)
Polls	Dashboard → Extensions	Composer action sheet (`CometChatCreatePoll`; rendered as `CometChatPollBubble`)
Collaborative Whiteboard	Dashboard → Extensions	Composer action sheet; opens as a collaborative bubble in the list
Collaborative Document	Dashboard → Extensions	Composer action sheet; opens as a collaborative bubble in the list
Message Translation	Dashboard → Extensions	Message long-press/action sheet in `CometChatMessageList`
Link Preview	Dashboard → Extensions	Automatically inside message bubbles for URLs
Thumbnail Generation	Dashboard → Extensions	Automatically on image/video bubbles (smaller previews)
Profanity Filter	Dashboard → Extensions	Message bubbles (censored text) — ⚠️ LEGACY

Message Shortcuts is the one extension that is NOT zero-code: enable it in the Dashboard, then implement a shortcut formatter extending CometChatTextFormatter — build it from the docs recipe /ui-kit/android/shortcut-formatter-guide (→ cometchat-android-v6-{kotlin,compose}-customization for the formatter mechanism).

Enablement — the whole flow

Ask which are already enabled — per-app Dashboard state is not readable from code; never assume OFF (and never re-suggest one that's already on).
Enable in the CometChat Dashboard → your app → Extensions → the extension. That's the actual "installation".
Re-login / restart the app — the kit picks extensions up at init+login; a session started before you toggled won't show it.
Verify in the right place (table above). No code change, no rebuild, for the 7 auto-rendered ones.
Only if the ask is styling the extension's UI → cometchat-android-v6-{kotlin,compose}-customization.

Deprecated / superseded — don't offer these

Profanity Filter is LEGACY: the extensions page still lists it, but its guide points at the legacy-docs archive. For new work steer to the Moderation product (features.android-v6.json → moderation, dashboard-configured rules + AI moderation) — say this plainly rather than wiring the legacy path. Anything not in the table above and not in features.android-v6.json does not exist for this kit: don't invent extensions (no "reactions extension" — reactions are core in v6; same for mentions).

Common pitfalls

Writing client code for an auto-rendered extension (never needed) · hand-rolling polls/stickers UI that the kit already renders · enabling in the Dashboard but not re-logging in · expecting an extension before init+login succeed · offering Profanity Filter for new work · treating reactions/mentions as extensions (they're core in v6) · assuming an extension enabled on one app applies to another (per-app setting).

Verify it works

No catalog/compile change is expected for the auto-rendered ones (nothing was emitted); for Message Shortcuts, compile (./gradlew :app:assembleDebug # in YOUR app (npm run verify:fences:android-v6 is a pack-repo gate)) and confirm the formatter is registered. On device, after enabling + re-login: the extension's entry point is present where the table says (composer action sheet / sticker keyboard / message action sheet / inside the bubble) and a sent artifact renders as its bubble type. Nothing showing ⇒ check init/login succeeded, then the Dashboard toggle for THIS app, then re-login — in that order.

Frequently asked questions

What does the Cometchat Android V6 Extensions AI skill do?

Why use Cometchat Android V6 Extensions on TypingMind?

Because you install it once and use it with any model. Cometchat Android V6 Extensions is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cometchat Android V6 Extensions in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cometchat/cometchat-skills/tree/main/skills/cometchat-android-v6-extensions. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Cometchat Android V6 Extensions?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cometchat Android V6 Extensions?

As many as you like. As long as a model supports skills, you can use Cometchat Android V6 Extensions with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cometchat Android V6 Extensions AI skill free?

Yes. It is published on GitHub by cometchat under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Writing Fragments

mattpocock

CommunityPopular

Writing, explore: mine raw fragments, no structure yet.

Writing For Agents

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Karpathy Guidelines

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define…

Create Agent

Create a custom agent (.agent.md) for a specific job.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Companion skills (read first)

Use this skill when

Prerequisites & install

The 8 built-ins — enable in Dashboard, appears here

Enablement — the whole flow

Deprecated / superseded — don't offer these

Common pitfalls

Verify it works

Frequently asked questions

Related AI Skills

Set up your own AI workspace now