Agent skill

Implement Navigation

by MartinStyk in MartinStyk/apk-analyzer

A skill your agent uses when adding a new screen destination to a feature, wiring navigation between screens, implementing an entry provider, or connecting NavKeys.

GPL-3.0Auto-check passedMobile

Install Implement Navigation

skills CLI

$ npx skills add MartinStyk/apk-analyzer --skill implement-navigation -a claude-code

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

GitHub CLI

$ gh skill install MartinStyk/apk-analyzer implement-navigation --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/MartinStyk/apk-analyzer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/implement-navigation .claude/skills/implement-navigation && 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/

Paste into Claude Code

Install the "implement-navigation" agent skill from https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/implement-navigation into .claude/skills/implement-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-navigation", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/implement-navigation

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add MartinStyk/apk-analyzer --skill implement-navigation -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install MartinStyk/apk-analyzer implement-navigation --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/MartinStyk/apk-analyzer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/implement-navigation .agents/skills/implement-navigation && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "implement-navigation" agent skill from https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/implement-navigation into .agents/skills/implement-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-navigation", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add MartinStyk/apk-analyzer --skill implement-navigation -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install MartinStyk/apk-analyzer implement-navigation --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/MartinStyk/apk-analyzer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/implement-navigation .cursor/skills/implement-navigation && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "implement-navigation" agent skill from https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/implement-navigation into .cursor/skills/implement-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-navigation", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/MartinStyk/apk-analyzer.git --path .claude/skills/implement-navigation

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add MartinStyk/apk-analyzer --skill implement-navigation -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install MartinStyk/apk-analyzer implement-navigation --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/MartinStyk/apk-analyzer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/implement-navigation .gemini/skills/implement-navigation && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "implement-navigation" agent skill from https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/implement-navigation into .gemini/skills/implement-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-navigation", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install MartinStyk/apk-analyzer implement-navigation

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add MartinStyk/apk-analyzer --skill implement-navigation -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/MartinStyk/apk-analyzer.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/implement-navigation .github/skills/implement-navigation && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "implement-navigation" agent skill from https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/implement-navigation into .github/skills/implement-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-navigation", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add MartinStyk/apk-analyzer --skill implement-navigation -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install MartinStyk/apk-analyzer implement-navigation --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/MartinStyk/apk-analyzer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/implement-navigation .opencode/skills/implement-navigation && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "implement-navigation" agent skill from https://github.com/MartinStyk/apk-analyzer/tree/develop/.claude/skills/implement-navigation into .opencode/skills/implement-navigation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-navigation", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: implement-navigation
GitHub stars: 368
Token cost: ~1.2k tokens
SKILL.md length: 223 words
Files: 1
Skills in repo: 18
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: GPL-3.0

At a glance

A skill your agent uses when adding a new screen destination to a feature, wiring navigation between screens, implementing an entry provider, or connecting NavKeys.

Works in 6 steps: Create internal NavKey → Create the screen composable → Register entry in the feature's entry… → …
Adding a new screen destination to a feature
SKILL.md covers Scenario A — Add an internal…, Scenario B — Navigate to a…, Transition Metadata and Entry Provider Function…, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Implement Navigation is an agent skill from MartinStyk/apk-analyzer. Use when adding a new screen destination to a feature, wiring navigation between screens, implementing an entry provider, or connecting NavKeys. Triggered by phrases like "navigate to", "add screen to feature", "wire navigation", "entry provider", "add destination", "navigate from X to Y".

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering Android development. The repository describes itself as: The most downloaded APK analysis app on Google Play. Detailed reports of every app on your device. No root, no ads, nothing leaves the phone. The licence is GPL-3.0.

When your agent uses it

Adding a new screen destination to a feature
Wiring navigation between screens
Implementing an entry provider
Connecting NavKeys

Example prompts

“navigate to”
“add screen to feature”
“wire navigation”
“/implement-navigation”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Create internal NavKey
Create the screen composable
Register entry in the feature's entry provider
Trigger navigation from source screen
Add API dependency in source feature's build.gradle.kts
Import and use the target NavKey

What it can do on your machine

Read from SKILL.md and the folder at commit d807559. 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 (its code samples are kotlin).
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

Implement Navigation loads about 1.2k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 223 words of instructions outside code blocks.

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

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 MartinStyk/apk-analyzer at commit d807559, republished under its GPL-3.0 licence (© MartinStyk). 223 words, ~1,199 tokens.

