Alembic
CheckedAlembic allows you to quickly convert data between different database formats (like SQL and JSON) for seamless integration and migration.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add manutej/luxor-claude-marketplace --skill alembic -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
manutej
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned manutej/luxor-claude-marketplace at 1861cc9720.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1861cc9720
- Scanned
- 4 files, 3,753 lines
About this skill
What it does
This skill, Alembic, provides a way to manage changes to your database schema over time using version-controlled migration scripts and SQLAlchemy. It's specifically designed for customer support systems to track all schema modifications, ensure reproducibility across environments (development, staging, production), and enable safe rollbacks if issues arise. The tool facilitates team collaboration on database schema changes while preserving data integrity during transformations.
When to use it
- Managing database schema updates in a customer support system.
- Ensuring consistent database structure across development, testing, and production environments.
- Implementing a controlled process for applying and reverting database migrations.
- Collaborating with other developers on database schema changes.
Key capabilities
- Version Control: Tracks all database schema changes.
- Reproducibility: Applies the same migrations across different environments.
- Rollback Capability: Allows safe reversion of problematic changes.
- Team Collaboration: Enables merging of schema changes from multiple developers.
- Data Preservation: Migrates data during schema transformations.
- Automated Migration Script Generation: (Implied - through SQLAlchemy integration)
Example prompts
While this skill doesn't directly respond to natural language prompts, a user might use it in conjunction with an AI agent by requesting:
- "Generate a new Alembic migration script for adding a 'customer_id' column to the 'tickets' table."
- "Review the latest Alembic migration scripts before deployment."
- "Apply the pending database migrations to the staging environment."
Tips & gotchas
- Prerequisites: Requires Python, SQLAlchemy, and
psycopg2-binary(for PostgreSQL). - Configuration: The
alembic.inifile needs to be configured with the correct database URL, ideally using environment variables for production environments. - Environment Variables: Using environment variables in
env.pyis recommended for managing sensitive database connection information.