documenso-install-auth
Install and configure Documenso SDK/API authentication. Use when setting up a new Documenso integration, configuring API keys, or initializing Documenso in your project. Trigger with phrases like "install documenso", "setup documenso", "documenso auth", "configure documenso API key".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 well-structured skill description with clear 'what' and 'when' clauses, explicit trigger phrases, and a distinct niche focused on Documenso SDK/API setup. Its main weakness is that the capability description could be more specific about the concrete actions performed beyond 'install and configure.' Overall, it would perform well in a multi-skill selection scenario.
Suggestions
Add more specific concrete actions, e.g., 'generates API key configuration, initializes the Documenso client, sets up environment variables for authentication.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso SDK/API) and some actions (install, configure, authentication), but doesn't list multiple concrete actions beyond setup—e.g., it doesn't mention specific steps like generating API keys, initializing client instances, or verifying connections. | 2 / 3 |
Completeness | Clearly answers both 'what' (install and configure Documenso SDK/API authentication) and 'when' (setting up a new integration, configuring API keys, initializing in project) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'install documenso', 'setup documenso', 'documenso auth', 'configure documenso API key', 'new Documenso integration'. Good coverage of variations a user might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Documenso setup and authentication—unlikely to conflict with other skills. The product name 'Documenso' and the focus on initial setup/auth create a clear niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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, actionable skill with clear step-by-step workflow and executable code examples across multiple languages. Its main weakness is moderate verbosity — the error handling table, security checklist, and API endpoints table inflate the token cost with information that could be externalized or trimmed. The verification step is a strong inclusion that ensures the setup actually works before moving on.
Suggestions
Move the error handling table and security checklist into a separate reference file (e.g., TROUBLESHOOTING.md) and link to it, keeping SKILL.md focused on the install/auth workflow.
Trim the prerequisites section — Claude doesn't need to be told what a package manager is or that it needs a Documenso account to use the Documenso API.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary elements: the API endpoints table partially duplicates the self-hosted override section, the error handling table covers basic issues Claude would know how to debug, and the security checklist contains general best practices Claude already understands. The prerequisites section explaining what a package manager is and listing obvious requirements adds minor bloat. | 2 / 3 |
Actionability | Fully executable code examples for TypeScript and Python SDK initialization, a concrete verification script with run command, specific dashboard navigation steps for API key generation, and copy-paste ready .env and .gitignore commands. Every step has concrete, executable guidance. | 3 / 3 |
Workflow Clarity | Clear 5-step sequential workflow from installation through verification. Step 5 provides an explicit validation checkpoint to confirm the connection works before proceeding. The error handling table serves as a troubleshooting feedback loop for common failure modes. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's somewhat monolithic — the error handling table, security checklist, and API endpoints table could be in separate reference files. The 'Next Steps' reference to documenso-hello-world is good, but the main file is long for what could be a more concise overview with references to supporting docs. | 2 / 3 |
Total | 10 / 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.