Name: apex-27
Rating: 59.2 (1 reviews)
Author: membranedev

apex-27

Apex 27 integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Apex 27 data.

Quality

69%

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/apex-27/SKILL.md

Quality

Content

63%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 highly actionable with executable CLI commands and a clear connection-state workflow, but is dragged down by a dead opening placeholder, repeated empty action descriptions, and an inlined actions table that should be split into a reference file.

Suggestions

Remove the 'I don't have enough information about Apex 27 to provide a description' placeholder and the unrelated Salesforce Apex docs link.

Move the 20-row actions table into a references file (e.g. references/actions.md) and link to it from the body, capturing real descriptions where available.

Add an explicit validation step after `membrane action run` (e.g. check the `output` field and handle error states) to close the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with code blocks, but the opening 'I don't have enough information about Apex 27 to provide a description' placeholder and a 20-row actions table repeatedly reading 'No description' are unnecessary padding that should be trimmed.	3 / 5
Actionability	Provides concrete, executable commands for install, login, connection, action listing/running, and proxying with documented flags, with only minor gaps from the 'No description' action rows.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with a state machine and explicit polling/feedback (CLIENT_ACTION_REQUIRED -> poll again), but the action-run path lacks an explicit validation checkpoint on outputs, leaving a minor gap.	4 / 5
Progressive Disclosure	Section headers give it structure, but with no bundle files and a large inlined actions table that belongs in a separate reference, organization is only adequate and references are not clearly signaled.	3 / 5
	Total	14 / 20 Passed

Description

75%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 concise, third-person, and clearly answers both what the skill does and when to use it, with concrete named entities. Its main weakness is a somewhat broad 'when' trigger that could enumerate more specific use cases.

Suggestions

Sharpen the 'when' clause with concrete trigger phrases (e.g. 'Use when listing contacts, leads, or listings, or when creating notes and call logs in Apex 27').

Frame the managed items as verbs/actions (e.g. 'list, create, and update Organizations, Pipelines, Users') to lift specificity toward 5.

Add a common synonym or file/context cue (e.g. CRM, estate-agency) to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Apex 27 domain and lists several concrete entities to manage ('Organizations, Pipelines, Users, Goals, Filters'), matching the 'several specific actions; minor gaps' anchor; not 3 because more than 1-2 items, not 5 because these are objects rather than a comprehensive set of distinct actions.	4 / 5
Completeness	Has a clear 'what' (manage the listed entities) and an explicit 'when' clause, but the trigger is broad ('interact with Apex 27 data') and could be more specific, fitting the 'both present, when could be more explicit' anchor.	4 / 5
Trigger Term Quality	Includes the domain name plus a natural 'Use when the user wants to interact with Apex 27 data' trigger and a spread of entity keywords; good coverage with a few natural terms missing, so above the midpoint but short of comprehensive synonyms.	4 / 5
Distinctiveness Conflict Risk	'Apex 27' is a distinct named niche with entity-specific triggers, so conflict risk is low; not 5 because the generic 'interact with data' phrasing leaves minor overlap potential with other CRM/data skills.	4 / 5
	Total	16 / 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/apex-27/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.