kotlin-platform-app-links-and-deep-links

Evaluate Android deep links and App Links in Kotlin Multiplatform projects.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/leogallego/ansible-jane --skill kotlin-platform-app-links-and-deep-links-leogallego
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kotlin-platform-app-links-and-deep-links
Source: https://github.com/leogallego/ansible-jane/tree/main/skills/kotlin-platform-app-links-and-deep-links
Command: npx skills add https://github.com/leogallego/ansible-jane --skill kotlin-platform-app-links-and-deep-links-leogallego

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines designing, implementing, and reviewing Android deep links, web links, and App Links in Kotlin Multiplatform projects, ensuring reliable entry points and correct ownership verification.

Core Features & Use Cases

  • Distinguish and validate deep links, App Links, and web links in Android manifests.
  • Review manifest intent-filters, host scope, and path matching to prevent accidental URL handling conflicts.
  • Assess App Link verification models, assetlinks.json correctness, and multi-host scenarios for robust ownership guarantees.
  • Clarify the shared-vs-platform boundary to keep Android-specific registration separate from shared navigation logic.
  • Provide actionable diagnostics and testing guidance for real-device validation.

Quick Start

Audit your Kotlin Multiplatform Android deep-link setup and implement the recommended manifest, verification, and routing updates.

Frequently Asked Questions about kotlin-platform-app-links-and-deep-links

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the difference between deep links, web links, and App Links in Android?

App Links require verified HTTP/HTTPS ownership using assetlinks.json, while deep links use custom URI schemes and web links lack verification. This Skill evaluates your manifest intent-filters to distinguish them and prevent accidental URL handling conflicts in Kotlin Multiplatform projects.

How do I verify App Links and configure assetlinks.json for multiple hosts in Kotlin Multiplatform?

Verifying App Links requires publishing a correct assetlinks.json file for each host. This Skill assesses your verification models, assetlinks.json accuracy, and multi-host scenarios to guarantee robust domain ownership across your Android and shared code.

How do I separate Android manifest deep link registration from shared navigation logic in KMP?

Separate platform-specific registration from shared routing by keeping intent-filters and host scope in the Android manifest while routing logic stays in shared code. This Skill clarifies the shared-vs-platform boundary to maintain clean cross-platform routing.

Why are my Android App Links not working and how do I test them on a real device?

App Links fail when manifest intent-filters, host scope, or assetlinks.json verification are incorrect. This Skill provides actionable diagnostics and testing guidance to validate path matching and verification workflows on real Android devices.

Does this approach work for Kotlin Multiplatform projects with cross-platform routing considerations?

Yes, this approach evaluates navigation entry points and back-stack behavior specifically for Kotlin Multiplatform. It ensures correct intent-filters and host verification while maintaining a clear separation between Android registration and shared routing.