Name: aqilla
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

aqilla

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

Quality

61%

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

Quality

Content

57%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 skill delivers strong, executable CLI guidance with a well-instrumented connection workflow, but it is weighed down by a large generic entity enumeration and lacks verification steps for destructive action runs. Structure is present but the inlined overview list works against progressive disclosure.

Suggestions

Remove or move the ~120-item entity bullet list into a separate reference file; most entries are generic and not Aqilla-specific, adding tokens without value.

Add a validation/verification checkpoint after running destructive actions (e.g., re-query the created record or check the response status before reporting success).

Split the proxy flag table and detailed clientAction handling into a referenced file so SKILL.md stays a lean overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The ~120-item 'Aqilla Overview' bullet list is heavy padding, much of it generic (Campaign, Lead, Forum, Donation) rather than Aqilla-specific, while the CLI sections are reasonably efficient, landing at 'noticeably verbose with padded sections' rather than the severely verbose anchor 1.	2 / 5
Actionability	Commands are fully executable and copy-paste ready across install, login, connection ensure/get, action list/run, and proxy requests with a flags table and JSON input examples, matching the 'fully executable, specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with state checks and a poll-after-action feedback loop, but running potentially destructive Aqilla actions (payments, journal entries) has no result-verification step, triggering the destructive/batch cap at 3.	3 / 5
Progressive Disclosure	Section headers organize the content but no bundle files exist and the large inline entity list is content that should be split out or trimmed, fitting 'some structure but content that should be separate is inline'.	3 / 5
	Total	13 / 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 is distinct and provides an explicit use-when clause, but its action list is generic and trigger coverage is thin. It reads as a competent but slightly under-specified integration description.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Aqilla operations such as 'post transactions, run reports, and manage invoices'.

Broaden trigger terms to include natural user phrasings like 'Aqilla records', 'Aqilla reports', or 'sync data with Aqilla'.

Tighten the 'when' clause with multiple concrete triggers (e.g., 'Use when the user wants to query, create, or update Aqilla records or run Aqilla reports').

Dimension	Reasoning	Score
Specificity	Names the Aqilla domain plus three actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Aqilla operations, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor and sitting above the minimal/generic anchor 2.	3 / 5
Completeness	Both a 'what' ('Aqilla integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Aqilla data.') are stated, but the trigger phrasing is limited, so it matches anchor 4 rather than the concrete-multi-trigger anchor 5.	4 / 5
Trigger Term Quality	The natural keyword 'Aqilla' and phrase 'interact with Aqilla data' are present, but there are no synonyms or variations, fitting 'some relevant keywords but missing common variations' rather than the fuller coverage of anchor 4.	3 / 5
Distinctiveness Conflict Risk	Aqilla is a specific named application, giving a clear niche with a distinct trigger and minimal conflict risk with other skills, matching the anchor 5 example.	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/aqilla/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.