documenso-hello-world
Create a minimal working Documenso example. Use when starting a new Documenso integration, testing your setup, or learning basic document signing patterns. Trigger with phrases like "documenso hello world", "documenso example", "documenso quick start", "simple documenso code", "first document".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/documenso-pack/skills/documenso-hello-world/SKILL.mdQuality
Discovery
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 solid description with excellent trigger terms and completeness, clearly specifying both what the skill does and when to use it. Its main weakness is that the 'what' portion is somewhat general — it says 'create a minimal working example' without detailing the specific actions involved (e.g., creating documents, adding recipients, sending for signature). Overall it performs well for skill selection purposes.
Suggestions
Add more specific concrete actions to the 'what' portion, e.g., 'Creates a minimal Documenso example that uploads a document, adds a signer, and sends it for signature.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Documenso integration) and a general action ('Create a minimal working example'), but doesn't list multiple specific concrete actions like creating documents, uploading PDFs, adding signers, or sending for signature. | 2 / 3 |
Completeness | Clearly answers both 'what' (create a minimal working Documenso example) and 'when' (starting a new integration, testing setup, learning basic signing patterns) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger phrases like 'documenso hello world', 'documenso example', 'documenso quick start', 'simple documenso code', and 'first document' — these are terms users would naturally say when starting out with Documenso. | 3 / 3 |
Distinctiveness Conflict Risk | Documenso is a specific product/platform, and the triggers are highly specific to that niche ('documenso hello world', 'documenso quick start'). Very unlikely to conflict with other skills. | 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 is a solid hello-world skill with excellent actionability — all three language examples are complete and executable. The main weaknesses are verbosity from providing three equivalent implementations inline and the lack of validation checkpoints between API-dependent steps. Trimming to one primary example with brief pointers to alternatives, and adding success verification between steps, would significantly improve it.
Suggestions
Add validation checkpoints between API calls (e.g., check doc.documentId is truthy before proceeding to upload, verify upload response before adding recipients) to catch failures early.
Consider making TypeScript the primary example and moving Python/curl equivalents to a separate reference file to reduce token usage.
Move the Field Types Reference table to a separate FIELD-TYPES.md file and link to it, keeping only the most common 3-4 types inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides three equivalent implementations (TypeScript, Python, curl) which is somewhat redundant for a hello-world example. The field types reference table and document lifecycle diagram add useful reference value, but the overall content is longer than necessary — a single primary example with brief notes on alternatives would be more token-efficient. | 2 / 3 |
Actionability | All code examples are fully executable and copy-paste ready with specific imports, API calls, and run commands. The TypeScript, Python, and curl examples each provide complete working workflows with concrete field coordinates, method names, and expected console output. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced (create → upload → add recipient → add field → send), and the document lifecycle diagram is helpful. However, there are no validation checkpoints — no verification that the document was created successfully before uploading, no check that the file upload succeeded before adding recipients, and no error handling in the workflow steps themselves despite this being an API-dependent multi-step process. | 2 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections, but the field types reference table (11 rows) and error handling table could be in separate reference files. The skill references external resources and next steps, but inline content is heavier than ideal for a quick-start skill with no bundle files to offload to. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.