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 and explicit trigger phrases targeting a specific product (Documenso). Its main weakness is that the capability description could be more specific about the concrete actions performed beyond generic 'install and configure.' Overall, it's a strong description that would enable accurate skill selection.
Suggestions
Add more specific concrete actions, e.g., 'Sets up environment variables, generates API tokens, installs the @documenso/sdk package, and validates authentication' to improve specificity.
| 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., no mention of specific configuration steps, token management, or environment variable setup. | 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 provided. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'install documenso', 'setup documenso', 'documenso auth', 'configure documenso API key', 'API keys', 'initializing Documenso'. These are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive—'Documenso' is a specific product name, and the scope is narrowed to installation/configuration/auth setup. Very unlikely to conflict with other skills. | 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 well-structured, highly actionable skill that provides clear step-by-step guidance for installing and authenticating with the Documenso SDK. Its main weakness is moderate verbosity — the security checklist, full endpoint table, and duplicated self-hosted URL override add tokens without proportional value. The workflow is clear with good validation via the verification script.
Suggestions
Remove the 'Self-Hosted Base URL Override' section since it duplicates the comment already present in Step 4's code example.
Trim the security checklist to 1-2 non-obvious items or remove entirely — most items (env vars, .gitignore, CI secrets) are standard practices Claude already knows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary content like the full API endpoints table (cloud staging, self-hosted patterns are predictable), the self-hosted base URL override section which duplicates the comment already shown in Step 4, and the security checklist which covers general best practices Claude already knows. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code for TypeScript and Python SDK initialization, API key generation steps are specific with exact UI navigation, and includes a concrete verification script with the exact command to run it. | 3 / 3 |
Workflow Clarity | Clear 5-step sequential workflow from installation through verification, with an explicit connection verification step (Step 5) that serves as a validation checkpoint. The error handling table provides a feedback loop for common failure modes with specific solutions. | 3 / 3 |
Progressive Disclosure | Has good structure with clear sections and a reference to 'documenso-hello-world' for next steps, plus external resource links. However, the error handling table, security checklist, and API endpoints table are all inline when some could be referenced separately, making the document longer than ideal for an overview skill. | 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
70e9fa4
- 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.