CtrlK
BlogDocsLog inGet started
Tessl Logo

igmarin/elixir-phoenix-skills

Curated library of 38 atomic skills, 7 personas, and 1 orchestrator for Elixir and Phoenix development. Organized by category: fundamentals, phoenix, database, testing, auth, infrastructure, quality, security, integrations, tooling, frameworks, personas, and orchestration. Covers core Elixir patterns, Phoenix LiveView, Ecto, OTP, Oban, testing, security, deployment, real-time, and modern tooling (Req, Swoosh, Cachex, Broadway, Ash).

91

1.37x
Quality

91%

Does it follow best practices?

Impact

91%

1.37x

Average score across 56 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

criteria.jsonevals/scenario-39/

{
  "context": "Checks whether the final artifact follows the elixir-skill-router instructions from the published Elixir Phoenix Skills plugin.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "instruction-1",
      "description": "The submitted artifact follows this skill instruction: Triages and decomposes any Elixir/Phoenix request into ordered sub-tasks, then delegates to the correct specialized skill. Identify the matching skill from the catalog below and route to it using the format defined in **Output Style**.",
      "max_score": 10
    },
    {
      "name": "instruction-2",
      "description": "The submitted artifact follows this skill instruction: Priority: TDD → Planning → Implementation → Quality → Review.",
      "max_score": 10
    },
    {
      "name": "instruction-3",
      "description": "The submitted artifact follows this skill instruction: **Example 1 — \"I need to add user notifications to my Phoenix app. Users should receive an email when a job completes, and I want a live counter on the dashboard.\"**",
      "max_score": 10
    },
    {
      "name": "instruction-4",
      "description": "The submitted artifact follows this skill instruction: **Routing statement (required on every response):** The routing statement MUST be the first substantive line of every response, before any analysis or implementation.",
      "max_score": 10
    },
    {
      "name": "instruction-5",
      "description": "The submitted artifact follows this skill instruction: **Language**: Generated artifacts and output MUST be in English unless explicitly requested otherwise.",
      "max_score": 10
    },
    {
      "name": "instruction-6",
      "description": "The submitted artifact follows this skill instruction: **Do not invoke this skill** for simple, single-concern requests that clearly map to one skill (e.g., \"write a test for this function\" → use `testing-essentials` directly)",
      "max_score": 10
    },
    {
      "name": "instruction-7",
      "description": "The submitted artifact follows this skill instruction: **Do not invoke this skill** if the request is a direct question about Elixir syntax or Phoenix patterns — route to the specific skill instead",
      "max_score": 10
    },
    {
      "name": "instruction-8",
      "description": "The submitted artifact follows this skill instruction: **Do not invoke this skill** if you already know all the skills needed and just need implementation guidance — use the specific skill directly",
      "max_score": 10
    },
    {
      "name": "instruction-9",
      "description": "The submitted artifact follows this skill instruction: **Do not route through this skill** when the user explicitly names a target skill (e.g., \"use the oban-essentials skill\")",
      "max_score": 10
    },
    {
      "name": "instruction-10",
      "description": "The submitted artifact follows this skill instruction: **Use `elixir-essentials` alone** if you only need Elixir language guidance without orchestration.",
      "max_score": 10
    }
  ]
}

evals

.mcp.json

README.md

tile.json