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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill documenso-observability83
Quality
77%
Does it follow best practices?
Impact
100%
2.00xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/documenso-pack/skills/documenso-observability/SKILL.mdDiscovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with excellent completeness and distinctiveness. It clearly defines the scope (Documenso-specific observability) and provides explicit trigger phrases. The main weakness is that the capabilities could be more specific about concrete actions rather than general observability categories.
Suggestions
Add more specific concrete actions like 'configure structured logging', 'set up distributed tracing', 'create dashboards', or 'implement health checks' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso integrations) and lists general actions (monitoring, logging, tracing, metrics collection, debugging), but doesn't provide concrete specific actions like 'configure log aggregation' or 'set up distributed tracing spans'. | 2 / 3 |
Completeness | Clearly answers both what (implement monitoring, logging, tracing for Documenso integrations) and when (setting up observability, implementing metrics, debugging production issues) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'documenso monitoring', 'documenso metrics', 'documenso logging', 'documenso tracing', 'documenso observability'. Also includes related terms like 'debugging production issues'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by combining the specific product 'Documenso' with observability concerns. The explicit trigger phrases all include 'documenso' prefix, making conflicts with generic monitoring skills unlikely. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, actionable observability guidance with executable code for metrics, logging, and tracing. However, it's overly long for a SKILL.md file and lacks validation checkpoints between setup steps. The content would benefit from splitting reference materials (dashboard JSON, alerting rules) into separate files and adding verification steps.
Suggestions
Add validation checkpoints after each major step (e.g., 'Verify metrics endpoint returns data: curl localhost:3000/metrics | grep documenso')
Move the Grafana dashboard JSON and Prometheus alerting rules to separate reference files (e.g., DASHBOARD.json, ALERTS.yml) and link to them
Add a troubleshooting workflow with explicit 'check -> diagnose -> fix -> verify' steps for common observability issues
Include a quick verification command after tracing setup to confirm spans are being exported
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose sections. The code examples are mostly necessary, but the Grafana dashboard JSON and some explanatory comments could be trimmed. The structure is reasonable but could be more compact. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with proper imports, complete implementations, and copy-paste ready examples. Includes concrete Prometheus alerting rules, health check endpoints, and working metric definitions. | 3 / 3 |
Workflow Clarity | Steps are numbered (Step 1-8) but lack explicit validation checkpoints between steps. No verification that metrics are actually being collected, no testing guidance for tracing setup, and no feedback loops for debugging observability issues. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic at ~400 lines. The Grafana dashboard JSON and alerting rules could be split into separate reference files. Only one external reference exists (documenso-incident-runbook). | 2 / 3 |
Total | 9 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (571 lines); consider splitting into references/ and linking | Warning |
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 | 8 / 11 Passed | |
- 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.