documenso-ci-integration
Configure CI/CD pipelines for Documenso integrations. Use when setting up automated testing, deployment pipelines, or continuous integration for Documenso projects. Trigger with phrases like "documenso CI", "documenso GitHub Actions", "documenso pipeline", "documenso automated testing".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 strong completeness and distinctiveness due to the Documenso-specific scoping and explicit trigger phrases. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., creating workflow files, configuring specific CI providers, setting up test suites). Overall it's a solid description that would perform well in skill selection.
Suggestions
Add more specific concrete actions like 'create GitHub Actions workflow files, configure test suites, set up deployment stages, manage environment secrets' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CI/CD pipelines for Documenso) and some actions (automated testing, deployment pipelines, continuous integration), but doesn't list specific concrete actions like 'create GitHub Actions workflows, configure test runners, set up deployment stages'. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure CI/CD pipelines for Documenso integrations) and 'when' (setting up automated testing, deployment pipelines, or continuous integration for Documenso projects), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms: 'documenso CI', 'documenso GitHub Actions', 'documenso pipeline', 'documenso automated testing'. These are phrases users would naturally say, and the explicit trigger phrase list covers common variations. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Documenso' + 'CI/CD' creates a very specific niche. The trigger terms are all Documenso-prefixed, making it unlikely to conflict with generic CI/CD skills or other Documenso skills focused on different aspects. | 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 strong, highly actionable skill with complete, executable examples covering the full CI/CD pipeline for Documenso. The workflow is well-sequenced with appropriate validation checkpoints and error recovery. The main weakness is that the content is somewhat long with full test implementations inline that could benefit from being split into referenced files, and there's minor verbosity in explanatory sections.
Suggestions
Consider moving the full unit test and integration test implementations into separate referenced files (e.g., `tests/unit/document-service.test.ts.example`) and keeping only key patterns/snippets inline to improve progressive disclosure and conciseness.
Remove the Resources section linking to GitHub Actions and Vitest docs — Claude already knows these tools and can find documentation independently.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable examples, but includes some unnecessary elements like the 'Resources' section linking to docs Claude already knows, the explanation of what the pre-commit hook does, and the overview section restating what's in the description. The CI strategy summary table is useful but the error handling table adds moderate bulk. | 2 / 3 |
Actionability | Fully executable code throughout: complete GitHub Actions YAML, TypeScript test files, bash commands for secrets, package.json scripts, and husky config. All examples are copy-paste ready with realistic details like timeout values, conditional execution, and cleanup steps. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence with logical ordering (workflow → unit tests → integration tests → secrets → scripts → pre-commit). Includes validation checkpoints: unit tests gate integration tests via `needs: unit-tests`, cleanup runs with `if: always()`, and the CI strategy table clarifies when each test type runs. Error recovery is addressed in the error handling table. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's quite long (~180 lines of substantive content) with full test file implementations inline that could be referenced as separate files. References to `documenso-local-dev-loop` and `documenso-deploy-integration` are good, but no bundle files exist to support splitting. The inline test code makes this somewhat monolithic. | 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.