Tessl • The package manager for agent skills

pipeline-blueprint

Provide CI/CD best practices and pipeline templates for GitHub Actions and GitLab CI, recommending configurations based on project type (frontend, backend, fullstack, library, monorepo, mobile). Trigger when users ask about setting up CI/CD, automating builds, improving pipelines, or mention keywords like GitHub Actions, GitLab CI, pipeline templates, or deployment automation.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/pipeline-blueprint/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

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

The body is a well-organized, executable template collection with strong actionability and decent conciseness. Its main weaknesses are the absence of validation/verification checkpoints in the deployment workflows and the lack of any reference files to offload the large template volume.

Suggestions

Add explicit validation checkpoints to deployment workflows (e.g., verify the built artifact exists, run a smoke test, confirm required secrets are present) before promoting to production.

Move the six project-type templates into reference files under references/ (e.g., references/frontend.yml) and keep SKILL.md as an overview that links to them, improving progressive disclosure.

Replace the placeholder `echo "Add your deployment command here"` deploy steps with at least one concrete, executable example per platform (e.g., an S3 sync or Cloudflare Pages command) so the guidance is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The prose is mostly efficient and avoids explaining concepts Claude already knows, with only minor instances of guidance that could be trimmed further.	4 / 5
Actionability	Provides multiple complete, copy-paste-ready YAML workflows for both platforms with concrete stages and caching; deploy steps remain placeholder echo commands, a minor gap.	4 / 5
Workflow Clarity	The selection flow (project type → template → adapt) is present but lacks validation checkpoints, and deploy steps are placeholders rather than verified sequences.	3 / 5
Progressive Disclosure	Content is well-organized into sections but everything is inlined in a 651-line SKILL.md with no referenced bundle files, so there is no one-level-deep reference structure to navigate.	3 / 5
	Total	14 / 20 Passed

Description

83%Weight 40%Scale 1-5

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 strong: it states concrete capabilities, names the platforms and project types it serves, and provides explicit trigger guidance with natural keywords. It is well-scoped and distinguishable from adjacent skills.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete actions — "Provide CI/CD best practices and pipeline templates" and "recommending configurations based on project type" — and enumerates six project types, leaving only minor coverage gaps.	4 / 5
Completeness	Clearly answers both what it does and when to use it: "Trigger when users ask about setting up CI/CD, automating builds, improving pipelines, or mention keywords like GitHub Actions, GitLab CI…" provides concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keyword coverage including brand names users actually say ("GitHub Actions", "GitLab CI") plus phrases like "pipeline templates" and "deployment automation"; a few synonyms could still be added.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (CI/CD for two named platforms) with distinct triggers and minimal overlap risk with unrelated skills.	4 / 5
	Total	17 / 20 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
skill_md_line_count	SKILL.md is long (652 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: zebbern/claude-code-guide
Path: skills/pipeline-blueprint/SKILL.md
Commit: 59c5fc4

Reviewed: 4 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.