Ecto Migrator
v1.0.0Generate Ecto migrations from natural language or schema descriptions. Handles tables, columns, indexes, constraints, references, enums, and partitioning. Supports reversible migrations, data migrations, and multi-tenant patterns. Use when creating or modifying database schemas, adding indexes, altering tables, creating enums, or performing data migrations in an Elixir project.
⭐ 1· 1.7k·2 current·2 all-time
by@gchapim
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Ecto migrations) match the content of SKILL.md and the provided references. The skill does not request unrelated binaries, credentials, or config paths — everything is appropriate for a migration-generation helper.
Instruction Scope
SKILL.md contains templates, patterns, and concrete migration snippets (indexes, constraints, multi-tenant patterns, data-migration guidance). It does not instruct the agent to read arbitrary local files, access environment variables, or send data to external endpoints. It also does not instruct the agent to execute migrations against a database (only shows mix/execute examples), so runtime scope is limited to generating code/text.
Install Mechanism
No install spec and no code files that run on the host. As an instruction-only skill, it does not download or write executables to disk — lowest-risk install profile.
Credentials
The skill declares no required environment variables, credentials, or config paths. That is proportionate: generating migration text does not require secrets or external service access.
Persistence & Privilege
always is false and the skill does not request persistent presence or modify other skills. Autonomous invocation is allowed (platform default) but the skill's content does not raise additional privilege concerns.
Assessment
This skill is coherent and appears safe as an authoring helper, but remember: generated migrations change your database schema. Always review generated migration code before running it, run migrations in a development/staging environment first, take backups, and ensure patterns (primary key type, tenant_id decisions, concurrent index flags, data-migration strategies) match your application's conventions. Because the skill is instruction-only, installing it does not add code to your system, but do not apply generated SQL/migrations without standard code review and testing.Like a lobster shell, security has layers — review code before you run it.
latestvk977h8xz1tqns2158p14zrkdm980fshq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.