CtrlK
BlogDocsLog inGet started
Tessl Logo

loyjoy

LoyJoy integration. Manage Organizations. Use when the user wants to interact with LoyJoy data.

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/loyjoy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 well-structured and action-oriented with executable CLI commands throughout, and connections are handled with explicit state-machine guidance. Its main weakness is the absence of a validate-before-act feedback loop for batch/destructive action runs, which caps workflow clarity.

Suggestions

Add an explicit validation/verification checkpoint before running mutating or batch actions (e.g. dry-run or confirm affected records, then verify the output field) to establish a feedback loop.

Replace the generic "LoyJoy Overview" bullet list and the marketing intro with entity/action-oriented content that directly supports action discovery.

Tighten the "When to use which actions: Use action names and parameters as needed" line into concrete guidance on choosing actions by intent.

DimensionReasoningScore

Conciseness

The body is mostly lean executable commands with brief, relevant context; the only padding is the marketing-style intro ("conversational marketing platform that allows businesses to automate...") and the "LoyJoy Overview" bullet list, which add little actionable value.

4 / 5

Actionability

It provides copy-paste-ready CLI commands with flags for install, login, connection, action search/run, and proxy requests, covering common cases; minor gaps remain in concrete examples for the result-handling and query-intent specifics.

4 / 5

Workflow Clarity

There is a rough sequence (install → login → connect → poll state → search/run actions) with explicit state-handling for connections, but it lacks a validation checkpoint before destructive or batch action runs, which the rubric caps at 3 for operations missing feedback loops.

3 / 5

Progressive Disclosure

Content is organized into well-signaled sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with a single external pointer (official docs URL) and no nested references; the "LoyJoy Overview" section is thin but structure is otherwise solid.

4 / 5

Total

15

/

20

Passed

Description

48%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 is concise and brand-distinct with a usable "Use when" trigger, but it underspecifies capabilities — "Manage Organizations" is the only concrete action. Expanding the action list and trigger synonyms would lift it above the mid range.

Suggestions

Replace "Manage Organizations" with 2-3 concrete actions (e.g. "list and update Organizations, manage chatbots, retrieve Users") to improve specificity.

Broaden the "Use when" clause with natural trigger phrases a user would actually say, such as "LoyJoy chatbots, conversations, leads, or Organizations".

Add file-format or entity synonyms (Organizations, Users, Chatbots) to strengthen trigger term coverage.

DimensionReasoningScore

Specificity

The description only states "LoyJoy integration" and "Manage Organizations" — it names the domain but lists a single generic action ("Manage Organizations") with no concrete operations, matching the anchor for naming the domain with minimal/generic actions.

2 / 5

Completeness

It provides a clear "what" (LoyJoy integration, manage organizations) plus a "Use when" trigger ("Use when the user wants to interact with LoyJoy data"), so both halves are present; the "when" is explicit but narrow, placing it just below the strongest anchor.

3 / 5

Trigger Term Quality

It surfaces the natural term "LoyJoy" and the generic "Organizations", but lacks synonyms or concrete variations a user would say; coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

The "LoyJoy" brand name gives it a distinct niche with low conflict risk against other skills, though the vague "Manage Organizations" action introduces minor overlap with general CRM-style skills.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.