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".

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and concise, with executable code, a clearly sequenced workflow, and proper cleanup/feedback loops for risky batch operations. Progressive disclosure is the weakest dimension: the body inlines sizable workflow and test blocks that overlap the deeper implementation-guide.md reference rather than summarizing and pointing to it.

Suggestions

Slim the inline GitHub Actions and test blocks to minimal examples and add a clearly signaled pointer (e.g. 'See references/implementation-guide.md for full workflows, GitLab CI, and cleanup scripts') so the body stays an overview.

Make the cross-skill links to `documenso-local-dev-loop` and `documenso-deploy-integration` explicit markdown links or clearly labeled references rather than bare inline names.

Dimension	Reasoning	Score
Conciseness	The body is lean and task-focused: it jumps straight into a workflow file, test code, secrets commands, and package.json scripts without explaining what CI, vitest, or GitHub Actions are, so every token earns its place.	3 / 3
Actionability	It provides fully executable, copy-paste-ready artifacts — a complete GitHub Actions YAML, runnable vitest unit and integration test files, concrete `gh secret set` commands, and package.json scripts — with specific file paths and env var bindings.	3 / 3
Workflow Clarity	Steps are clearly sequenced (workflow -> unit tests -> integration tests -> secrets -> scripts -> optional hook), integration tests are gated on unit-test success via `needs`, and the destructive cleanup runs with `if: always()` plus an afterAll deletion loop, giving explicit validation/feedback checkpoints for a risky batch operation.	3 / 3
Progressive Disclosure	The body is well-sectioned and points to a real one-level-deep reference (`documenso-local-dev-loop`, `documenso-deploy-integration`, and references/implementation-guide.md), but the in-body GitHub Actions and test code duplicate material expanded in implementation-guide.md without clearly signaling 'see implementation-guide.md for full workflows', so some content that could live only in the reference is inline.	2 / 3
	Total	11 / 12 Passed

Description

82%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-structured with clear 'what' and 'when' guidance and strong, natural trigger phrases scoped to the Documenso CI niche. Its only weakness is specificity, where it names broad categories rather than enumerating concrete, distinct actions.

Suggestions

Replace generic categories ('automated testing, deployment pipelines, continuous integration') with concrete actions, e.g. 'mock the Documenso SDK for unit tests, run integration tests against staging, wire up GitHub Actions secrets, and clean up test documents'.

Tighten the description prose — the embedded newlines and trailing spaces add noise without aiding recall.

Dimension	Reasoning	Score
Specificity	The description names the domain ('CI/CD pipelines for Documenso integrations') and references automated testing, deployment pipelines, and continuous integration, but these are high-level categories rather than a list of multiple concrete actions (e.g. 'create unit test mocks', 'configure staging secrets', 'add cleanup steps').	2 / 3
Completeness	It answers both 'what' ('Configure CI/CD pipelines for Documenso integrations') and 'when' via an explicit 'Use when setting up...' clause plus 'Trigger with phrases like...', satisfying the what-and-when requirement.	3 / 3
Trigger Term Quality	It lists natural trigger phrases users would say ('documenso CI', 'documenso GitHub Actions', 'documenso pipeline', 'documenso automated testing'), giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	The 'documenso'-prefixed triggers carve out a clear niche scoped to Documenso CI work, making it unlikely to fire for unrelated CI/deployment skills.	3 / 3
	Total	11 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/documenso-pack/skills/documenso-ci-integration/SKILL.md
Commit: 4c47e33

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.