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 implementations are complete and executable. The main weaknesses are redundancy (three equivalent implementations inline) and lack of validation checkpoints between API calls. The field types table and error handling section add useful reference value but could be better served as linked reference files to keep the quick-start focused.
Suggestions
Add validation checkpoints between API calls (e.g., check response status/existence of documentId before proceeding to upload) to catch errors early in the workflow.
Move the Field Types Reference table and Python/curl equivalents to separate linked files (e.g., FIELD_TYPES.md, examples/) to keep the hello-world skill focused on a single executable path.
Add a brief verification step at the end (e.g., check document status via API or log the signing URL) to confirm the workflow completed successfully.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides three equivalent implementations (TypeScript, Python, curl) for the same task, which is somewhat redundant for a hello-world skill. The field types reference table and document lifecycle diagram add useful reference value but bulk up the content. Some trimming is possible (e.g., the test PDF generation step includes unnecessary detail). | 2 / 3 |
Actionability | All code examples are fully executable and copy-paste ready across three languages/tools. Specific coordinates, field types, API endpoints, and run commands are provided. The TypeScript example includes inline comments explaining each step. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (create → upload → add recipient → add field → send), but there are no validation checkpoints or error recovery steps between stages. For an API workflow where each step depends on the previous one succeeding, there should be explicit checks (e.g., verify document was created before uploading, verify upload succeeded before adding recipients). | 2 / 3 |
Progressive Disclosure | The skill has good section organization and references external resources and next-step skills. However, the field types reference table and three full implementation variants could be split into separate reference files to keep the hello-world skill leaner. The inline content is heavy for what should be a quick-start guide. | 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
3e83543
- 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.