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

Blog Docs Log in Get started

klaxoon

Klaxoon integration. Manage Users, Organizations, Filters. Use when the user wants to interact with Klaxoon 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/klaxoon/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 highly actionable with copy-paste-ready CLI commands and a well-validated connection flow, but it carries some padding and inlines a large reference table that would benefit from being split into a separate file.

Suggestions

Trim the marketing-style intro paragraph about Klaxoon's purpose and tighten best-practices prose to assume Claude's competence.

Move the 20-row 'Popular actions' table into a references file (e.g., ACTIONS.md) and link to it from the body to improve progressive disclosure.

Add an explicit numbered quick-start sequence at the top (install → login → connection ensure → action list/run) so the macro workflow is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph ('It provides tools for brainstorming, quizzes, surveys... improve engagement and productivity') and best-practices prose include explanation that could be trimmed, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Provides copy-paste-ready commands across the full lifecycle (install, login, connection ensure/get, action list/run, request proxy) with concrete flags and JSON examples covering the common cases, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The connection sub-flow has explicit validation checkpoints and feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED state branching with re-polling), but the top-level install→auth→connect→search→run sequence is conveyed through section order rather than an explicit numbered list, fitting the 'clear sequence with most checkpoints; minor gaps' anchor.	4 / 5
Progressive Disclosure	Sections are clearly headed, but the 20-row 'Popular actions' table is inline reference content that belongs in a separate file and there are no external references or bundle files, matching the 'some structure but content that should be separate is inline' anchor.	3 / 5
	Total	15 / 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 cleanly states what the skill does and when to use it with a distinct, niche trigger, but the capability list relies on one generic verb and the trigger terms are limited to the product name without synonyms.

Suggestions

Replace the single generic verb 'Manage' with distinct concrete actions (e.g., 'Create, update, and delete Users, Organizations, and Filters') to lift specificity.

Expand the 'Use when' clause with additional natural trigger phrases users might say (e.g., 'boards', 'ideas', 'meetings', 'brainstorming') for broader trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Klaxoon domain and three entities ('Manage Users, Organizations, Filters') but relies on a single generic verb rather than multiple distinct concrete actions, matching the 'names domain and 1-2 concrete actions' anchor and falling short of the multi-verb anchor at 4.	3 / 5
Completeness	Provides a clear 'what' ('Manage Users, Organizations, Filters') and an explicit 'when' ('Use when the user wants to interact with Klaxoon data'), matching the anchor where both are present but the trigger could be more specific; not a 5 because the when-clause is a single phrase rather than comprehensive concrete triggers.	4 / 5
Trigger Term Quality	Includes the natural app name ('Klaxoon', 'Klaxoon data') but lacks common variations or synonyms beyond the product name, aligning with the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Klaxoon is a specific named product with a distinct trigger ('interact with Klaxoon data'), giving it a clear niche with minimal overlap risk against other skills.	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/klaxoon/SKILL.md
Commit: f484c82

Reviewed: 6 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.