Name: asure-software
Rating: 62.4 (1 reviews)
Author: membranedev

asure-software

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

Quality

74%

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/asure-software/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 highly actionable with executable commands and a well-validated connection workflow, supported by clean sectioning. It loses points mainly to a padded marketing intro and a missing post-action verification step for mutating operations.

Suggestions

Delete the introductory marketing paragraph about Asure Software's market positioning; Claude does not need it to run the integration.

Fix the dangling 'Step 2' reference by either labeling the 'Searching for actions' section as Step 2 or removing the cross-references.

Add a brief verification note for mutating proxy/action calls (e.g. re-query the resource after a POST/PUT/DELETE to confirm the change landed) to close the validation gap for destructive operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the opening marketing paragraph ('Asure Software provides cloud-based solutions... used by HR, facilities, and IT departments') and lines like 'so you can focus on the integration logic rather than auth plumbing' explain context Claude does not need, plus the 'action list' command is demonstrated twice, keeping it at the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides copy-paste-ready executable commands for every stage (install, login, connection ensure, action list, action run, request) with a complete flag table for the proxy, covering the common cases fully.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit validation checkpoints (polling --wait, branching on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with feedback loops), but the dangling 'Step 2' reference (no labeled Step 2) and the absence of any post-action verification for potentially mutating proxy calls keep it just below the fully-validated anchor.	4 / 5
Progressive Disclosure	Content is well organized into clear sections (Overview, Working with Asure Software, Popular actions, Best practices) with no nested references, but at ~143 lines everything lives in a single inline file with no detail offloaded to separate reference files, leaving a minor organization gap relative to the ideal one-level-deep split.	4 / 5
	Total	16 / 20 Passed

Description

73%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, and its product-specific naming makes it highly distinct. Its main weakness is generic verb choices that undersell the concrete capabilities the body actually exposes.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Asure operations visible in the body, e.g. 'Request time off, manage employees, leave types, and accruals'.

Sharpen the 'when' trigger by naming the entities users mention, e.g. 'Use when the user wants to query or update time-off requests, employees, leave types, or accruals in Asure Software'.

Add the natural synonym 'AsureForce' (matching the docs URL developer.asureforce.net) so the skill also triggers on that common variant.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Asure Software integration') and lists a few actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete, domain-specific operations, so it stops at the 1-2 concrete-actions anchor rather than reaching comprehensive specific actions.	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Asure Software data') are present, but the 'when' clause is fairly generic and could name concrete intents (time-off, employees, accruals) to reach the fully-explicit anchor.	4 / 5
Trigger Term Quality	'Asure Software' and 'interact with Asure Software data' are natural terms a user would say, giving good keyword coverage; it falls short of 5 only because there are no synonym or product-variant terms to round out the trigger set.	4 / 5
Distinctiveness Conflict Risk	Naming a specific commercial product ('Asure Software') gives it a clear niche with distinct triggers and minimal risk of overlapping with unrelated skills.	5 / 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/asure-software/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.