Skip to content
TrustedSkillsbeta
Back to all skills

Ecto Constraint Debug

Checked
oliver-kriska·vlatest·testing·MIT

Identifies and resolves unexpected constraints during automated tests, improving reliability and pinpointing root causes quickly.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add oliver-kriska/claude-elixir-phoenix --skill ecto-constraint-debug -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

oliver-kriska

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 oliver-kriska/claude-elixir-phoenix at 19791bb7dc.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
19791bb7dc
Manifest
targets/pi/skills/ecto-constraint-debug/SKILL.md
Scanned
6 files, 759 lines
Copies in repo
3 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows an AI agent to debug Ecto constraint issues within Elixir and Phoenix applications. It helps identify the root cause of validation errors, incorrect data types, or other constraint violations that prevent database operations from succeeding. The agent can analyze error messages and suggest fixes based on Ecto's schema definitions.

When to use it

  • When encountering cryptic "constraint violation" errors in your Phoenix application’s database interactions.
  • During development when rapidly iterating on data models and needing quick feedback on constraint correctness.
  • To assist junior developers or those less familiar with Ecto's schema validation process.
  • For automated testing of data integrity by simulating invalid inputs and verifying error handling.

Key capabilities

  • Error message analysis
  • Schema definition interpretation
  • Constraint violation identification
  • Fix suggestion

Example prompts

  • "I'm getting a constraint violation error: 'email cannot be blank'. What does my schema say about the email field?"
  • "My Ecto schema for User has a validation that age must be greater than 18. How can I test this constraint?"
  • "The database operation failed with an error related to uniqueness constraints. Can you help me understand which fields are involved and why the conflict occurred?"

Tips & gotchas

This skill requires access to your Elixir/Phoenix project's schema definitions (e.g., lib/your_app/repo.ex). Ensure the AI agent has sufficient context about your application’s data models for accurate analysis and suggestions.