Tessl • The package manager for agent skills

playwright-ci

Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

80%

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

A concise, actionable overview with strong golden rules and a clean guide index, held back by the absence of an explicit multi-step workflow and by guide references that point to files not present in the bundle.

Suggestions

Include the referenced guide files (ci-github-actions.md, ci-gitlab.md, ci-other.md, parallel-and-sharding.md, docker-and-containers.md, projects-and-dependencies.md, reporting-and-artifacts.md, test-coverage.md, global-setup-teardown.md) in the bundle so the index links resolve.

Add a short "How to use this skill" sequence (pick provider guide → apply golden rules → verify with a sample shard run) with an explicit validation/checkpoint step to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	Lean body with no concept padding: golden rules are tight one-liners carrying concrete values ("retries: 2 in CI only", "traces: 'on-first-retry'", "--shard=N/M"). Assumes Claude's competence; not 2 because there is no unnecessary explanation to trim.	3 / 3
Actionability	Rules give concrete, directly-usable values and identifiers: "retries: 2", "~/.cache/ms-playwright", "mcr.microsoft.com/playwright:v*", "storageState". Not 2 because these are real executable snippets, not pseudocode or vague direction.	3 / 3
Workflow Clarity	The body is a principles-plus-index hub, not a sequenced multi-step workflow; no explicit validation checkpoints or feedback loops are present. Not 1 because the structure is clear and unambiguous, but not 3 because there is no sequenced process with validation steps.	2 / 3
Progressive Disclosure	Navigation is well-designed with clearly signaled one-level-deep table links to 9 guides, but none of the referenced files (ci-github-actions.md, parallel-and-sharding.md, etc.) exist in the bundle, so the disclosure does not actually resolve. Not 1 because the indexing structure itself is excellent; not 3 because the referenced paths are absent.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 specific, well-targeted description with strong natural trigger terms and a clear niche, weakened only by the absence of an explicit 'Use when...' clause that caps completeness at 2.

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up or debugging Playwright tests in CI pipelines, or when the user mentions a specific CI provider, sharding, or test reporting."

Lead with a third-person verb phrase (e.g. "Configures Playwright test runs across CI providers...") to match the action-led style of the strongest reference examples.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown" — rather than vague language. Not score 2 because the enumeration is comprehensive and specific, not a partial domain naming.	3 / 3
Completeness	Clearly states what ("Production-ready CI/CD configurations for Playwright" plus the capability list) but provides no "Use when..." or equivalent explicit trigger guidance. Capped at 2 per the missing-trigger guideline; not 3 because 'when' is only implied, not stated.	2 / 3
Trigger Term Quality	Natural terms a user would say are well covered: "Playwright", "CI/CD", "GitHub Actions", "GitLab CI", "Docker", "parallel sharding", "code coverage". Not score 2 because common variations and provider names are present, not just a single keyword.	3 / 3
Distinctiveness Conflict Risk	"Playwright CI/CD" is a clear niche with distinct provider/tool triggers unlikely to fire for unrelated skills. Not 2 because it is far more specific than generic overlap examples like "Works with document files".	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 9 missing	Warning

	Total	15 / 16 Passed

Repository: zebbern/claude-code-guide
Path: skills/playwright/ci/SKILL.md
Commit: af7d491

Reviewed: about 8 hours 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.