Name: jack-henry
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

jack-henry

Jack Henry integration. Manage data, records, and automate workflows. Use when the user wants to interact with Jack Henry 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/jack-henry/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 content is a strong, executable guide with a clear connection-state workflow and well-organized sections. Its main weaknesses are minor verbosity (a redundant company intro and a repeated command) and the absence of explicit action-result validation.

Suggestions

Remove the introductory 'Jack Henry is a technology solutions...' paragraph or compress it to one line; the official-docs link already provides context Claude can use.

Deduplicate the action-list command by keeping it in 'Searching for actions' and removing the repeated 'Popular actions' invocation, or cross-reference instead.

Add an explicit checkpoint after running an action, e.g. 'Check the output field for errors and re-run with adjusted --input if the action reports a failure', to strengthen workflow validation.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but the opening paragraph explaining what Jack Henry is and the duplicated action-list command (in both 'Searching for actions' and 'Popular actions') are unnecessary padding that could be tightened, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands for install, login, connection, action search/run, and proxying with a clear flags table, but relies on placeholder substitution (CONNECTION_ID, QUERY, <actionId>) and lacks a single fully-filled end-to-end example, so it is not quite a 5.	4 / 5
Workflow Clarity	The connection flow is a clear sequence with a documented state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-and-retry feedback loop, but there is no explicit validation of action-run results before proceeding, leaving a minor checkpoint gap.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clearly headed sections (overview, install, auth, connecting, actions, proxy, best practices) with no nested references, but the inline proxy-flag table and entity listing could justify a separate reference file, so it is good but not exemplary.	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 correctly answers both what and when and is highly distinct thanks to the Jack Henry proper noun, but its capability list and trigger keywords are generic. Tightening the actions and expanding natural trigger phrases would lift it from good to excellent.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Query customer and account records, retrieve loan and transaction details, and initiate ACH/wire transfers' instead of 'Manage data, records, and automate workflows'.

Broaden the trigger clause with natural synonyms, e.g. 'Use when the user wants to query Jack Henry accounts, loans, transactions, or initiate ACH/wire transfers'.

Mention the entity types users actually name (customers, accounts, loans, payments) as trigger terms to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and lists a few action categories ('Manage data, records, and automate workflows'), but these are generic verbs rather than concrete, specific capabilities, so it sits at the '1-2 concrete actions but not comprehensive' anchor rather than a 4.	3 / 5
Completeness	It states both what ('Jack Henry integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Jack Henry data') explicitly, but the 'when' trigger is narrow and the 'what' is generic, so it is not a clear 5.	4 / 5
Trigger Term Quality	'Jack Henry data' provides one strong natural proper-noun keyword users would say, but coverage is otherwise generic ('data', 'records', 'workflows') with no synonyms or related natural phrases, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The proper noun 'Jack Henry' carves out a clear niche with a distinct trigger, making conflict with other skills minimal.	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/jack-henry/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.