Name: apptus
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

apptus

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

Quality

66%

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

Quality

Content

67%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 concrete Membrane CLI commands and a well-structured connection-readiness workflow, but it carries some padding (a generic data-term overview and a stub 'Popular actions' section) and a dangling step reference. Tightening these would improve token efficiency and flow.

Suggestions

Remove or replace the generic 'Apptus Overview' bullet list with Apptus-specific entities, or move it to a reference file, since terms like 'Data Cleansing' add no actionable value here.

Flesh out 'Popular actions' with real example action ids/inputs, or delete the section since its command duplicates 'Searching for actions'.

Fix the dangling 'skip to Step 2' reference by explicitly labeling the post-connection steps (e.g. search actions → run/proxy) so the workflow numbering is coherent.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the generic 18-term 'Apptus Overview' bullet list and the 'Popular actions' section (which repeats the discovery command already shown and lists no actual actions) add padding that could be trimmed, fitting 'mostly efficient but includes some unnecessary content'.	3 / 5
Actionability	Concrete, copy-paste-ready commands cover install, login, connection ensure/wait, action list/run, and proxy requests with a flags table, but the 'Popular actions' stub delivers no real examples and the run example uses a generic placeholder input, leaving minor gaps.	4 / 5
Workflow Clarity	There is a clear install→login→connect→search→run sequence with a genuine feedback loop around connection state (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with re-polling), but the dangling 'skip to Step 2' reference and the absence of result-validation for data actions are minor gaps.	4 / 5
Progressive Disclosure	The single SKILL.md is organized into clear, navigable sections with headers and no bundle files are needed for this CLI integration; the generic overview list and detailed flag reference are inlined but the structure remains easy to navigate, fitting 'good structure with minor organization gaps'.	4 / 5
	Total	15 / 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 clearly identifies its niche (Apptus) and provides an explicit 'Use when' trigger, but the capability verbs are generic and the trigger vocabulary is narrow. It is solid but could be sharper on concrete actions and trigger synonyms.

Suggestions

Replace generic verbs with concrete Apptus capabilities, e.g. 'Manage product attributes, categories, and merchandising rules; run queries and import/export data'.

Broaden trigger terms with natural synonyms users might say, such as 'e-commerce merchandising', 'product recommendations', or 'Apptus product placement'.

Tighten the 'what' so it reads as specific Apptus operations rather than abstract data-management phrasing.

Dimension	Reasoning	Score
Specificity	It names the domain (Apptus) and three action verbs ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like 'extract text' or 'fill forms', landing between the generic-actions anchor (2) and the concrete-actions anchor (3).	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Apptus data') are present, though the 'what' is somewhat generic, fitting the anchor where both exist but could be more specific.	4 / 5
Trigger Term Quality	The trigger revolves around a single keyword family ('Apptus', 'Apptus integration', 'Apptus data') with one natural phrase ('interact with Apptus data'), but no synonyms or variations are offered, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Apptus' is a specific named product with a clear niche and a distinct trigger ('interact with Apptus data'), giving minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/apptus/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.