tgdb-add-app

Integrate containerized projects into TGDB with configuration artifacts and validation.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/tgdb77/tgdb --skill tgdb-add-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tgdb-add-app
Source: https://github.com/tgdb77/tgdb/tree/main/skills/tgdb-add-app
Command: npx skills add https://github.com/tgdb77/tgdb --skill tgdb-add-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TGDB users need a consistent, low-risk way to integrate a new containerized project into TGDB, while choosing the correct integration path (AppSpec vs advanced module) and ensuring rootless/rootful compatibility.

Core Features & Use Cases

  • Integration route decision (AppSpec vs advanced app): Determines whether the project fits TGDB AppSpec (menu 6) or should be implemented as an advanced application (menu 7) based on operational complexity and maintainability.
  • Rootless vs rootful deployment planning: Recommends default and compatibility settings using explicit rules for host networking, privileged mounts, low ports, and sensitive host resources.
  • Upstream-to-TGDB specification mapping: Extracts required deployment information (image/tag or build instructions, ports, env vars, volumes, init/migrate/seed needs) and turns it into TGDB-ready artifacts.
  • Implementation guidance + smoke-test verification: Produces concrete file changes (app.spec, quadlet units, env/config templates, optional build scripts) and runs validation checks to ensure the app is discoverable and renderable.

Quick Start

Ask: "Evaluate this project for TGDB integration and implement the necessary TGDB files and validation for it."

Frequently Asked Questions about tgdb-add-app

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

FAQPage Schema
How do I integrate a new containerized app into TGDB using Podman quadlet units?

To integrate a containerized app into TGDB, you extract upstream deployment data like ports and volumes, then generate TGDB-ready artifacts including app.spec files and Podman quadlet units. This process ensures correct rootless deployment and maintainability.

When should I choose TGDB AppSpec versus an advanced app module for deployment?

Choose TGDB AppSpec for standard integrations with lower operational complexity, and select the advanced app module when the deployment requires custom handling. The decision is based on maintainability and the specific deployment constraints of the containerized project.

How does rootless Podman deployment planning handle host networking and privileged mounts?

Rootless deployment planning applies conservative safety defaults by using explicit rules to restrict host networking, privileged mounts, low ports, and sensitive host resources. This ensures the containerized application operates securely without unnecessary rootful access.

What deployment information do I need to extract from an upstream repo for TGDB integration?

You must extract the container image tag or build instructions, required ports, environment variables, volume mounts, and any initialization, migration, or seeding needs. This information is mapped into TGDB-ready configuration artifacts for deployment.

Can I validate TGDB app integration and quadlet rendering before final deployment?

Yes, you can validate TGDB app integration by running smoke-test style validation checks. These checks ensure the newly integrated application is fully discoverable within the system and that the Podman quadlet units render correctly.