Name: contractbook
Rating: 51.2 (1 reviews)
Author: membranedev

contractbook

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

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/contractbook/SKILL.md

Quality

Content

56%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 provides actionable, executable CLI guidance with a clear connection workflow and feedback loop, but is dragged down by a large padded entity/integration list and lack of any progressive-disclosure references. Tightening the inline dump and moving bulk reference material out would materially improve it.

Suggestions

Replace the ~90-line bullet list of entity and integration names with a brief summary plus a pointer to where the full catalog can be discovered (e.g. via `membrane action list`), removing the padding.

Fix the workflow numbering (label "Step 2" explicitly and reconcile the "1b" sub-step) so the connection sequence reads as a single coherent ordered process.

Add at least one concrete Contractbook-specific action example (e.g. listing or running a real contract action) so the actionable guidance is not entirely generic placeholder-driven.

Dimension	Reasoning	Score
Conciseness	The ~90-line bullet dump of entity and integration names ("Contract", "Template", ... "Google Cloud Storage Integration") plus filler like "Use action names and parameters as needed." is significant padding, though the operational sections are leaner.	2 / 5
Actionability	Concrete copy-paste CLI commands cover the common workflow (login, connection ensure, action list/run, request) with a flags table; minor gaps remain in the form of generic placeholders and no Contractbook-specific action example.	4 / 5
Workflow Clarity	A clear connection sequence with state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-user-action feedback loop is present, but step numbering is inconsistent ("1b", an unlabeled "Step 2").	4 / 5
Progressive Disclosure	The single file is section-organized but has no external references signaled, and the large inline entity list is content that could plausibly be split into a separate reference file.	3 / 5
	Total	13 / 20 Passed

Description

57%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 correctly answers both what the skill does and when to use it and is distinct by virtue of naming a specific product, but its actions and trigger terms are generic. Replacing vague phrasing with concrete Contractbook operations and natural trigger synonyms would raise it.

Suggestions

Replace generic verbs with concrete Contractbook actions, e.g. "Create and send contracts for e-signature, manage templates and counterparties, and automate contract workflows."

Expand the trigger clause with natural synonyms users would say, e.g. "Use when the user wants to manage contracts, send documents for e-signature, or work with Contractbook records."

Avoid the generic phrase "interact with Contractbook data", which restates the brand rather than describing a recognizable user intent.

Dimension	Reasoning	Score
Specificity	It names the domain (Contractbook) but the actions "Manage data, records, and automate workflows" are minimal and generic rather than concrete Contractbook operations such as creating contracts or sending for e-signature.	2 / 5
Completeness	Both a "what" (Contractbook integration; manage data, records, workflows) and an explicit "Use when..." "when" clause are present; the "when" is generic and could be more specific.	4 / 5
Trigger Term Quality	"Contractbook" is a relevant keyword and "interact with Contractbook data" is a usable trigger, but common synonyms and variations (contracts, e-signature, templates, documents) are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Contractbook gives it a clear niche with minimal conflict risk, though the generic triggers leave minor overlap with adjacent CRM or document-signing skills.	4 / 5
	Total	13 / 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/contractbook/SKILL.md
Commit: f484c82

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