Name: gitbook
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

gitbook

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

Quality

66%

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/gitbook/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 concrete Membrane CLI commands and a clear connection workflow including polling checkpoints. It loses points for a padded introductory explanation and a monolithic structure with no progressive disclosure to separate reference material.

Suggestions

Trim the introductory paragraph that defines GitBook and Membrane; Claude already knows these and the value is in the CLI commands.

Fix the step numbering (referenced "Step 2" and "1b" have no matching "Step 1"/"Step 2" headers) so the workflow sequence is unambiguous.

Move the detailed clientAction state reference and the proxy flag table into a separate reference file linked from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient CLI commands, but the opening paragraph explaining what GitBook and Membrane are ("GitBook is a knowledge management platform...", "Think of it as a modern documentation tool...") is padding Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a documented flag table, covering the common cases executably.	5 / 5
Workflow Clarity	The install→auth→connect→search→run flow is clear and the connection step includes state-polling feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the "Step 2"/"1b" numbering is inconsistent and never resolves to labeled steps.	4 / 5
Progressive Disclosure	It is a single monolithic file with no bundle files or external references, and reference-style content (the clientAction state-machine details and proxy flag table) is inlined rather than split into a deeper reference.	3 / 5
	Total	15 / 20 Passed

Description

61%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 well-scoped to GitBook with an explicit trigger clause, but its capability list is generic. Tightening the actions to concrete GitBook operations and adding synonym trigger terms would lift specificity and trigger quality.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete GitBook operations such as creating/editing pages, searching spaces, and managing content.

Add natural synonym trigger terms users would say, e.g. "documentation", "wiki", "knowledge base", or "GitBook pages".

Keep the explicit "Use when..." clause but tie the when to those concrete operations for a sharper trigger.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the GitBook domain but the actions are generic and abstract rather than concrete GitBook operations (e.g. create pages, edit content, search spaces).	2 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with GitBook data"), but the what is generic so it stops short of the concrete-trigger anchor at 5.	4 / 5
Trigger Term Quality	"GitBook" and "interact with GitBook data" provide the core natural keyword but miss common variations and synonyms a user might say such as documentation, wiki, pages, or knowledge base.	3 / 5
Distinctiveness Conflict Risk	The description is scoped specifically to GitBook ("GitBook integration", "interact with GitBook data"), giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	14 / 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/gitbook/SKILL.md
Commit: f484c82

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