Getting Started
Installation
npm install -g homingoPrerequisites
Initialize a Project
homingo initThis creates ~/.homingo/config.json (in your home directory) and scaffolds a skills directory with a sample SKILL.md.
Instant Fleet Health Check
Once you have skills in your skills directory, get an instant health check:
homingo scanScan runs locally in under a second with zero API calls. It analyzes skill overlaps using heuristic scoring and checks for scope overload, giving you:
- A fleet health score (0–100)
- Conflicting skill pairs ranked by severity
- Scope overload warnings
- Clear next steps
Capability Map
To understand how your fleet is organized, generate a capability map:
homingo mapMap runs locally and produces:
- capability clusters
- nearest-neighbor profiles for each skill
- merge candidates and overlap hubs
- handbook-style JSON and HTML output
Deep Diagnostic
When scan surfaces issues, dig deeper with a full routing audit:
homingo auditAudit uses LLM-powered routing simulation. Pair mode tests whether overlapping skills can be distinguished; fleet mode tests those same prompts against the full manifest:
homingo audit --mode fleetThis takes longer but gives more precise conflict and discoverability data.
Pre-Deploy Validation
Before shipping a new or modified skill, lint it:
# Lint the full fleet
homingo lint
# Lint a single skill against its neighbors
homingo lint --skill my-new-skillLint runs adversarial routing tests, detects scope overload, and suggests description rewrites.
What's Next?
- Learn about each command: scan, map, audit, lint, init, logs
- Understand the core concepts: Routing Drift, Shadow Router, Scope Overload, Research Context
- Configure thresholds and output: Configuration
