Name: gigalixir
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

gigalixir

Gigalixir integration. Manage data, records, and automate workflows. Use when the user wants to interact with Gigalixir data.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/gigalixir/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concrete, actionable integration guide with copy-paste commands and a clear connection/async-state workflow. Its weaknesses are a padded opening that explains concepts Claude already knows and a slightly broken step-numbering scheme (orphan '1b', undefined 'Step 2').

Suggestions

Trim the opening Gigalixir overview paragraph and the 'focus on integration logic rather than auth plumbing' fluff; assume Claude knows what a PaaS is.

Fix the step numbering: rename '1b' to a coherent step and define the referenced 'Step 2' (or remove the dangling 'skip to Step 2' reference).

Merge or differentiate the overlapping 'Searching for actions' and 'Popular actions' sections to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-focused content, but the opening paragraph explains what Gigalixir is ('a PaaS designed for deploying Elixir and Phoenix applications...') and includes fluff like 'so you can focus on the integration logic rather than auth plumbing', fitting 'Mostly efficient but includes some unnecessary explanation.'	3 / 5
Actionability	Copy-paste-ready commands cover install, login, connection ensure, polling, action list/run, and proxy, plus a flags table; examples cover the common cases, matching 'Fully executable; copy-paste ready code or commands.'	5 / 5
Workflow Clarity	There is a clear sequence (install → auth → connect → wait → search → run) with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop (re-poll after user action), but step numbering is broken ('1b' with no '1a', an undefined 'Step 2'), fitting 'Clear sequence with most checkpoints present; minor validation gaps.'	4 / 5
Progressive Disclosure	The single self-contained file is well-organized into clear sections (Overview, Working with Gigalixir, Install, Auth, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references; minor redundancy between 'Searching for actions' and 'Popular actions' keeps it at 'Good structure; minor organization gaps' rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

57%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names a distinct niche (Gigalixir) and includes an explicit 'Use when...' trigger, but the capability phrasing is generic data-management language that does not reflect Gigalixir's actual PaaS functions. It is serviceable but could be tightened with concrete deploy/scale actions.

Suggestions

Replace generic 'Manage data, records, and automate workflows' with concrete Gigalixir actions like 'Deploy, scale, and manage Elixir/Phoenix applications and environment variables'.

Add natural trigger synonyms a user would say, e.g. 'Use when deploying to Gigalixir, scaling Elixir/Phoenix apps, or managing Gigalixir app config'.

Mention the Membrane CLI interaction model briefly so the description reflects how the skill actually operates.

Dimension	Reasoning	Score
Specificity	The domain (Gigalixir) is named, but the listed actions 'Manage data, records, and automate workflows' are generic data-app phrasing rather than concrete PaaS capabilities (deploy, scale, manage apps); this matches the anchor 'Names the domain but actions are minimal or generic.'	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Gigalixir data') are present; the what is somewhat generic so it sits at 'Has both what and when; when could be more specific' rather than a 5.	4 / 5
Trigger Term Quality	'Gigalixir' and 'interact with Gigalixir data' provide a relevant keyword, but common variations a user would actually say (Elixir, Phoenix, deploy) are missing, fitting 'Some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	'Gigalixir integration' names a clear niche with distinct triggers and minimal conflict risk, but the generic 'Manage data, records, and automate workflows' language creates minor overlap risk, matching 'Mostly distinct; minor overlap risk with closely related skills.'	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/gigalixir/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.