discovery

Locate and aggregate commands from multiple sources with precedence and collision detection.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/invowk/invowk --skill discovery-invowk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discovery
Source: https://github.com/invowk/invowk/tree/main/.claude/skills/discovery
Command: npx skills add https://github.com/invowk/invowk --skill discovery-invowk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locates and aggregates commands from multiple sources with clear precedence rules and collision detection to support reliable, transparent command namespaces.

Core Features & Use Cases

  • Discovery precedence: a strict 4-level order guiding how current directory, local modules, user commands, and config paths contribute commands, with shadowing rules for non-module sources and inclusion for modules.
  • Module awareness: loads and prefixes module commands, detects collisions, and supports aliases for disambiguation.
  • Source tracking: maintains metadata about where each command originated and how sources interact.

Quick Start

Modify the discovery rules in the codebase to observe the four-level precedence and collision handling.

Frequently Asked Questions about discovery

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

FAQPage Schema
How do I resolve command collisions across multiple modules and search paths?

Command collisions across modules and search paths are resolved using a strict 4-level precedence order. This discovery process prioritizes the current directory, local modules, user commands, and config paths, applying shadowing rules for non-module sources while including module commands transparently.

What is the precedence order for discovering commands from different sources?

Command discovery follows a strict 4-level precedence order: current directory, local modules, user commands, and configured search paths. Non-module sources are subject to shadowing rules, while module commands are included and prefixed to maintain transparent namespace isolation.

How do I debug command resolution logic when local modules shadow user commands?

Debugging command resolution logic involves analyzing the two-track discovery process with source tracking. You can observe the four-level precedence and collision handling by modifying discovery rules in the codebase to see how non-module sources shadow commands and how modules interact.

Does command discovery support aliases for disambiguating module namespace collisions?

Yes, command discovery supports aliases for disambiguating module namespace collisions. The module awareness feature loads and prefixes module commands, detects collisions automatically, and allows aliases to resolve naming conflicts across the current directory, sibling modules, and configured search paths.

When should I implement a two-track discovery process for command aggregation?

A two-track discovery process for command aggregation is needed when building or debugging internal discovery logic and module resolution. It is essential when you must disambiguate command namespaces across the current directory, sibling modules, user commands, and configured search paths with collision detection.