Name: entrust-datacard
Rating: 62.4 (1 reviews)
Author: membranedev

entrust-datacard

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

Quality

74%

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

Quality

Content

82%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 highly actionable with executable CLI commands and a sensible state-aware connection workflow, supported by clean sectioning. The main weaknesses are minor prose padding and inconsistent step numbering that breaks the otherwise clear sequence.

Suggestions

Remove marketing filler ("Their products are used by governments, enterprises, and financial institutions" and the "focus on the integration logic rather than auth plumbing" aside) to tighten token efficiency.

Normalize the workflow numbering so "Step 2" and "1b" references resolve to actual labeled steps (e.g., Step 1 connect, Step 2 search actions, Step 3 run), clarifying the main path.

If the action catalog or proxy details grow, split them into a reference file (e.g., ACTIONS.md) referenced one level deep to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean CLI commands and an options table, but includes minor padding such as "Their products are used by governments, enterprises, and financial institutions" and "so you can focus on the integration logic rather than auth plumbing", fitting the level-4 "efficient; minor over-explanation" anchor.	4 / 5
Actionability	It provides copy-paste-ready, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request proxy) plus a concrete flags table, matching the level-5 "fully executable; specific examples cover the common cases" anchor.	5 / 5
Workflow Clarity	There is a clear install → login → connect → wait → search → run sequence with state-machine validation (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but the "Step 2" / "1b" labels reference steps that are not consistently numbered, leaving minor gaps at level 4 rather than 5.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections (Overview, Working with, Install, Auth, Connecting, Searching, Popular actions, Best practices) with no nested references, but at ~140 lines with all content inlined and no bundle files it sits at level 4's "good structure, minor organization gaps" rather than the minimal-overview level 5.	4 / 5
	Total	17 / 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 answers both what and when and is well-scoped to a distinct product, but its action verbs are generic and its trigger phrasing lacks synonyms. It is solid but not exemplary.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete actions the integration actually performs (e.g., "create orders, manage card production jobs, query printers and users").

Expand the when-clause with natural trigger phrases and synonyms users would say, such as "Entrust Datacard", "datacard", "card production", or "identity card printing".

Consider listing the key object types (Order, Printer, Card, User) in the description to sharpen capability specificity.

Dimension	Reasoning	Score
Specificity	Names the Entrust Datacard domain plus a couple of actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete like "extract" or "fill forms", fitting the level-3 anchor and falling short of level 4's "several specific actions".	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Entrust Datacard data"), but the when-clause is general rather than packed with concrete trigger phrases, placing it at level 4 rather than level 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Entrust Datacard data" surfaces the product name and "data"/"records" as keywords, but lacks synonyms or variations a user might naturally say, matching the level-3 anchor rather than the comprehensive level-5 coverage.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named proprietary product "Entrust Datacard" gives it a clear niche with minimal overlap risk against other skills, matching the level-5 anchor.	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/entrust-datacard/SKILL.md
Commit: f484c82

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