Name: erpnext
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

erpnext

ERPNext integration. Manage Companies. Use when the user wants to interact with ERPNext data.

Quality

63%

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

Quality

Content

65%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 copy-paste CLI commands and useful reference tables, and the connection workflow is clearly sequenced. It loses points for over-explanation, missing validation on destructive action runs, and a monolithic structure with no reference files.

Suggestions

Add a verification step after destructive/batch actions (e.g. re-fetch the document or check the `output`/`state` fields) so create/update/bulk workflows include a validation checkpoint.

Trim the ERPNext overview paragraph and editorializing sentences; assume Claude knows what an ERP system is.

Move the large popular-actions table and proxy-flag reference into a separate REFERENCES.md and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly command-focused and efficient, but the opening paragraph explains what ERPNext is and includes editorializing ('focus on the integration logic rather than auth plumbing', 'This is the fastest way') that Claude does not need.	3 / 5
Actionability	Copy-paste-ready CLI commands are given throughout (login, connection ensure/get, action list/run, request) plus concrete action-key and proxy-flag tables covering the common cases.	5 / 5
Workflow Clarity	The connection flow is well sequenced with a state-machine and polling checkpoints, but destructive/batch operations (create-document, update-document, bulk update) lack any explicit validation step, capping the score.	3 / 5
Progressive Disclosure	The single file is well sectioned with headers, but with no bundle files the bulky 20-row popular-actions catalog and proxy-flag table are inlined rather than split into a reference file.	3 / 5
	Total	14 / 20 Passed

Description

62%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 concise and includes an explicit 'Use when' trigger, naming the ERPNext domain clearly. It is weak on action breadth and trigger-term variety, listing only 'Manage Companies' as a concrete capability.

Suggestions

List more concrete actions beyond 'Manage Companies' (e.g., list/create/update documents, customers, sales orders) to improve specificity.

Add natural trigger synonyms users might say, such as 'ERPNext records', 'DocType', 'sales invoices', or 'ERPNext CRM'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to query, create, or update ERPNext documents such as customers, orders, or invoices.'

Dimension	Reasoning	Score
Specificity	Names the domain ('ERPNext integration') plus one concrete action ('Manage Companies'), but coverage is minimal rather than comprehensive.	3 / 5
Completeness	Both 'what' (ERPNext integration, manage companies) and an explicit 'when' ('Use when the user wants to interact with ERPNext data') are present, though the 'when' could be more specific.	4 / 5
Trigger Term Quality	'ERPNext' and 'interact with ERPNext data' are relevant keywords a user might say, but common synonyms and variations are missing.	3 / 5
Distinctiveness Conflict Risk	ERPNext is a named, specific system giving a clear niche with low conflict risk, but the generic 'interact with data' phrasing leaves minor overlap with other data skills.	4 / 5
	Total	14 / 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/erpnext/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.