hdtrieu

Android Agent Skills — Development skill for Claude Code

Development community

A Claude Code plugin marketplace with skills for Android engineering: Kotlin/Compose.

How to install Android Agent Skills

This entry records only its repository, not the path inside it, so there is no exact command to give. Open hdtrieu/android-agent-skills and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Android Agent Skills does

A Claude Code plugin marketplace with skills for Android engineering: Kotlin/Compose.

Alternatives in Development

  • Routing — Reverse Engineering Skill Routing Matrix 29.6k ★
  • Kotlin Lsp — Kotlin /plugin install kotlin-lsp@claude-plugins-official 14k ★
  • Lamda — The most powerful Android RPA agent framework, next generation mobile automation 7.7k ★

README

Android Agent Skills

A Claude Code plugin marketplace with skills for Android engineering: Kotlin/Compose conventions, Clean Architecture + MVI, tests, local review, root-cause analysis, Maestro E2E, implementation plans, Jira ticket branches and GitLab merge requests.

Nothing company-specific is bundled. Jira, Confluence, GitLab and Figma access, and your team's branch and commit rules, come from **your own environment variables** or your repository's instructions.

Install

In Claude Code:

/plugin marketplace add hdtrieu/android-agent-skills
/plugin install android-skills@android-agent-skills

Skills are namespaced, e.g. `/android-skills:jira-ticket ABC-123`. Claude also loads them automatically when a task matches their description.

Skills

Skill Purpose
android-conventions Kotlin, Compose, Hilt, Coroutines and layer rules for writing or reviewing code
implement-mvi-feature Plan/implement a screen with Action/UiState/Result, pure Reducer, ViewModel
writing-tests Choose the right test layer; 12 regression archetypes; deterministic coroutine tests
local-review Pre-MR review loop with the reviewer agent, a per-branch decision ledger and ticket test-case coverage
root-cause-analysis Diagnose a defect from evidence before fixing it
maestro-e2e Write and run Maestro flows; screenshots against the design
implementation-plan Ticket + PRD + discussions + repos → scoped, estimated plan with Gantt
jira-ticket Read a Jira ticket, extract acceptance criteria, prepare the branch
create-mr Commit, push and open a GitLab MR (or GitHub PR) with review/CI gates
mr-review Resolve MR review threads in a loop: triage, fix, test, reply, resolve, push
project-integrations Jira, Confluence, GitLab and Figma access and the REST fallback

Shared references: [MVI contract](plugins/android-skills/references/mvi.md), [module structure](plugins/android-skills/ref