Name: jrni
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

jrni

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

Quality

68%

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/jrni/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.

The content is highly actionable with executable CLI commands and a well-sequenced connection workflow including state-based recovery. It loses points on minor verbosity, a dangling "Step 2" reference, and inlining detail that could be split into reference files.

Suggestions

Trim the JRNI overview prose and the auth-plumbing aside so the body assumes Claude's competence and earns more conciseness.

Resolve the undefined "Step 2" reference (there is no Step 1/Step 2 numbering) and add an explicit success check after `membrane action run` to close the workflow loop.

Move the proxy flag table and the clientAction state breakdown into reference files under ./references/ and link to them from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as the JRNI marketecture prose ("Retailers, banks...") and the "so you can focus on the integration logic rather than auth plumbing" aside, fitting anchor 3.	3 / 5
Actionability	It provides copy-paste-ready CLI commands across install, login, connection ensure/get, action list/run, and proxy requests with a full flag table, covering the common cases as in anchor 5.	5 / 5
Workflow Clarity	There is a clear install→auth→connect→search→run sequence with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll loop, but the dangling "Step 2" reference and absence of success-validation for run actions keep it at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	The single SKILL.md is well-sectioned with clear headers and no nested references, but inlined content like the proxy flag table and full clientAction breakdown could live in reference files; with no bundle files present this fits anchor 4 (good structure, minor organization gaps).	4 / 5
	Total	16 / 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 covers both what and when with a clear "Use when" trigger, anchored on a distinctive proper-noun domain. Its weakness is generic action verbs and limited keyword variation, which keep specificity and trigger quality at mid-range.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete JRNI actions like "list availability, create bookings, and manage customer records" to lift specificity.

Expand the trigger clause with natural phrases users would say, e.g. "Use when the user wants to query JRNI appointments, availability, or customer bookings."

Add file/extension or API surface terms (e.g. "JRNI API", "appointments", "events") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the JRNI domain with a couple of actions, but the verbs are generic rather than concretely enumerated, matching anchor 3 rather than the multi-action 4/5.	3 / 5
Completeness	It states both what ("JRNI integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with JRNI data"), matching anchor 4; not 5 because the trigger phrase is generic rather than listing concrete triggers.	4 / 5
Trigger Term Quality	The only natural keyword is "JRNI" with the trigger phrase "interact with JRNI data"; there are no synonyms or extensions, fitting anchor 3 (some relevant keywords, missing common variations).	3 / 5
Distinctiveness Conflict Risk	"JRNI" is a distinct proper-noun niche with low conflict risk, fitting anchor 4 (mostly distinct, minor overlap); not 5 because "interact with JRNI data" is broad enough to slightly overlap generic data skills.	4 / 5
	Total	14 / 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/jrni/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.