Name: quaderno
Rating: 61.6 (1 reviews)
Author: membranedev

quaderno

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

Quality

73%

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

Quality

Content

88%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 a tight, highly actionable integration guide with executable commands, a clearly sequenced connection workflow, and explicit validation/feedback loops. Its only weak spots are a redundant repeated command and slightly generic overview prose.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and minimal padding, though the 'Popular actions' section repeats the `action list` command already shown under 'Searching for actions' and the Quaderno overview is mildly explanatory — fitting score 4 (efficient with minor trimmable instances).	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (npm install, membrane login, connection ensure, action list/run, request with a full flag table), matching the score-5 anchor of fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced (install → login → connection ensure → poll/wait) with explicit validation checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR states) and a feedback loop (poll again after the user acts), matching the score-5 anchor.	5 / 5
Progressive Disclosure	The body is well-organized into clearly headed sections with no unnecessary external references (none exist), but as a single ~140-line file it is not the clean one-level-deep split of the score-5 anchor, landing at score 4.	4 / 5
	Total	18 / 20 Passed

Description

57%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 names the Quaderno domain and includes an explicit 'Use when' trigger, but its stated capabilities ('manage data, records, automate workflows') are generic rather than reflecting Quaderno's concrete invoicing/tax features. It is clear and distinct but lacks specificity.

Suggestions

Replace generic actions with Quaderno-specific capabilities, e.g. 'Create invoices, retrieve tax rates, and manage customers and subscriptions in Quaderno'.

Add concrete trigger terms users would actually say, such as 'Use when the user wants to create Quaderno invoices, look up tax rates, or manage subscriptions'.

Mention key Quaderno entities (invoices, credit notes, customers, products) to sharpen the 'what' and reduce overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	Phrases 'Manage data, records, and automate workflows' name the Quaderno domain but the actions are generic ('manage data, records', 'automate workflows') rather than concrete Quaderno-specific capabilities like invoicing or tax calculation, matching the score-2 anchor of naming the domain with minimal/generic actions.	2 / 5
Completeness	It has both a 'what' ('Quaderno integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Quaderno data'), but the 'what' is somewhat generic so it sits at score 4 rather than 5.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Quaderno data' includes the natural keyword 'Quaderno' but misses common variations or synonyms, fitting the score-3 anchor of some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	Naming 'Quaderno' explicitly gives it a clear, distinct niche with minimal conflict risk, but the surrounding 'manage data, records, and automate workflows' is broad enough to create minor overlap, matching score 4.	4 / 5
	Total	13 / 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/quaderno/SKILL.md
Commit: f484c82

Reviewed: 5 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.