aramb-metadata

Analyze docker-compose files and codebases to generate or update aramb.toml configuration.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/clode-labs/aramb-skills --skill aramb-metadata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aramb-metadata
Source: https://github.com/clode-labs/aramb-skills/tree/main/aramb-metadata
Command: npx skills add https://github.com/clode-labs/aramb-skills --skill aramb-metadata

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This Skill generates or updates the aramb.toml configuration by analyzing docker-compose files or the project codebase, enabling consistent service definitions and environment setup for aramb-managed deployments.

## Core Features & Use Cases

  • Analyze docker-compose files and code structure to infer services, environment variables, secrets, and installation details.
  • Merge new findings with an existing aramb.toml, preserving uniqueIdentifiers and validating TOML syntax.
  • Produce independent service definitions with proper references and build/runtime separation when applicable.

### Quick Start Use the skill against a repository root to generate aramb.toml. Ensure the APPLICATION_ID environment variable is set and available for all service definitions.

Frequently Asked Questions about aramb-metadata

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

FAQPage Schema
How do I generate an aramb.toml configuration from existing docker-compose files?

To generate an aramb.toml configuration, this skill analyzes your docker-compose files and codebase to infer services, environment variables, and secrets, producing coherent metadata for aramb orchestration. It merges findings with existing files while validating TOML syntax.

Can I merge new service definitions into an existing aramb.toml without losing data?

You can merge new service definitions into an existing aramb.toml without losing data. The skill preserves unique identifiers during the merge process and validates the resulting TOML syntax to ensure configuration integrity.

How do I extract environment variables and secrets from my codebase for aramb deployment?

Extracting environment variables and secrets for aramb deployment is done by analyzing your code structure and docker-compose files. The skill infers these installation details and automatically populates the aramb.toml configuration with the required environment setup.

Does aramb-metadata support separate build and runtime configurations for services?

aramb-metadata supports separate build and runtime configurations. It produces independent service definitions with proper references, adhering to dependency rules while maintaining build and runtime separation when applicable for aramb-managed deployments.

What environment setup is required before generating aramb.toml metadata?

Before generating aramb.toml metadata, ensure the APPLICATION_ID environment variable is set and available for all service definitions. Run the skill against your repository root to analyze the project codebase and docker-compose files.

Why are my aramb service definitions failing dependency validation?

Aramb service definitions fail dependency validation when the generated configuration lacks proper references or violates security rules. The skill enforces dependency rules and validates TOML syntax to ensure independent service definitions remain coherent across backend, frontend, and database services.