Name: journeyfront
Rating: 62.4 (1 reviews)
Author: membranedev

journeyfront

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

Quality

74%

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

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 body is a strong, command-driven integration guide with executable examples and a clear connection-state workflow including a polling feedback loop. Weaknesses are minor: a few filler lines, inconsistent step numbering, and slight redundancy between the action-listing sections.

Suggestions

Fix the workflow numbering so 'skip to Step 2' has an actual Step 2 header and the lone '1b' aligns with numbered steps, or relabel them as named phases.

Trim filler lines ('Use action names and parameters as needed.' and the awkward Agent Types sentence) and shorten the introductory product paragraph.

Merge or differentiate 'Searching for actions' and 'Popular actions' so the action-discovery guidance appears once with clear intent.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, concrete commands, with only minor over-explanation such as the introductory product paragraph and filler like 'Use action names and parameters as needed' and the awkward Agent Types sentence, matching the 'Efficient; minor instances of over-explanation that could be trimmed' anchor rather than the leaner score 5.	4 / 5
Actionability	It provides copy-paste ready commands across install, login, connection ensure/get, action list/run, and proxy with a full flag table, matching the 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The connection lifecycle is sequenced with state-based branching and an explicit feedback loop (poll until READY, re-poll after the user completes an action), matching the 'Clear sequence with most checkpoints present; minor validation gaps' anchor; it falls short of 5 because step numbering is inconsistent ('skip to Step 2' with no Step 2 header, a lone '1b' without 1a/2).	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well sectioned (Overview, Authentication, Connecting, Searching, Actions, Proxy, Best practices), matching the 'Good structure; most content is appropriately placed; minor organization gaps' anchor; it does not reach 5 because the 'Popular actions' section partly duplicates 'Searching for actions' and the proxy flag table could be a candidate for a separate reference.	4 / 5
	Total	17 / 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 pairs a what/when structure in third person and is distinct because it names a specific product, but its action list is generic and its trigger-term coverage is thin. Tightening 'Manage data, records' into concrete Journeyfront actions and adding natural synonyms would lift specificity and trigger-term quality.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Journeyfront actions (e.g., 'query journey events, manage templates, automate workflow steps').

Expand the 'Use when' clause with natural synonyms users might say, such as 'customer journey analytics', 'journey events', or 'Journeyfront workflows'.

Consider mentioning the data hierarchy (User/Journey/Step/Event, Template) in the description to add specificity beyond 'data, records'.

Dimension	Reasoning	Score
Specificity	The description names the domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the 'Names domain and 1-2 concrete actions, but not comprehensive' anchor; it falls short of score 4 because nothing is as specific as 'extract, fill, merge' and exceeds score 2 by naming multiple actions.	3 / 5
Completeness	It provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Journeyfront data'), matching the 'Has both what and when; when could be more explicit or specific' anchor; it does not reach 5 because the 'what' is generic and the trigger phrase is narrow.	4 / 5
Trigger Term Quality	It relies on 'Journeyfront' and 'Journeyfront data' as the primary natural terms but lacks common variations or synonyms (e.g., 'customer journey', 'analytics'), matching the 'Some relevant keywords but missing common variations or synonyms' anchor rather than the broader coverage at score 4.	3 / 5
Distinctiveness Conflict Risk	Naming the proprietary product 'Journeyfront' with a product-specific trigger ('interact with Journeyfront data') creates a clear niche with minimal conflict risk, matching the 'Clear niche with distinct triggers; minimal conflict risk' anchor.	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/journeyfront/SKILL.md
Commit: f484c82

Reviewed: ~17 hours 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.