Name: sap-hana
Rating: 63.2 (1 reviews)
Author: membranedev

sap-hana

SAP S4 HANA integration. Manage Organizations, Persons, Leads, Deals, Activities, Notes and more. Use when the user wants to interact with SAP S4 HANA 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/sap-hana/SKILL.md

Quality

Content

75%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.

A highly actionable CLI integration skill with copy-paste commands and a well-structured connection workflow including error-recovery feedback loops. It loses points mainly for an unnecessary ERP intro and slightly inconsistent step numbering.

Suggestions

Delete the opening paragraph explaining what SAP S4 HANA / an ERP is; Claude already knows this and it pads the context window.

Fix the step numbering so 'skip to Step 2' resolves to a labeled Step 2 and '1b' has a matching 1a, making the connection sequence unambiguous.

Consider moving the 19-row Popular actions table into a references/actions.md file referenced from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Command examples are efficient, but the opening paragraph explaining what SAP S4 HANA / an ERP system is and prose like 'so you can focus on the integration logic rather than auth plumbing' restate concepts Claude already knows.	3 / 5
Actionability	Provides copy-paste-ready CLI commands with flags across install, auth, connection, action search, action run, and proxy, plus a full proxy-options reference table covering the common cases.	5 / 5
Workflow Clarity	The connect-to-wait-to-search-to-run sequence has state-based feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with re-polling), but numbering is inconsistent ('skip to Step 2' with no Step 2, '1b' with no 1a).	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references, but as a single 160-line file over the 50-line simple-skill threshold it inlines a long 19-row actions table that could live in a separate reference.	4 / 5
	Total	16 / 20 Passed

Description

75%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.

A solid description that names the domain, lists concrete managed entities, and includes an explicit Use-when trigger in third person. It stops short of the top band by relying on one generic trigger clause and a single uniform verb.

Suggestions

Vary the action verbs beyond 'Manage' (e.g., 'Create, update, and list Organizations, Persons, Leads...') to broaden specificity.

Expand the 'when' clause into concrete trigger phrases (e.g., 'Use when the user wants to query, create, or update SAP S/4HANA records like sales orders, business partners, or purchase orders').

Add common synonyms/variants users say (e.g., 'S/4HANA', 'SAP ERP', 'business partners') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete entity types to manage (Organizations, Persons, Leads, Deals, Activities, Notes), but the single repeated verb 'Manage' leaves minor gaps in action diversity rather than comprehensive coverage.	4 / 5
Completeness	Explicitly states both what (integration managing listed entities) and when ('Use when the user wants to interact with SAP S4 HANA data'), but the 'when' is a single generic clause rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the natural product term 'SAP S4 HANA' plus entity keywords users would mention, but lacks synonyms or common variants beyond the one system name.	4 / 5
Distinctiveness Conflict Risk	The SAP S4 HANA product name carves a clear, distinct niche with low conflict risk, though generic entity terms like Leads and Deals could marginally overlap with CRM skills.	4 / 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/sap-hana/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.