services-inventory

Discovers and catalogs microservices with metadata and dependency maps.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Muath2000/TradeStation --skill services-inventory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: services-inventory
Source: https://github.com/Muath2000/TradeStation/tree/main/.claude/skills/services-inventory
Command: npx skills add https://github.com/Muath2000/TradeStation --skill services-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the discovery, cataloging, and documentation of all microservices within a codebase, providing a clear and comprehensive overview of your system's architecture.

Core Features & Use Cases

  • Service Discovery: Identifies all microservices, including shared libraries and tools.
  • Metadata Cataloging: Documents service identity, version, ownership, tech stack, dependencies, and folder structure.
  • Dependency Mapping: Generates visual ASCII diagrams and matrices of inter-service relationships.
  • Use Case: Onboarding a new engineer to a complex microservice architecture. This Skill provides them with an immediate, detailed map of all services, how they connect, and who owns what, drastically reducing ramp-up time.

Quick Start

Use the services-inventory skill to discover all services and generate a dependency map.

Frequently Asked Questions about services-inventory

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

FAQPage Schema
How do I discover and catalog all microservices in a codebase?

To catalog microservices in a codebase, you can automate service discovery to identify all services, shared libraries, and tools. This process documents service identity, version, ownership, tech stack, dependencies, and folder structure.

What is the best way to map dependencies between microservices?

Mapping microservices dependencies involves generating visual ASCII diagrams and matrices of inter-service relationships. This provides a comprehensive overview of your system architecture and how services connect.

How do I document a microservice architecture for new engineer onboarding?

Documenting a microservice architecture for onboarding involves generating service catalogs and executive one-pagers. These artifacts detail ownership, tech stacks, and folder structures to drastically reduce ramp-up time.

Can I audit the tech stack and ownership of multiple microservices automatically?

Yes, you can audit microservice tech stacks and ownership automatically through exhaustive codebase discovery. This evidence-based reporting ensures accurate metadata cataloging for all identified services and shared libraries.

Does microservice codebase analysis require evidence-based reporting for accuracy?

Microservice codebase analysis requires exhaustive discovery and evidence-based reporting to guarantee accuracy. This ensures the generated service catalogs, dependency maps, and executive one-pagers reflect the true system architecture.