using-omni-link

Scan repositories to build an ecosystem graph and detect contract mismatches.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Sebdysart/omni-link-hustlexp --skill using-omni-link
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-omni-link
Source: https://github.com/Sebdysart/omni-link-hustlexp/tree/main/skills/using-omni-link
Command: npx skills add https://github.com/Sebdysart/omni-link-hustlexp --skill using-omni-link

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a unified control plane for managing complex, multi-repository software projects, ensuring consistency, detecting drift, and enforcing development best practices across an entire ecosystem.

Core Features & Use Cases

  • Ecosystem Grounding: Understand the current state of all scanned repositories, including contract statuses and recent changes.
  • Cross-Repo Impact Analysis: Predict the ripple effects of proposed changes across different services or modules before implementation.
  • Automated Verification: Enforce coding standards, prevent hallucinations, and ensure adherence to API contracts.
  • Use Case: Before refactoring a shared API endpoint, use cross-repo-impact to identify all consumers that will be affected, then use anti-slop-gate to ensure the new implementation adheres to all established contracts and conventions.

Quick Start

Use the using-omni-link skill to ground yourself in the ecosystem state before starting work.

Frequently Asked Questions about using-omni-link

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

FAQPage Schema
How do I analyze cross-repo impact before refactoring a shared API?

Multi-repo ecosystem management scans repositories to build an ecosystem graph containing API bridges, type lineage, and contract mismatches. It enforces development laws by verifying imports against manifests and preventing hallucinated dependencies across repositories.

How do I prevent hallucinated imports across multiple repositories?

API governance in a multi-repo ecosystem injects a digest of contract mismatches and type lineage into the development workflow. It enforces coding standards and verifies implementations against manifests to prevent drift across repositories.

What is the best way to detect contract mismatches across microservices?

Contract verification scans repositories to build an ecosystem graph that detects API contract mismatches and drift across services. It provides a unified control plane to ensure consistency and enforce development best practices across the entire ecosystem.

Can I predict the ripple effects of proposed changes across different modules?

Ecosystem management enforces iron laws for development by verifying against manifests, preventing hallucinated imports, and injecting digests of API bridges and contract mismatches. It ensures consistency and detects drift across all scanned repositories.

Does multi-repo ecosystem management work without external dependencies?

Contract verification in a multi-repo ecosystem detects drift and mismatches by scanning repositories and building an ecosystem graph of API bridges and type lineage. It enforces coding standards and prevents hallucinated imports across all services.