Name: fixer
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

fixer

Fixer integration. Manage Organizations, Users. Use when the user wants to interact with Fixer data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/fixer/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 content is highly actionable with executable Membrane CLI commands and a clear connection state-check workflow, but it is held back by unnecessary prose, a junk placeholder section, and slightly confusing step labeling.

Suggestions

Remove the marketing prose and the placeholder '## Fixer Overview' (Task/Job/Fix) section to tighten conciseness.

Fix the step numbering (define 'Step 2', relabel '1b' to a coherent 1/2/3 sequence) so the connection workflow is unambiguous.

Add a validation/checkpoint note for destructive proxy requests (POST/PUT/DELETE), e.g. confirming the path and method before sending.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands, but it includes unnecessary intro prose ('reliable and accurate data for converting currencies'), marketing-style fluff ('so you can focus on the integration logic rather than auth plumbing'), and a junk placeholder section ('Task / Job / Fix'), matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests, plus a popular-actions table and proxy-flag table that cover the common cases, matching the top anchor.	5 / 5
Workflow Clarity	The connection workflow has a clear state-check sequence with a re-poll feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but step labels are confusing ('1b' with no 1a, undefined 'Step 2') and destructive proxy verbs (POST/PUT/DELETE) lack validation checkpoints, so it sits just below level 5.	4 / 5
Progressive Disclosure	With no bundle directories present, the skill is a single well-organized file with clear headers and no nested references; it is slightly long for one file (~145 lines) but coherently sectioned, matching 'good structure; most content appropriately placed'.	4 / 5
	Total	16 / 20 Passed

Description

62%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 includes an explicit 'Use when...' trigger and names the Fixer domain, giving it solid completeness and distinctiveness, but it is generic in its action verbs ('Manage') and missing the natural currency/exchange-rate keywords users would say.

Suggestions

Replace the generic 'Manage Organizations, Users' with the concrete Fixer capabilities, e.g. 'Get latest and historical exchange rates, convert currencies, retrieve supported symbols'.

Add natural trigger terms users actually say, such as 'exchange rates', 'currency conversion', or 'FX rates', to the 'Use when...' clause.

Resolve the mismatch between the description ('Manage Organizations, Users') and the body (currency exchange) so the description accurately reflects what the skill does.

Dimension	Reasoning	Score
Specificity	Names the Fixer domain and two concrete objects ('Organizations, Users'), but the verb 'Manage' is generic and coverage is not comprehensive, fitting the 'names domain and 1-2 concrete actions' anchor rather than the more specific level 4.	3 / 5
Completeness	Both a 'what' ('Manage Organizations, Users') and an explicit 'when' ('Use when the user wants to interact with Fixer data') are present, but the 'when' could be more specific, landing on the level-4 anchor rather than the fully explicit level 5.	4 / 5
Trigger Term Quality	It includes the product keyword 'Fixer' and a 'Use when...interact with Fixer data' trigger, but omits the natural synonyms users would actually say ('exchange rates', 'currency conversion'), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'Fixer' brand anchors a clear niche with minimal conflict risk, though the generic 'Manage Organizations, Users' phrasing creates minor overlap with other admin-style skills, matching 'mostly distinct; minor overlap risk'.	4 / 5
	Total	14 / 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/fixer/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.