Agent skill

Quality Test Pilot

by nekomangaorg in nekomangaorg/Neko

Writes high-quality unit tests for Kotlin Android codebases to increase meaningful test coverage.

Apache-2.0Auto-check passedTesting & QA

Install Quality Test Pilot

skills CLI
$ npx skills add nekomangaorg/Neko --skill quality-test-pilot -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nekomangaorg/Neko quality-test-pilot --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nekomangaorg/Neko.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'.agents/skills/test pilot' .claude/skills/quality-test-pilot && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
quality-test-pilot
GitHub stars
2.8k
Token cost
~1.1k tokens
SKILL.md length
563 words
Files
2
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Writes high-quality unit tests for Kotlin Android codebases to increase meaningful test coverage.

  • Works in 5 steps: SCAN: Look for coverage gaps. Target… → SELECT & PROPOSE: Pick the BEST… → BUILD (Upon Approval): Implement with… → …
  • Add tests for untested edge cases
  • SKILL.md covers ✅ Always do:, ⚠️ Ask first: and 🚫 Never do:
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Quality Test Pilot is an agent skill from nekomangaorg/Neko. Writes high-quality unit tests for Kotlin Android codebases to increase meaningful test coverage. Use this skill to add tests for untested edge cases, ViewModel states, exception handling blocks, or UseCases using MockK, runTest, and the Given-When-Then pattern.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `journal.md`).

It sits in Testing & QA, covering Test coverage, Android development and Unit testing. It works with Kotlin and Android. The repository describes itself as: Unofficial MangaDex Reader for Android 8+. The licence is Apache-2.0.

When your agent uses it

  • Add tests for untested edge cases
  • ViewModel states
  • Exception handling blocks
  • UseCases using MockK

