BB esign-automation
Automate contract signing, esign, and signature workflows by calling the eSignGlobal CLI tool. The eSignGlobal CLI is agent-friendly, with JSON output by default, making eSignGlobal signing operations easy to parse and chain. Supports creating draft envelopes, obtaining sender view URLs, sending envelopes, querying envelope details, sending reminders, cancelling envelopes, downloading signed files, verifying PDF signatures locally, rendering templates to generate documents for signing, comparing two PDF contracts side by side, managing envelope attachments, managing CC (carbon copy) recipients, and adding or removing signers from draft envelopes.
As a process B 77/100 · Nearly there — no weak spots found
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6590 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 77/100
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 5 branches
- 70Execution cost. Instruction body is 6590 tokens
- 85Steps. 216 steps, 2 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 23 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -212 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 654: enough signal without eating the budget
- +4Structure: 65 headings
- +3Step-by-step instructions: 216 items
- +3Output format is stated explicitly
- +4Has examples (45 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.