Name: bunnydoc
Rating: 62.4 (1 reviews)
Author: membranedev

bunnydoc

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

Quality

74%

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/bunnydoc/SKILL.md

Quality

Content

82%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 an action-oriented, well-structured CLI integration guide with executable commands and a polling-based connection workflow. The main gaps are minor padding in the intro and the absence of explicit post-action verification.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational prose with copy-paste commands; the opening paragraph ('document management system that helps users organize, store, and share files...') is mild padding justified by the niche product, fitting anchor 4 rather than 3 or 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, 'connection ensure', 'connection get --wait', 'action list/run', 'request' with flag tables), covering common cases per anchor 5.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with a polling feedback loop and explicit state handling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), matching anchor 4; not 5 because running actions lacks an explicit verify-the-result checkpoint.	4 / 5
Progressive Disclosure	Well-organized into clear sections with tables for actions and proxy flags; no bundle files exist so all content is inline, but the structure is navigable and reasonable for a CLI integration, fitting anchor 4; not 5 because the popular-actions and flag tables could arguably split into reference files.	4 / 5
	Total	17 / 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 concise, third-person, and includes an explicit 'Use when' trigger with a clear brand niche. Its weakness is generic action verbs ('manage data, records') that limit specificity and trigger-term breadth.

Suggestions

Replace generic verbs with concrete BunnyDoc capabilities (e.g., 'create signature requests, manage templates, subscribe to webhooks, add team members').

Expand the 'when' clause to enumerate natural user triggers (e.g., 'Use when the user wants to send documents for signature, manage BunnyDoc templates, or handle webhook events').

Add common synonyms/file extensions or workflow keywords users would actually say to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' — names the BunnyDoc domain plus a few actions, but the actions are generic ('manage data/records') rather than concrete capabilities, matching anchor 3.	3 / 5
Completeness	Both 'what' ('BunnyDoc integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when...') are present, matching anchor 4; not 5 because the 'when' clause is generic ('interact with BunnyDoc data') rather than enumerating concrete triggers.	4 / 5
Trigger Term Quality	Trigger phrase 'Use when the user wants to interact with BunnyDoc data' offers brand-specific keywords but misses common variations or synonyms, fitting anchor 3; not 4 because natural term coverage is thin beyond 'BunnyDoc data'.	3 / 5
Distinctiveness Conflict Risk	Tightly scoped to a named product ('BunnyDoc integration') with brand-specific triggers, giving a clear niche and minimal conflict risk per anchor 5; the generic action verbs do not undermine the distinct brand boundary.	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/bunnydoc/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.