Example prompts

  • “Use the quality-test-pilot skill to write high-quality unit tests for Kotlin Android codebases to increase meaningful test coverage”
  • “/quality-test-pilot”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. SCAN: Look for coverage gaps. Target ViewModel state flows that are never collected or asserted, error states, exception handling blocks…
  2. SELECT & PROPOSE: Pick the BEST opportunity that targets critical business logic (not UI or simple getters), covers a specific "sad path"…
  3. BUILD (Upon Approval): Implement with precision. Set up mocks clearly using mockk(). Structure the test with Arrange, Act, Assert…
  4. VERIFY: Run ./gradlew ktfmtFormat to format your test code. Run the specific test class (./gradlew testDebugUnitTest --tests…
  5. PRESENT: Create a PR using Conventional Commits with the test: prefix (e.g., test: add coverage for network timeout exception in…

What it can do on your machine

Read from SKILL.md and the folder at commit e52cc82. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quality Test Pilot loads about 1.1k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 563 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nekomangaorg/Neko at commit e52cc82, republished under its Apache-2.0 licence (© nekomangaorg). 563 words, ~1,058 tokens.

Download SKILL.mdSave it as .claude/skills/quality-test-pilot/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
quality-test-pilot
description
Writes high-quality unit tests for Kotlin Android codebases to increase meaningful test coverage. Use this skill to add tests for untested edge cases, ViewModel states, exception handling blocks, or UseCases using MockK, runTest, and the Given-When-Then pattern.

Goal

You are "Test Pilot" 🧪 - a quality assurance agent who bulletproofs the Kotlin codebase by increasing meaningful test coverage. Your mission is to write ONE high-quality unit test for an untested edge case, ViewModel state, or UseCase.

Philosophy:

  • Untested code is broken code.
  • Test behavior, not implementation details.
  • Edge cases are where the bugs live.
  • A failing test is a feature, not a bug.

Journaling Rules (Read .agents/skills/test pilot/journal.md before starting and write learnings to it): Your journal is NOT a log - only add entries for CRITICAL testing learnings. Format as ## YYYY-MM-DD - [Title] \n **Learning:** [Insight] \n **Action:** [How to apply next time]. Ensure the date is the exact date of the run (not a past/future date). ONLY log things like: a specific way this app handles CoroutineTestDispatchers, a fragile mock pattern that causes flaky tests, or how this app provides dependency injection in test environments. DO NOT journal routine work like "Added test for LoginViewModel" or generic JUnit tips.

Constraints

✅ Always do:

  • Explain the coverage gap or untested edge case identified and the proposed unit test design, then wait for user approval before writing test code.
  • Run ./gradlew ktfmtFormat to ensure the new test file matches project formatting.
  • Run ./gradlew testDebugUnitTest before creating a PR.
  • Use the project's preferred mocking framework (e.g., MockK) and coroutine testing libraries (runTest).
  • Follow the Given-When-Then (or Arrange-Act-Assert) pattern strictly.
  • Clean up test coroutine dispatchers after tests complete.

⚠️ Ask first:

  • Refactoring production code heavily just to make it testable.
  • Adding new testing dependencies to the Gradle files.

🚫 Never do:

  • Write UI/Espresso tests (too flaky for autonomous daily runs).
  • Modify src/main code to force a test to pass.
  • Write empty tests or tests without assertions.
  • Use Thread.sleep() or hardcoded delays in tests.
  • Never use the prefix refactor: in PR titles or commits. Use test: instead.
Show full SKILL.md (263 more words)Show less

Instructions

  1. SCAN: Look for coverage gaps. Target ViewModel state flows that are never collected or asserted, error states, exception handling blocks, network failure paths, business logic with complex conditional branches in UseCases/Repositories, or Flow transformations (map, combine).
  2. SELECT & PROPOSE: Pick the BEST opportunity that targets critical business logic (not UI or simple getters), covers a specific "sad path" or edge case, and can be written cleanly without complex database emulation. Explain what was identified and detail the proposed test scenario (Given-When-Then). Wait for user approval before writing code.
  3. BUILD (Upon Approval): Implement with precision. Set up mocks clearly using mockk(). Structure the test with Arrange, Act, Assert comments. Use descriptive, sentence-like test names (e.g., given network error when fetching data then state is Error).
  4. VERIFY: Run ./gradlew ktfmtFormat to format your test code. Run the specific test class (./gradlew testDebugUnitTest --tests "YourTestClass"). Verify it correctly fails if the production behavior is temporarily inverted (mutation testing mindset), then passes when restored.
  5. PRESENT: Create a PR using Conventional Commits with the test: prefix (e.g., test: add coverage for network timeout exception in AuthViewModel). Include What and Why in the description.

Examples

  • Adding a runTest block to verify a ViewModel emits the correct Error state when a repository throws an exception.
  • Using mockk to stub a repository response and assert that a UseCase maps the data correctly.
  • Writing a given network error when fetching data then state is Error test method.
  • Adding a unit test to cover the "sad path" of a login flow, ensuring the correct validation messages are generated.

© nekomangaorg, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/test pilot of nekomangaorg/Neko.

  • SKILL.md
  • journal.md

Open the folder on GitHubat commit e52cc82

Compare with similar skills

Quality Test Pilot next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Quality Test Pilot compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quality Test Pilot this skillnekomangaorg/Neko2.8k—~1.1kAutomated safety check: PassApache-2.0
Improve Code Coveragealexvanyo/composelife267—~1.1kAutomated safety check: PassApache-2.0
Mocking With Mockitoskydoves/android-testing-skills334—~4.5kAutomated safety check: PassApache-2.0
Mocking With Mockkskydoves/android-testing-skills334—~4.1kAutomated safety check: PassApache-2.0
Android Data Layer and Room in KMPrcosteira79/android-skills153—~1.2kAutomated safety check: PassMIT
Writing Tests With Kotlin Testskydoves/android-testing-skills334—~4.2kAutomated safety check: PassApache-2.0

Similar skills

  • Improve Code Coverage

    alexvanyo/composelife

    Helps increment code coverage in this Kotlin Multiplatform project.

    267 GitHub stars~1.1k tokensUpdated today
    MobileAuto-check passed
  • Mocking With Mockito

    skydoves/android-testing-skills

    A skill your agent uses to wire Mockito (the dominant Android mocking framework, exclusively used by androidx itself) into a JVM unit-test suite.

    334 GitHub stars~4.5k tokensUpdated 4 mo ago
    Testing & QAAuto-check passed
  • Mocking With Mockk

    skydoves/android-testing-skills

    A skill your agent uses to wire MockK (the Kotlin-first mocking framework) into a JVM unit-test suite, especially when coroutines, singleton/object mocking, or constructor mocking dominate.

    334 GitHub stars~4.1k tokensUpdated 4 mo ago
    Testing & QAAuto-check passed
  • Android Data Layer and Room in KMP

    rcosteira79/android-skills

    Sets out the repository pattern's error-propagation model for Android and Kotlin Multiplatform, plus the Room setup for commonMain.

    153 GitHub stars~1.2k tokensUpdated 21 days ago
    MobileAuto-check passed
  • Writing Tests With Kotlin Test

    skydoves/android-testing-skills

    A skill your agent uses to write tests with the kotlin.test library — the multiplatform assertion + annotation API that compiles the same in commonTest and on the JVM (JUnit4 or JUnit5), Android…

    334 GitHub stars~4.2k tokensUpdated 4 mo ago
    MobileAuto-check passed
  • Kotlin Coroutines

    rcosteira79/android-skills

    A skill your agent uses when writing, reviewing, or debugging coroutine code in Kotlin — including dispatcher selection, scope management, structured concurrency, cancellation, exception handling…

    153 GitHub stars~1.5k tokensUpdated 21 days ago
    DevelopmentAuto-check passed

More from nekomangaorg/Neko

All 15 skills in this repo
  • Architecture Overclock

    nekomangaorg/Neko

    Resolves deep, structural performance bottlenecks in the Kotlin Android codebase.

    2.8k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Architecture Renovator

    nekomangaorg/Neko

    Resolves deep architectural debt in the Kotlin Android codebase through macro-level refactoring.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Build Foreman

    nekomangaorg/Neko

    Optimizes Gradle build scripts, compilation times, and Android Studio sync performance.

    2.8k GitHub stars~807 tokensUpdated yesterday
    Auto-check passed
  • Code Steward

    nekomangaorg/Neko

    Maintains Kotlin codebase health, idiomatic style, and modern API usage.

    2.8k GitHub stars~977 tokensUpdated yesterday
    Auto-check passed
  • Domain Distiller

    nekomangaorg/Neko

    Extracts duplicated or tangled business logic from ViewModels, Repositories, or UI components into pure, highly testable Kotlin Use Cases (Interactors) following the Single Responsibility Principle.

    2.8k GitHub stars~1k tokensUpdated yesterday
    Auto-check passed
  • Frontend Artisan

    nekomangaorg/Neko

    Elevates the Jetpack Compose user interface through micro-UX improvements, animations, accessibility (a11y) fixes, and UI structural polish.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Quality Test Pilot

What does Quality Test Pilot do?

Writes high-quality unit tests for Kotlin Android codebases to increase meaningful test coverage. Quality Test Pilot is an agent skill from nekomangaorg/Neko. Writes high-quality unit tests for Kotlin Android codebases to increase meaningful test coverage.

When should I use Quality Test Pilot?

Quality Test Pilot fits situations like: add tests for untested edge cases; viewModel states; exception handling blocks; useCases using MockK.

How do I install Quality Test Pilot in Claude Code?

Run `npx skills add nekomangaorg/Neko --skill quality-test-pilot -a claude-code`. Or copy the skill folder (.agents/skills/test pilot in nekomangaorg/Neko) into .claude/skills/quality-test-pilot in your project. Claude Code loads it when a task matches its description.

How do I install Quality Test Pilot in Codex?

Run `npx skills add nekomangaorg/Neko --skill quality-test-pilot -a codex`. Or copy the skill folder (.agents/skills/test pilot in nekomangaorg/Neko) into .agents/skills/quality-test-pilot in your project. Codex loads it when a task matches its description.

Can I use Quality Test Pilot in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nekomangaorg/Neko --skill quality-test-pilot -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quality-test-pilot, .gemini/skills/quality-test-pilot, .github/skills/quality-test-pilot and .opencode/skills/quality-test-pilot in your project.

What does Quality Test Pilot need to run?

SKILL.md names no scripts, command-line tools or credentials: Quality Test Pilot is instructions for the agent only.

Does Quality Test Pilot access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Quality Test Pilot safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Quality Test Pilot use?

Quality Test Pilot is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Quality Test Pilot use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Quality Test Pilot?

Skills that share tags, products or a category with Quality Test Pilot: Improve Code Coverage (alexvanyo/composelife, 267 stars), Mocking With Mockito (skydoves/android-testing-skills, 334 stars), Mocking With Mockk (skydoves/android-testing-skills, 334 stars) and Android Data Layer and Room in KMP (rcosteira79/android-skills, 153 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quality Test Pilot?

nekomangaorg (a GitHub organization) maintains it in nekomangaorg/Neko, which has 2,812 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 9, 2026.

Source: nekomangaorg/Neko on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.