Name: engageats
Rating: 60.8 (1 reviews)
Author: membranedev

engageats

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

Quality

71%

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

Quality

Content

76%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 concrete, executable CLI commands and a well-validated connection workflow. It loses points for lacking validation feedback loops around destructive action/proxy operations and for inlining reference-like detail rather than splitting it out.

Suggestions

Add a validation/checkpoint step before destructive or batch operations, e.g. a dry-run or confirm prompt before `membrane action run` with mutating intents or proxy requests using DELETE/PUT.

Move the clientAction field reference and the proxy flag table into a separate references file (e.g. REFERENCE.md) and link to it from the body to deepen progressive disclosure.

Trim the opening 'what is an ATS' paragraph since Claude already understands the domain.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with flags, but retains minor over-explanation such as the opening definition of what an ATS is and the descriptive clientAction field prose; not a 5 because those tokens could be trimmed, not a 3 because the bulk is efficient.	4 / 5
Actionability	Provides copy-paste-ready bash commands for install, auth, connection, action discovery, action runs, and proxy requests, with concrete flags and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The connection setup flow has a clear sequence with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll loop, but destructive or batch operations (action run, proxy with DELETE/PUT) lack validation/verification feedback loops, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Single well-organized file with clear section headers and no nested references; good structure overall, though it exceeds 50 lines and inlines content (clientAction field reference, proxy flag table) that could live in separate files, keeping it just below a 5.	4 / 5
	Total	16 / 20 Passed

Description

66%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 cleanly states what the skill does and when to use it, anchored to a distinct product name. Its main weakness is generic action language and limited trigger-term coverage.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete ATS operations such as 'search candidates, update job postings, and track applications'.

Broaden trigger terms to include natural phrases users say, e.g. 'Use when the user wants to query candidates, manage job postings, or automate EngageATS hiring workflows.'

Dimension	Reasoning	Score
Specificity	Names the EngageATS domain plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete ATS-specific operations, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor; not a 2 because multiple actions are listed, not a 4 because none are specific.	3 / 5
Completeness	Both 'what' ('EngageATS integration. Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with EngageATS data') are present and explicit; not a 5 because the 'what' is generic and the 'when' trigger is narrow.	4 / 5
Trigger Term Quality	The trigger relies on the single term 'EngageATS' plus 'data', which are relevant but missing common variations, synonyms, or file extensions; not a 4 because keyword coverage is thin rather than just 'a few natural terms missing'.	3 / 5
Distinctiveness Conflict Risk	'EngageATS' is a specific named product, giving it a clear niche with a distinct trigger and minimal overlap risk with other skills.	5 / 5
	Total	15 / 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/engageats/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.