CtrlK
BlogDocsLog inGet started
Tessl Logo

zenkraft

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

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/zenkraft/SKILL.md
SKILL.md
Quality
Evals
Security

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 copy-paste commands and a strong connection-state workflow including validation feedback loops. It is held back only by minor over-explanation, a lack of validation guidance before destructive proxy/action calls, and a somewhat dense single-file layout.

Suggestions

Add a validation/check step before destructive proxy calls (e.g. for DELETE) and before action runs, such as confirming the target or dry-running a GET first, to satisfy the destructive-operation feedback-loop guidance.

Trim rhetorical padding like 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection' to improve token efficiency.

Consider splitting the proxy flags table and request details into a short references file to lighten the main SKILL.md, signaling the reference clearly one level deep.

DimensionReasoningScore

Conciseness

The body is dominated by executable commands, a flags table, and best practices with little padding, but a few sentences over-explain ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') that could be trimmed; not a 5 due to these minor instances.

4 / 5

Actionability

Provides copy-paste-ready commands for every common case (install, login, connection ensure/get, action list/run, request) plus a complete flags table, fully covering the integration workflow with executable examples.

5 / 5

Workflow Clarity

The connection setup is a clear sequence with explicit state-based validation (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but there is no validation checkpoint before potentially destructive proxy (DELETE) or action-run calls, a minor gap that keeps it below 5.

4 / 5

Progressive Disclosure

A single well-organized file with clear section headers and no need for external references (no bundle files present); good structure, though the inlined flags table and proxy options are dense enough that minor organization gaps remain versus a 5.

4 / 5

Total

17

/

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 cleanly answers what and when using a distinct product name as the trigger, but its action vocabulary is generic and it offers only one trigger phrase. Tightening the actions and adding concrete trigger terms would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete Zenkraft actions, e.g. 'Create and track shipments, generate labels, schedule pickups, and quote rates' to raise specificity.

Expand the 'when' clause with concrete trigger phrases users actually say, e.g. 'Use when the user wants to create shipments, print labels, track packages, or get shipping rates in Zenkraft'.

Add common synonyms/file or object terms (shipments, labels, manifests, tracking) so the trigger term coverage is comprehensive.

DimensionReasoningScore

Specificity

Names the Zenkraft domain and two actions ('Manage data, records, and automate workflows') but the actions are generic rather than concrete, matching the 'domain + 1-2 actions, not comprehensive' anchor; not a 4 because it lacks several specific concrete actions.

3 / 5

Completeness

Explicitly answers both 'what' (Zenkraft integration, manage data/records/workflows) and 'when' ('Use when the user wants to interact with Zenkraft data'); not a 5 because the 'when' offers only a single trigger phrase rather than multiple concrete ones.

4 / 5

Trigger Term Quality

Includes the natural product term 'Zenkraft' and 'data' in the trigger clause, but misses common variations or synonyms a user might say; not a 2 because 'Zenkraft' is a genuine natural keyword, not pure jargon.

3 / 5

Distinctiveness Conflict Risk

Zenkraft is a specific named platform giving it a clear niche with a distinct trigger, but the generic action verbs ('manage data, records, automate workflows') carry minor overlap risk with adjacent CRM/Salesforce skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.