CtrlK
BlogDocsLog inGet started
Tessl Logo

documenso-observability

Implement monitoring, logging, and tracing for Documenso integrations. Use when setting up observability, implementing metrics collection, or debugging production issues. Trigger with phrases like "documenso monitoring", "documenso metrics", "documenso logging", "documenso tracing", "documenso observability".

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 highly actionable with complete, executable code and useful reference tables, but it is not concise (duplicating the bundled implementation guide inline) and lacks explicit validation feedback loops in its workflows. Progressive disclosure is weakened because the body overlaps heavily with the reference rather than deferring detail to it.

Suggestions

Replace the inline Step 1–6 code blocks that duplicate the implementation guide with brief summaries plus pointers (e.g., 'See references/implementation-guide.md for the full instrumented client'), keeping the body as an overview.

Add explicit validation/feedback checkpoints to the webhook and alerting steps (e.g., verify the metrics endpoint responds before deploying alerts; retry failed webhook processing).

Resolve the dangling 'documenso-incident-runbook' reference in Next Steps — either add it to references/ or phrase it as a suggestion to create it.

DimensionReasoningScore

Conciseness

Mostly efficient with executable code and tables, but the body duplicates much that also appears in implementation-guide.md (instrumented client, logger, health check, metrics endpoint, alerting rules) without delegating, adding length that competes with context.

2 / 3

Actionability

Provides fully executable TypeScript/TypeScript and YAML across all six steps — instrumented Proxy client, winston logger, Express endpoints, Prometheus metrics, webhook handler, alerting rules — copy-paste ready.

3 / 3

Workflow Clarity

Steps are clearly numbered (Step 1–6) but lack explicit validation checkpoints or feedback loops; the webhook and alerting steps involve operations that would benefit from verify-then-retry guidance, and the health-check endpoint references an undefined `app`.

2 / 3

Progressive Disclosure

Structure exists (sections + a real references/implementation-guide.md) but the guide is only weakly signaled in the body; the body re-implements topics already covered in the reference rather than pointing to it one level deep, and the 'Next Steps' pointer to a nonexistent runbook is not clearly signaled.

2 / 3

Total

9

/

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: it names concrete capabilities, includes both a 'Use when' clause and explicit trigger phrases, and is tightly scoped to Documenso observability. Third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists three concrete actions — 'Implement monitoring, logging, and tracing for Documenso integrations' — naming specific observability capabilities rather than vague language.

3 / 3

Completeness

Explicitly answers what ('Implement monitoring, logging, and tracing for Documenso integrations') and when ('Use when setting up observability, implementing metrics collection, or debugging production issues'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Provides a good spread of natural trigger phrases users would say: 'documenso monitoring', 'documenso metrics', 'documenso logging', 'documenso tracing', 'documenso observability'.

3 / 3

Distinctiveness Conflict Risk

Scoped to Documenso integrations with a clear, distinct niche (Documenso-specific observability); unlikely to trigger for unrelated skills.

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.