Name: journyio
Rating: 56.8 (1 reviews)
Author: membranedev

journyio

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

Quality

65%

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/journyio/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 body is a well-structured, actionable guide with concrete CLI commands and a clear connection workflow including feedback loops. It loses points mostly to background prose padding and a 'Popular actions' section that promises but does not deliver a list.

Suggestions

Trim the marketing-style CDP intro and 'so you can focus...' sentence to assume Claude's competence.

Either populate 'Popular actions' with concrete example actions or rename the section to reflect that it only shows the discovery command.

Add a brief validation note for destructive proxy operations (e.g. confirming before DELETE/PATCH on records).

Dimension	Reasoning	Score
Conciseness	The bulk is lean executable commands, but the CDP intro paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding.	3 / 5
Actionability	Copy-paste ready membrane commands with explained flags cover auth, connection, action discovery, execution, and proxying; minor gaps remain (placeholders, and 'Popular actions' lists no actual actions).	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-again feedback loop, with only minor validation gaps.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no external bundle files needed; all content lives appropriately in one SKILL.md with minor organization gaps.	4 / 5
	Total	15 / 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 covers both what and when with a clear product-named trigger, but its action language is generic rather than concrete, limiting specificity. Tightening the action verbs to reflect actual CDP capabilities would raise the score.

Suggestions

Replace generic verbs with concrete CDP actions, e.g. 'Collect, unify, and activate customer data; manage users, accounts, and trips.'

Add file-extension or entity-level trigger phrases (e.g. 'when the user mentions Journy.io users, accounts, or itinerary items').

Clarify the 'when' clause with specific intents like syncing records or automating workflows.

Dimension	Reasoning	Score
Specificity	Names the Journy.io domain with several action verbs ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete CDP-specific capabilities.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Journy.io data') are present, though the trigger could be more specific.	4 / 5
Trigger Term Quality	Includes the natural product term 'Journy.io' and 'data' in the trigger clause, but lacks synonyms or broader variations users might say.	3 / 5
Distinctiveness Conflict Risk	The named SaaS product 'Journy.io' gives it a clear niche, but the generic action phrasing ('manage data', 'automate workflows') creates minor overlap risk with other 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/journyio/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.