Name: ascora
Rating: 63.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ascora

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

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ascora/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 body is highly actionable with executable commands and strong error-state handling, and it is well-sectioned for navigation. Its main weakness is the lack of a verify-before-execute checkpoint for destructive actions such as marking payments or invoices as sent.

Suggestions

Add an explicit validation step before destructive/batch actions (e.g. list the affected payments, confirm with the user, then run mark-payments-sent) to lift workflow clarity above the cap.

Fill the empty Description column in the Popular actions table or move that table plus the proxy flag reference into a separate reference file.

Trim filler lines ("Use action names and parameters as needed") and condense the opening Ascora summary to assume Claude's competence.

Dimension	Reasoning	Score
Conciseness	Largely efficient with copy-pasteable commands earning their place, though lines like "Use action names and parameters as needed" and the opening Ascora summary are trimmable filler.	4 / 5
Actionability	Fully executable guidance throughout: concrete install/login/connection/action/proxy commands plus complete flag tables covering the common cases.	5 / 5
Workflow Clarity	The connect-wait-search-run sequence has explicit state checkpoints and error feedback loops, but actions like "Mark Payments as Sent" are destructive/batch operations with no validation checkpoint before execution, capping this dimension per the rubric.	3 / 5
Progressive Disclosure	Well-organized into clear navigable sections, but at ~145 lines reference-like material (the Popular actions table and full proxy flag table) is inlined rather than split into separate files.	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 answers both what and when with a strong, distinctive brand trigger, but the capability list stays generic ("manage data, records") rather than naming concrete operations. Tightening the action verbs and adding a second trigger phrase would raise specificity and completeness.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Ascora operations, e.g. "List and update jobs, time entries, clients, and invoices".

Add a second explicit trigger phrase, e.g. "Use when the user wants to query Ascora jobs, clients, or invoices."

Mention key entity names (jobs, time entries, clients) that a user would naturally say, to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Ascora integration") and a couple of actions ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete like "extract text" or "fill forms".	3 / 5
Completeness	Both "what" (Ascora integration managing data/records/workflows) and "when" (Use when the user wants to interact with Ascora data) are present and clear, but the trigger guidance is a single phrase rather than multiple concrete triggers.	4 / 5
Trigger Term Quality	The explicit "Use when the user wants to interact with Ascora data" gives a strong natural trigger plus the brand term "Ascora" with "data", "records", and "workflows"; a few common synonym variations are missing.	4 / 5
Distinctiveness Conflict Risk	The "Ascora" brand name pins a clear niche with distinct triggers and minimal conflict risk against other 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/ascora/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.