How do I install the Advanced Alchemy CLI skill?

Run npx skillmds@latest add alti3/advanced-alchemy-cli in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Advanced Alchemy CLI safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Advanced Alchemy CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Advanced Alchemy CLI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Advanced Alchemy CLI?

alti3 (@alti3) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Advanced Alchemy CLI by alti3 — Agent Skill

Name: Advanced Alchemy CLI
Author: alti3

Advanced Alchemy CLI

Use Advanced Alchemy's CLI for migrations, revision management, inspection, branching, fixture dumping, and framework CLI integration. Use when setting up or operating Alembic migrations through `alchemy`, `litestar database`, or `flask database`, or when embedding the commands into Click or Typer applications. Do not use for runtime repository or service logic.

alti3 374e29a 2 files · 2.4 KB Updated Sep 17, 2026

File contents

CLI

Execution Workflow

Install the CLI extra when standalone alchemy commands are needed.
Point every command at an explicit dotted config path via --config.
Use init, make-migrations, upgrade, and downgrade as the core lifecycle.
Use inspection commands such as check, heads, history, and show-current-revision in CI or troubleshooting.
Use branch-management and utility commands only when the migration graph actually requires them.

Implementation Rules

Prefer explicit config paths over implicit discovery in automation.
Keep destructive commands such as drop-all behind clear environment guards.
Use check in CI for drift detection before deployments.
Embed the CLI into Click or Typer only when the project already has an application CLI worth extending.

Example Pattern

alchemy init --config path.to.alchemy_config.config
alchemy make-migrations --config path.to.alchemy_config.config -m "add users"
alchemy upgrade --config path.to.alchemy_config.config

Validation Checklist

Confirm the dotted config path imports cleanly in the target environment.
Confirm migration commands operate on the intended database bind.
Confirm CI uses check or revision-inspection commands before deploys.
Confirm destructive or offline SQL modes are only used intentionally.

Cross-Skill Handoffs

Use advanced-alchemy-getting-started if the config object itself is not wired yet.
Use advanced-alchemy-litestar or advanced-alchemy-flask when framework CLIs expose the same migration commands.
Use advanced-alchemy-database-seeding when fixture dumping or loading is part of the operational workflow.

Advanced Alchemy References

---name: advanced-alchemy-clidescription: Use Advanced Alchemy's CLI for migrations, revision management, inspection, branching, fixture dumping, and framework CLI integration. Use when setting up or operating Alembic migrations through `alchemy`, `litestar database`, or `flask database`, or when embedding the commands into Click or Typer applications. Do not use for runtime repository or service logic.---# CLI## Execution Workflow1. Install the CLI extra when standalone `alchemy` commands are needed.2. Point every command at an explicit dotted config path via `--config`.3. Use `init`, `make-migrations`, `upgrade`, and `downgrade` as the core lifecycle.4. Use inspection commands such as `check`, `heads`, `history`, and `show-current-revision` in CI or troubleshooting.5. Use branch-management and utility commands only when the migration graph actually requires them.## Implementation Rules- Prefer explicit config paths over implicit discovery in automation.- Keep destructive commands such as `drop-all` behind clear environment guards.- Use `check` in CI for drift detection before deployments.- Embed the CLI into Click or Typer only when the project already has an application CLI worth extending.## Example Pattern```bashalchemy init --config path.to.alchemy_config.configalchemy make-migrations --config path.to.alchemy_config.config -m "add users"alchemy upgrade --config path.to.alchemy_config.config```## Validation Checklist- Confirm the dotted config path imports cleanly in the target environment.- Confirm migration commands operate on the intended database bind.- Confirm CI uses `check` or revision-inspection commands before deploys.- Confirm destructive or offline SQL modes are only used intentionally.## Cross-Skill Handoffs- Use `advanced-alchemy-getting-started` if the config object itself is not wired yet.- Use `advanced-alchemy-litestar` or `advanced-alchemy-flask` when framework CLIs expose the same migration commands.- Use `advanced-alchemy-database-seeding` when fixture dumping or loading is part of the operational workflow.## Advanced Alchemy References- https://advanced-alchemy.litestar.dev/latest/usage/cli.html- https://docs.advanced-alchemy.litestar.dev/latest/usage/cli.html

Frequently asked questions