pipeline

Detect stack and generate CI/CD pipeline configs. Usage: /pipeline <detect|generate> [options]

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/pipeline/SKILL.md

Quality

Content

76%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 token-efficient and provides mostly executable command/script guidance, but the detect→generate workflow is implicit and lacks validation checkpoints, and external file references cannot be verified against a bundle that is absent.

Suggestions

Make the detect→generate workflow explicit with numbered steps (e.g. 1. detect → stack.json, 2. generate --input stack.json) and add a verification step (e.g. lint the generated YAML).

Point script references at local bundle paths (./scripts/) or confirm the bundled scripts exist, since ./scripts, ./references, and ./assets are absent.

Clarify or remove the self-referential 'Skill Reference → SKILL.md' pointer, which currently points to a path outside the skill bundle.

Dimension	Reasoning	Score
Conciseness	The ~25-line body is lean and efficient: usage, examples, a script list with flags, and a reference pointer — no padding and no explanation of concepts Claude already knows, matching the lean-and-efficient anchor.	5 / 5
Actionability	Concrete slash-command examples and script invocations with full flag sets (--repo, --platform, --input, --output, --format) are given, but no actual code is shown and the referenced scripts live at external paths not present in the bundle, leaving a minor gap.	4 / 5
Workflow Clarity	The detect→generate sequence is only implicit (via --input <stack.json>) rather than explicitly numbered, and there are no validation or verification checkpoints for pipeline generation, fitting the steps-present-but-checkpoints-missing anchor and the batch-operation cap at 3.	3 / 5
Progressive Disclosure	Sections (Usage, Examples, Scripts, Skill Reference) are well organized with one-level-deep, clearly signaled references; the minor gap is that referenced script paths and the 'Skill Reference' point to external/non-bundled locations rather than local bundle files.	4 / 5
	Total	16 / 20 Passed

Description

53%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 clearly states what the skill does but omits any 'when to use' trigger guidance, capping completeness. Trigger terms are relevant but lack common synonyms, and capabilities are only partially enumerated.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up CI/CD, generating GitHub Actions or GitLab CI pipelines, or detecting a project's stack and tooling.'

Expand capability coverage to name target platforms and output formats (e.g. 'generate GitHub Actions or GitLab CI YAML').

Include natural synonyms users say ('GitHub Actions', 'GitLab CI', 'build workflow') to improve trigger-term recall.

Dimension	Reasoning	Score
Specificity	Names the domain ('CI/CD pipeline configs') and two concrete actions ('Detect stack', 'generate'), but coverage is not comprehensive — platforms (GitHub/GitLab) and output formats are absent, matching the 1-2 concrete actions anchor.	3 / 5
Completeness	The 'what' is clear ('Detect stack and generate CI/CD pipeline configs'), but there is no 'Use when...' trigger clause — the 'Usage:' line is invocation syntax, not usage guidance, so completeness is capped at 3 per the missing-trigger guideline.	3 / 5
Trigger Term Quality	Relevant keywords like 'stack', 'CI/CD pipeline', and 'configs' appear, but common natural synonyms users would say ('GitHub Actions', 'GitLab CI', 'build workflow', 'YAML') are missing, fitting the some-relevant-keywords anchor.	3 / 5
Distinctiveness Conflict Risk	'Detect stack and generate CI/CD pipeline configs' carves a fairly distinct CI/CD niche with minimal overlap risk, though 'pipeline'/'CI/CD' could collide with adjacent devops skills, placing it just below the clear-niche anchor.	4 / 5
	Total	13 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/pipeline/SKILL.md
Commit: 19392f7

Reviewed: ~11 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.