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

alchemer

Alchemer integration. Manage data, records, and automate workflows. Use when the user wants to interact with Alchemer 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/alchemer/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 CLI commands and a well-validated connection workflow, but it carries some padding (the empty-description actions table and the platform intro) and has no progressive file structure to offload reference material.

Suggestions

Trim the introductory 'Alchemer is a survey and data collection platform...' paragraph or fold it into one line, since Claude can infer the platform's purpose.

Move the 20-row 'Popular actions' table (all 'No description') into a references file and keep only a few key examples inline, or drop the empty Description column.

Label the post-connection section as 'Step 2' explicitly (or remove the 'skip to Step 2' reference) so the workflow numbering is internally consistent.

Dimension	Reasoning	Score
Conciseness	Most sections are efficient with copy-paste commands, but the introductory paragraph explaining what Alchemer is and the 20-row 'Popular actions' table where every row says 'No description' add padding that could be trimmed, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	The body is dominated by fully executable, copy-paste-ready commands (install, login, connection ensure, action list, action run, request) with concrete flag tables and JSON examples covering the common cases, matching the top anchor.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but the loose 'skip to Step 2' reference (with no labelled Step 2) is a minor sequencing gap that keeps it below 5.	4 / 5
Progressive Disclosure	No bundle files exist, so the single SKILL.md carries everything; it is well-organized into clear sections with one external docs link and no nested references, though the bulk 'Popular actions' table is reference-style content that could live in a separate file, a minor organization gap.	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 is third-person, names the platform, and covers both what and when, but its actions are generic and its trigger terms miss the natural survey/form/feedback vocabulary a user would actually say.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions like 'create and list surveys, manage contacts and contact lists, fetch survey responses'.

Expand the 'Use when' clause with natural trigger terms: surveys, forms, questionnaires, survey responses, contact lists.

Add file-format or object hints (e.g. survey questions, email campaigns) to sharpen distinctiveness from generic data tools.

Dimension	Reasoning	Score
Specificity	Names the Alchemer domain and a few action-like phrases ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete operations, so it sits at the '1-2 concrete actions, not comprehensive' anchor rather than the detailed list of score 4.	3 / 5
Completeness	It states both what ('Alchemer integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Alchemer data'), but the 'when' trigger is generic rather than listing concrete trigger phrases, so it does not reach the explicit-anchor level of 5.	4 / 5
Trigger Term Quality	The phrase 'Use when the user wants to interact with Alchemer data' includes the core keyword 'Alchemer' but omits natural synonyms users would actually say (surveys, forms, questionnaires, feedback), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named platform 'Alchemer' gives it a clear, mostly-distinct niche with only minor overlap risk against other data/survey integrations; it is not generic enough to score 3 nor fully trigger-precise enough for 5.	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/alchemer/SKILL.md
Commit: f484c82

Reviewed: 3 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.