Name: knowbe4
Rating: 60.8 (1 reviews)
Author: membranedev

knowbe4

KnowBe4 integration. Manage Users, Roles, Organizations, Persons, Groups, Campaigns and more. Use when the user wants to interact with KnowBe4 data.

Quality

71%

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/knowbe4/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 body is highly actionable with copy-paste CLI commands and a solid connection-state validation loop, but it carries unnecessary conceptual padding and inlines large reference tables that would benefit from being split into separate files.

Suggestions

Cut the introductory paragraph defining KnowBe4 and the redundant 'KnowBe4 Overview' bullet list, which explain concepts Claude already knows.

Move the Popular actions table and proxy flag reference into a references/ file (e.g. ACTIONS.md) and link to it from the body to improve progressive disclosure.

Fix the broken 'skip to Step 2' reference by either labeling the next section 'Step 2: Search for actions' or removing the step numbering, and add a brief note to verify the `output` field after running an action.

Dimension	Reasoning	Score
Conciseness	Mostly efficient actionable CLI guidance, but the opening paragraph explaining what KnowBe4 is and the redundant 'KnowBe4 Overview' bullet list restate concepts Claude already knows and could be trimmed.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands across the common cases (install, login, connection ensure, polling, action list/run, proxy) backed by a concrete Popular actions table and a proxy flag reference.	5 / 5
Workflow Clarity	Clear install→login→connect→search→run→proxy sequence with a real validation/feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED and CONFIGURATION_ERROR), but the dangling 'skip to Step 2' reference with no Step 2 header and absent output validation after running actions are minor gaps.	4 / 5
Progressive Disclosure	Well-organized section headers aid navigation, but this is a monolithic ~167-line single file with large reference-style content (the 18-row Popular actions table and proxy flag table) inlined and no use of references/ files despite the skill's substantial size.	3 / 5
	Total	15 / 20 Passed

Description

71%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 clearly names a distinct branded domain and lists concrete managed entities with an explicit 'Use when' clause. Its main weaknesses are a generic repeated verb and the absence of the natural domain terms (phishing, security awareness training) users would actually say.

Suggestions

Replace the repeated generic verb 'Manage' with distinct concrete actions (e.g., 'List, create, and update Users, Groups, and Campaigns') to lift specificity toward 5.

Add the natural user-facing terms 'phishing campaigns' and 'security awareness training' to the 'Use when' clause so it triggers on domain phrasing, not just the brand name.

Tighten the 'when' clause to list concrete triggers (e.g., 'Use when the user wants to manage KnowBe4 users, run phishing or training campaigns, or pull account reports').

Dimension	Reasoning	Score
Specificity	Lists several concrete entities to manage (Users, Roles, Organizations, Persons, Groups, Campaigns), but relies on a single generic verb 'Manage' and hedges with 'and more', leaving minor coverage gaps that keep it below a 5.	4 / 5
Completeness	Explicitly answers both 'what' (KnowBe4 integration managing those entities) and 'when' ('Use when the user wants to interact with KnowBe4 data'), but the 'when' clause is brand-tied and lacks concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	Triggers rest mainly on the brand name 'KnowBe4' plus entity nouns, while the natural user phrasing for this domain ('phishing simulation', 'security awareness training') is missing, so common synonyms/variations are absent.	3 / 5
Distinctiveness Conflict Risk	Targets a specific branded niche (KnowBe4) with distinct entity-level triggers, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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/knowbe4/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.