Name: jiminny
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

jiminny

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

Quality

64%

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

Quality

Content

71%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 efficient and highly actionable with concrete CLI commands and a well-instrumented connection-state workflow, but it is a single monolithic file with no progressive disclosure references and contains a couple of dangling step references that hurt navigation.

Suggestions

Fix the dangling navigation: define a labeled 'Step 2' (or reword to 'skip to Searching for actions') and align the '1b' subheading with a clear 'Step 1'.

Consider extracting the proxy flag table and the connection-state reference into a separate reference file (e.g. references/proxy.md) linked from the body to improve progressive disclosure.

Trim the light marketing padding such as 'so you can focus on the integration logic rather than auth plumbing' to push conciseness toward the lean anchor.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and command-driven, with only minor padded phrases such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection', matching the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	Concrete executable commands appear throughout (e.g. `membrane connection ensure "https://jiminny.com" --json`, `membrane action run <actionId> --connectionId=CONNECTION_ID --json`) plus a full proxy-flag table, with minor gaps from unspecific placeholders and dynamically-discovered actions, matching the 'mostly executable guidance; minor gaps' anchor.	4 / 5
Workflow Clarity	The connection flow has a clear state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED with explicit 'poll again' retry), but 'skip to Step 2' is referenced twice with no defined Step 2 and section '1b' has no matching Step 1, a minor navigation gap matching the 'clear sequence with most checkpoints; minor validation gaps' anchor.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inline in one ~140-line file with well-organized headers but no one-level-deep references, and content like the proxy flag table could be separated, matching the 'some structure but could be better organized; content that should be separate is inline' anchor.	3 / 5
	Total	15 / 20 Passed

Description

57%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 pairs a 'what' with an explicit 'Use when...' trigger and leverages the distinct Jiminny brand name, but its action language is generic rather than concrete and the trigger lacks synonym coverage.

Suggestions

Replace generic verbs with Jiminny-specific concrete actions, e.g. 'Search and retrieve call recordings, transcripts, and snippets; pull user and comment data' instead of 'Manage data, records, and automate workflows'.

Broaden the trigger clause with natural synonyms users would say, e.g. 'Use when the user wants to search Jiminny calls, transcriptions, recordings, snippets, or user data'.

Tighten the 'when' clause to specific Jiminny entities (calls, snippets, comments, users) shown in the body's overview to reduce overlap with other integration skills.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Jiminny domain but the actions are generic abstractions rather than concrete operations, falling between anchors 2 and 3 and closer to the minimal/generic anchor.	2 / 5
Completeness	It has both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' clause ("Use when the user wants to interact with Jiminny data"), but the 'when' is generic, matching the 'has both what and when; when could be more specific' anchor rather than the fully concrete level 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Jiminny data" supplies the keyword "Jiminny" and a natural trigger phrase, but coverage of synonyms or variations is thin, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app "Jiminny" makes it largely distinct with low conflict risk, though the generic 'manage data, records, automate workflows' phrasing could overlap with other integration skills, matching the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	13 / 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/jiminny/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.