search-overview

Consolidate Android search across apps, files, contacts, and web into one interface.

49|3|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/mrndstvndv/Search --skill search-overview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: search-overview
Source: https://github.com/mrndstvndv/Search/tree/main/.opencode/skill/search-overview
Command: npx skills add https://github.com/mrndstvndv/Search --skill search-overview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Android fragmentation leads to scattered search experiences across apps, files, and contacts. This Skill provides a single, launcher-style interface to access them all quickly and consistently.

Core Features & Use Cases

  • Unified search across apps, files, contacts, web engines, settings, calculator, and Termux.
  • Provider-based architecture enabling easy extension and customization.
  • Clear, MVVM-style structure with dedicated entry points for quick navigation.
  • Use Case: Type a query to launch an app, locate a local file, or query the web from one overlay.

Quick Start

Open the app and begin typing to access apps, files, contacts, and web results instantly.

Frequently Asked Questions about search-overview

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

FAQPage Schema
How do I create a unified Android search interface across apps, files, and contacts?

You can build a unified Android search interface using a provider-based architecture with Kotlin and Compose, consolidating apps, files, contacts, and web results into a single launcher-style UI. This modular approach enables quick navigation and consistent local content discovery.

How does a provider-based architecture work for Android launcher search?

A provider-based architecture works by assigning modular entry points to each search domain, such as apps, settings, or tools. This structure allows you to independently extend and customize specific search providers within your Kotlin and Compose application.

Can I use Kotlin and Compose to build a single search overlay for Android settings and Termux?

Yes, Kotlin and Compose can build a single search overlay for Android settings and Termux. The implementation uses an MVVM-style structure with dedicated entry points to query multiple utilities and system tools from one interface.

What is the best way to implement local content discovery in an Android search app?

The best way to implement local content discovery is by consolidating multiple search providers into one interface. Using a launcher-style UI with Kotlin and Compose allows users to instantly locate local files and contacts by typing a query.

How do I add a new search provider to an existing Android search application?

You add a new search provider by leveraging the modular entry points in the provider-based architecture. This design enables easy extension, allowing you to integrate new search domains like web engines or calculators without disrupting the existing Compose UI.