CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/living-documentation-publisher

Converts passing Cucumber JSON output into stakeholder-facing living documentation: generates HTML reports via multiple-cucumber-html-reporter (Node) or Serenity BDD aggregate (JVM), applies Gherkin tags to drive report sections, and publishes to GitHub/GitLab Pages in CI. Use when BDD scenarios are in use and the team needs an always-current, non-test-engineer-readable document showing which acceptance criteria pass.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A thorough, actionable skill with executable code, a gated publish workflow, and clean one-level-deep references. Its main weakness is redundancy: the workflow is described in the Overview, the 'How to use' list, and the detailed steps, with the latter's 'Step N' annotations further duplicating section numbering.

Suggestions

Collapse the Overview's 'This skill covers the full workflow: produce Cucumber JSON...publish the HTML artefact...' paragraph, since it restates both the 'How to use' list and the per-step sections.

Remove the parenthetical 'Step 1'/'Step 4'/'Steps 2-3' annotations in the 'How to use' list - they duplicate the detailed section numbering and read as confusing cross-references.

Trim the blockquote definition plus the 'living documentation vs plain test reports' paragraph to a single framing sentence, relying on the sourced link for the full distinction.

DimensionReasoningScore

Conciseness

Mostly efficient with executable code, but the same workflow is restated three times (the Overview summary paragraph, the 'How to use' list, and the per-step sections) and the blockquote-plus-distinction paragraph explains a concept Claude largely knows; it is not level 3 because not every token earns its place, and not level 1 because the bulk is lean and actionable.

2 / 3

Actionability

Provides copy-paste-ready, executable guidance - package.json script, serenity.properties config, gherkin tags, and bash commands (npx cucumber-js, mvn verify, serenity:aggregate, serenity:check, set -e gating); it is not level 2 because the examples are complete rather than pseudocode.

3 / 3

Workflow Clarity

A clear six-step sequence with an explicit validation gate in Step 5 ('Only publish passing runs' via set -e and serenity:check) plus an anti-patterns table for error recovery; it is not level 2 because validation checkpoints and feedback loops are explicit, not implicit.

3 / 3

Progressive Disclosure

SKILL.md is an overview with well-signaled, one-level-deep references to the three verified bundle files (node-reporter.md, serenity-reporter.md, ci-publish.md); it is not level 2 because references are clearly signaled and content is appropriately split rather than monolithic.

3 / 3

Total

11

/

12

Passed

Description

100%

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

A strong, third-person description that states concrete capabilities and gives an explicit 'Use when' trigger tied to BDD/Cucumber living documentation. It is distinguishable from sibling reporting skills and avoids fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - "generates HTML reports via multiple-cucumber-html-reporter (Node) or Serenity BDD aggregate (JVM), applies Gherkin tags to drive report sections, and publishes to GitHub/GitLab Pages in CI" - matching the level-3 anchor of several specific actions; it is not level 2 because the actions are comprehensive rather than partial.

3 / 3

Completeness

Explicitly answers both what (the actions) and when via "Use when BDD scenarios are in use and the team needs an always-current, non-test-engineer-readable document"; it is not level 2 because the when is explicit, not implied.

3 / 3

Trigger Term Quality

Covers natural terms users would say - "Cucumber JSON", "BDD scenarios", "living documentation", "GitHub/GitLab Pages", "acceptance criteria" - with good breadth; it is not level 2 because common variations are present rather than missing.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (stakeholder-facing living documentation from passing Cucumber output) with distinct triggers unlikely to fire for other skills; it is not level 2 because the scope is specific rather than overlapping.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

Passed

Reviewed

Table of Contents