CtrlK
BlogDocsLog inGet started
Tessl Logo

documenso-security-basics

Implement security best practices for Documenso document signing integrations. Use when securing API keys, configuring webhooks securely, or implementing document security measures. Trigger with phrases like "documenso security", "secure documenso", "documenso API key security", "documenso webhook security".

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is strong on conciseness, actionability, and workflow clarity with executable code, validation checkpoints, and checklists. Its main weakness is progressive disclosure: a bundle file exists but is orphaned (never referenced from the body), and detailed guidance is kept inline instead of being navigated to.

Suggestions

Add a clearly signaled one-level-deep reference to the existing bundle, e.g. under a section like "**Full implementation guide**: See [implementation-guide.md](references/implementation-guide.md)", so the provided reference is discoverable rather than orphaned.

Move the detailed per-step implementation (e.g. the extended API key management and rotation material that the implementation guide already contains) into the bundle and keep SKILL.md as a tighter overview pointing to it, reducing inline duplication.

Fix the small completeness gap in the Step 4 example where `userEmail` and `client` are referenced but not declared as parameters/variables, so the code is fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and action-oriented — minimal concept explanation, tight code blocks with only purposeful comments, and no padding about what webhooks or API keys are. It assumes Claude's competence and every section earns its tokens.

3 / 3

Actionability

Provides fully executable TypeScript, Python, and bash snippets (e.g. the timingSafeEqual webhook verifier and the openssl certificate/secret generation commands) that are largely copy-paste ready, matching the executable-code anchor rather than the pseudocode level below.

3 / 3

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints — notably the key-rotation procedure's "Verify secondary key works" step before promotion — and a Security Checklist plus Error Handling table provide feedback loops for recovery, satisfying the top anchor.

3 / 3

Progressive Disclosure

The body is well-sectioned but the provided bundle file references/implementation-guide.md is never linked or signaled from the body ("Next Steps" points to a different skill, "Resources" links only external URLs), and detailed implementation stays inline rather than being split out — fitting the "references present but not clearly signaled; content that should be separate is inline" anchor.

2 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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-crafted: third-person/imperative voice, concrete actions, explicit "Use when" triggers, and a product-specific niche that avoids skill conflicts. It satisfies every dimension at the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "securing API keys, configuring webhooks securely, or implementing document security measures" — naming the domain and several specific tasks, matching the multi-action anchor rather than the single-action level below.

3 / 3

Completeness

Explicitly answers both what ("Implement security best practices for Documenso document signing integrations") and when ("Use when securing API keys, configuring webhooks securely..." plus explicit trigger phrases), satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would actually say ("documenso security", "secure documenso", "documenso API key security", "documenso webhook security") alongside the "Use when" clause, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Targets a clear, product-specific niche (Documenso signing integrations) with distinct, product-named triggers, making conflict with generic security skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
Reviewed

Table of Contents

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.