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

Blog Docs Log in Get started

docebo

Docebo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Docebo 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/docebo/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 skill is highly actionable with concrete, executable Membrane CLI commands and a clear connection workflow with polling checkpoints. Its main weaknesses are an oversized inline entity list that hurts token efficiency and the absence of any reference files to offload catalog material.

Suggestions

Move the 75-item entity/activity enumeration into a references file (e.g. ENTITIES.md) and keep only the core resource types inline, relying on 'membrane action list' for discovery.

Number the workflow steps consistently and resolve the dangling 'Step 2' reference so the connect-to-action flow is unambiguous.

Split the proxy flags reference into a short inline summary plus a separate reference file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The CLI command examples are lean and assume competence, but the ~75-item entity/activity enumeration (lines 23-97) is a substantial token spend that duplicates what 'membrane action list' can discover, so the body could be tightened.	3 / 5
Actionability	Commands are copy-paste ready throughout (install, login, connection ensure/get, action list/run, request) with a concrete flags table and JSON examples covering the common cases.	5 / 5
Workflow Clarity	There is a clear sequence (install -> authenticate -> connect -> poll for READY -> search -> run) with state-based polling checkpoints and a retry loop for CLIENT_ACTION_REQUIRED, though the 'Skip to Step 2' references are slightly dangling since steps are not consistently numbered.	4 / 5
Progressive Disclosure	Headers give the body structure, but with no bundle files present the large entity catalog and proxy reference material are inlined in SKILL.md rather than split into one-level-deep reference files.	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 is third-person, answers both what and when, and is well-scoped to a distinct product. It is held back by generic action verbs and a thin set of trigger terms that omit common LMS vocabulary.

Suggestions

Replace generic verbs ('Manage data, records, automate workflows') with concrete Docebo actions such as enrolling users, building courses, and generating reports.

Broaden trigger terms to include natural LMS phrasing users would say, e.g. 'courses, enrollments, learning plans, LMS'.

Add a couple of concrete trigger phrases to the 'Use when...' clause to lift completeness toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain (Docebo) and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete LMS operations like enrolling users or building courses, so it is not comprehensive.	3 / 5
Completeness	Both 'what' (Docebo integration managing data/records and automating workflows) and 'when' ('Use when the user wants to interact with Docebo data') are present and explicit, though the 'when' clause covers a single trigger rather than several concrete ones.	4 / 5
Trigger Term Quality	The primary natural keyword 'Docebo' appears, but common variations a user might say (LMS, courses, learning plans, enrollments) are missing, leaving only relevant-but-incomplete keyword coverage.	3 / 5
Distinctiveness Conflict Risk	'Docebo integration' targets a specific named product with a distinct trigger term, giving it a clear niche and minimal conflict risk with 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/docebo/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.