Name: precoro
Rating: 49.6 (1 reviews)
Author: membranedev

precoro

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

Quality

54%

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

Quality

Content

42%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 operational guidance for using the Membrane CLI with Precoro is concrete and well-sequenced, but it is buried under hundreds of irrelevant bullet points that destroy token efficiency. Removing the padded overview list would dramatically improve the skill.

Suggestions

Delete the 'Precoro Overview' bullet list of ~660 generic and unrelated terms; it is padding that wastes context and obscures the real guidance.

If any reference material is genuinely needed, move it into a references/ file and link to it one level deep instead of inlining it in SKILL.md.

Add an explicit verification step after running actions (e.g., checking the output/error fields) to close the workflow feedback loop for data-mutating operations.

Dimension	Reasoning	Score
Conciseness	The ~660-line 'Precoro Overview' bullet list is heavily padded with irrelevant terms (AI Ethics, Blockchain, Quantum Computing, Global Warming, the letters A-Z), wasting enormous context budget on content Claude already knows or that is unrelated to Precoro.	1 / 5
Actionability	The 'Working with Precoro' section provides concrete, copy-paste-ready commands (login, connection ensure, action list/run, request) with a flags table, though a few placeholders like CONNECTION_ID must be substituted.	4 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced with validation checkpoints (polling --wait, checking READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR states), though step numbering is slightly inconsistent and action-result verification is implicit.	4 / 5
Progressive Disclosure	There are no bundle files and the SKILL.md is a monolithic 800+ line document whose giant term list is inlined content that clearly does not belong inline, with no external reference files to offload detail.	2 / 5
	Total	11 / 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 brand-distinct and covers both what and when, but its action language is generic and it lacks the natural procurement vocabulary users would actually say. Tightening the actions to concrete procurement terms would raise specificity and trigger quality.

Suggestions

Replace generic actions like 'Manage data, records, and automate workflows' with concrete procurement operations (e.g., 'create purchase orders, manage invoices and suppliers, track approvals').

Add natural trigger phrases users would say, such as 'procurement', 'purchase orders', 'invoices', or 'suppliers', to the 'Use when' clause.

Make the 'when' clause more specific than 'interact with Precoro data' by listing the concrete intents that should activate the skill.

Dimension	Reasoning	Score
Specificity	It names the domain ('Precoro integration') and a few actions ('Manage data, records, and automate workflows'), but those actions are generic and omit concrete procurement operations like purchase orders, invoices, or suppliers.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Precoro data'), though the 'when' clause is somewhat generic rather than listing concrete triggers.	4 / 5
Trigger Term Quality	The brand keyword 'Precoro' is a natural trigger users would say, but common domain synonyms (procurement, purchase orders, invoices, suppliers) are missing.	3 / 5
Distinctiveness Conflict Risk	The Precoro brand name makes the trigger highly specific and unlikely to fire for unrelated skills, giving it a clear niche with minimal conflict risk.	5 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (813 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/precoro/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.