Skip to content
TrustedSkillsbeta
Back to all skills

Elixir Tdd

Checked
hwatkins·vlatest·backend·MIT

Elixir TDD helps developers write robust Elixir code by automating test creation and execution, boosting confidence & reducing bugs.

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 hwatkins/my-skills --skill elixir-tdd -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

hwatkins

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 hwatkins/my-skills at d245c4fdd3.

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

Scanned
1 file, 433 lines
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 AI agents to write and execute test-driven development (TDD) code in Elixir. It facilitates creating automated tests before writing the actual implementation, ensuring a robust and well-tested codebase. The agent can generate tests based on provided specifications or existing code.

When to use it

  • Generating unit tests for new Elixir modules or functions.
  • Refactoring existing Elixir code by first writing tests to verify behavior.
  • Creating integration tests to ensure different parts of an Elixir application work together correctly.
  • Automating the testing process during development cycles.

Key capabilities

  • Test generation based on specifications.
  • Execution of Elixir unit tests.
  • Integration with Elixir's testing framework (ExUnit).
  • Code refactoring guided by existing test suite.

Example prompts

  • "Write a TDD test for a function that calculates the factorial of a number."
  • "Generate ExUnit tests for this Elixir module: [module code]"
  • “Refactor this Elixir code, ensuring all functionality is preserved by running existing tests.”

Tips & gotchas

  • Requires familiarity with Elixir and TDD principles.
  • The quality of generated tests depends on the clarity and completeness of provided specifications.