Download SKILL.mdSave it as .claude/skills/implement-navigation/SKILL.md (or your agent's skills folder).

name: implement-navigation
description: Use when adding a new screen destination to a feature, wiring navigation between screens, implementing an entry provider, or connecting NavKeys. Triggered by phrases like "navigate to", "add screen to feature", "wire navigation", "entry provider", "add destination", "navigate from X to Y".

Scenario A — Add an internal screen within an existing feature

Internal screens are sub-destinations within a feature (not top-level tabs). Their NavKeys live in feature/<feature>/impl/navigation/.

1. Create internal NavKey

feature/<feature>/impl/src/main/kotlin/.../navigation/<Name>NavKey.kt

Without parameters:

kotlin

package sk.styk.martin.apkanalyzer.feature.<feature>.impl.navigation

import androidx.navigation3.runtime.NavKey
import kotlinx.serialization.Serializable

@Serializable
internal data object <Name>NavKey : NavKey

With parameters:

kotlin

@Serializable
internal data class <Name>NavKey(val id: String) : NavKey

2. Create the screen composable

feature/<feature>/impl/src/main/kotlin/.../<subpackage>/<Name>Screen.kt

kotlin

@Composable
internal fun <Name>Screen(
    onBack: () -> Unit,
) {
    // content
}

3. Register entry in the feature's entry provider

Open the existing <Feature>EntryProvider.kt and add a new entry<> block:

kotlin

entry<<Name>NavKey>(
    metadata = slideFromEndEntryMetadata(),
) {
    <Name>Screen(
        onBack = { navigator.goBack() },
    )
}

With NavKey parameters (access via key lambda argument):

kotlin

entry<<Name>NavKey>(
    metadata = slideFromEndEntryMetadata(),
) { key ->
    <Name>Screen(
        id = key.id,
        onBack = { navigator.goBack() },
    )
}

In the source screen's entry<> block in the entry provider:

kotlin

onNavigateTo<Name> = { navigator.navigate(<Name>NavKey) }
// or with parameters:
onNavigateTo<Name> = { id -> navigator.navigate(<Name>NavKey(id)) }

Scenario B — Navigate to a different feature's screen

Cross-feature navigation uses the target feature's api NavKey.

1. Add API dependency in source feature's `build.gradle.kts`

kotlin

dependencies {
    implementation(projects.feature.<target>.api)
}

2. Import and use the target NavKey

In the source feature's entry provider:

kotlin

import sk.styk.martin.apkanalyzer.feature.<target>.api.<Target>NavKey

// Inside the entry block:
onNavigateToTarget = { navigator.navigate(<Target>NavKey) }

// With parameters (real example):
onAppDetails = { packageName ->
    navigator.navigate(AppDetailNavKey(AppDetailInput.InstalledPackage(packageName)))
}

Transition Metadata

Import from sk.styk.martin.apkanalyzer.core.uilibrary.animation.*

Metadata	Use For
`slideFromEndEntryMetadata()`	Detail screens, drill-down sub-screens
`bottomEntryMetadata()`	Bottom sheets, filter panels, modal screens
(none)	Top-level tab destinations
Custom `NavDisplay.predictivePopTransitionSpec`	Special overlay transitions (e.g., search screen fade)

Custom transition example (search overlay):

kotlin

entry<AppSearchNavKey>(
    metadata = NavDisplay.predictivePopTransitionSpec { _ ->
        EnterTransition.None togetherWith fadeOut(tween(200))
    },
) { ... }

Entry Provider Function Signatures

kotlin

fun EntryProviderScope<NavKey>.<feature>Entries() {
    entry<<Feature>NavKey> {
        <Feature>Screen()
    }
}

kotlin

fun EntryProviderScope<NavKey>.<feature>Entries(navigator: Navigator) {
    entry<<Feature>NavKey> {
        <Feature>Screen(
            onBack = { navigator.goBack() },
        )
    }
}

Multiple internal screens

kotlin

fun EntryProviderScope<NavKey>.<feature>Entries(navigator: Navigator) {
    entry<<Feature>NavKey> {
        <Feature>Screen(
            onBack = { navigator.goBack() },
            onNavigateToDetail = { id -> navigator.navigate(<Detail>NavKey(id)) },
        )
    }

    entry<<Detail>NavKey>(
        metadata = slideFromEndEntryMetadata(),
    ) { key ->
        <Detail>Screen(
            id = key.id,
            onBack = { navigator.goBack() },
        )
    }
}

Wiring Checklist

NavKey created (@Serializable, implements NavKey)
Screen composable created with callback parameters
Entry registered in entry provider with correct transition metadata
Navigation call added in source entry block
For new top-level features: entry provider called in ApkAnalyzerApp.kt
For cross-feature: API module dependency added in build.gradle.kts

Files

Just SKILL.md in .claude/skills/implement-navigation of MartinStyk/apk-analyzer.

Open the folder on GitHubat commit d807559

Compare with similar skills

Implement Navigation 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.

Implement Navigation compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Implement Navigation this skillMartinStyk/apk-analyzer	368	—	~1.2k	Automated safety check: Pass	GPL-3.0	2 days ago
Compose Multiplatform Patternsmonta-app/ocpp-emulator	179	5 repos	~2k	Automated safety check: Pass	Apache-2.0	6 days ago
Kotlin Patternsgetknit/knit	130	5 repos	~4.7k	Automated safety check: Pass	GPL-3.0	2 days ago
Stylesarindamxd/camerax-android	132	4 repos	~2.3k	Automated safety check: Pass	Apache-2.0	5 days ago
Jetpack Compose Expertaldefy/compose-skill	596	—	~4.8k	Automated safety check: Pass	Custom licence	2 mo ago
Verified Emailarindamxd/camerax-android	132	4 repos	~4.7k	Automated safety check: Pass	Apache-2.0	5 days ago

Similar skills

Compose Multiplatform Patterns
monta-app/ocpp-emulator
Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.
179 GitHub starsUsed in 5 repos~2k tokens
MobileAuto-check passed
Kotlin Patterns
getknit/knit
Idiomatic Kotlin patterns, best practices, and conventions for building robust, efficient, and maintainable Kotlin applications with coroutines, null safety, and DSL builders.
130 GitHub starsUsed in 5 repos~4.7k tokens
MobileAuto-check passed
Styles
arindamxd/camerax-android
A skill your agent uses to integrate the Jetpack Compose Styles API into an Android project.
132 GitHub starsUsed in 4 repos~2.3k tokens
MobileAuto-check passed
Jetpack Compose Expert
aldefy/compose-skill
Guides Jetpack Compose and Compose Multiplatform work across Android, Desktop, iOS and web, plus Android TV, Material 3 motion, paging, navigation and design-to-code.
596 GitHub stars~4.8k tokensUpdated 2 mo ago
MobileAuto-check passed
Verified Email
arindamxd/camerax-android
Provides a complete workflow for implementing verified email retrieval on Android Credential Manager API.
132 GitHub starsUsed in 4 repos~4.7k tokens
MobileAuto-check passed
Compose UI
Moustachauve/WLED-Android
Best practices for building UI with Jetpack Compose, focusing on state hoisting, detailed performance optimizations, and theming.
169 GitHub starsUsed in 3 repos~676 tokens
MobileAuto-check passed

Questions about Implement Navigation

What does Implement Navigation do?

A skill your agent uses when adding a new screen destination to a feature, wiring navigation between screens, implementing an entry provider, or connecting NavKeys. Implement Navigation is an agent skill from MartinStyk/apk-analyzer. Use when adding a new screen destination to a feature, wiring navigation between screens, implementing an entry provider, or connecting NavKeys.

When should I use Implement Navigation?

Implement Navigation fits situations like: adding a new screen destination to a feature; wiring navigation between screens; implementing an entry provider; connecting NavKeys.

How do I install Implement Navigation in Claude Code?

Run `npx skills add MartinStyk/apk-analyzer --skill implement-navigation -a claude-code`. Or copy the skill folder (.claude/skills/implement-navigation in MartinStyk/apk-analyzer) into .claude/skills/implement-navigation in your project. Claude Code loads it when a task matches its description.

How do I install Implement Navigation in Codex?

Run `npx skills add MartinStyk/apk-analyzer --skill implement-navigation -a codex`. Or copy the skill folder (.claude/skills/implement-navigation in MartinStyk/apk-analyzer) into .agents/skills/implement-navigation in your project. Codex loads it when a task matches its description.

Can I use Implement Navigation 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 MartinStyk/apk-analyzer --skill implement-navigation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implement-navigation, .gemini/skills/implement-navigation, .github/skills/implement-navigation and .opencode/skills/implement-navigation in your project.

What does Implement Navigation need to run?

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

Does Implement Navigation 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 Implement Navigation 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 Implement Navigation use?

Implement Navigation is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Implement Navigation use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 Implement Navigation?

Skills that share tags, products or a category with Implement Navigation: Compose Multiplatform Patterns (monta-app/ocpp-emulator, 179 stars), Kotlin Patterns (getknit/knit, 130 stars), Styles (arindamxd/camerax-android, 132 stars) and Jetpack Compose Expert (aldefy/compose-skill, 596 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Implement Navigation?

MartinStyk (a GitHub user) maintains it in MartinStyk/apk-analyzer, which has 368 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 5, 2026.

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

Install Implement Navigation

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md