CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cicd-automation-workflow-automate

Design efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes that reduce manual work and accelerate delivery while maintaining quality and security. Use when creating or improving build, test, and deployment automation.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/cicd-automation-workflow-automate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 well-organized with sensible Use/Do-not-use and Safety sections, but it stays at the level of high-level directives: no executable examples, no validation checkpoints, and a dangling reference to a nonexistent playbook. The persona/Context sections also duplicate the description without adding guidance.

Suggestions

Fix the broken reference: either create resources/implementation-playbook.md with the promised workflow patterns and examples, or remove the references to it in Instructions and Resources.

Replace the redundant persona paragraph and vague Context/Requirements sections with concrete guidance, such as a minimal example GitHub Actions workflow with caching, artifacts, and a quality-gate job.

Add validation checkpoints to the workflow, e.g., lint workflow files (actionlint), run the pipeline on a branch before touching the default branch, and verify the rollback plan before recommending deployment.

DimensionReasoningScore

Conciseness

Mostly lean, but the opening persona paragraph restates the frontmatter description nearly verbatim and the 'Context' and 'Requirements' sections ('Focus on creating reliable, maintainable automation that handles edge cases...', 'Take the requirements, target, and scope from the user's request') are content-free filler — more than the 'minor instances' anchor 4 allows.

3 / 5

Actionability

Instructions such as 'Define pipeline stages with caching, artifacts, and quality gates' and 'Add security scans, secret handling, and approvals for risky steps' are concrete directives, but there are no commands, workflow snippets, or examples, and the referenced playbook containing the patterns does not exist — matching anchor 3's 'concrete guidance but incomplete'.

3 / 5

Workflow Clarity

A rough sequence is present (inventory -> define stages -> add security -> document rollout/rollback), but the steps are unnumbered bullets with no validation checkpoints or feedback loops (e.g., linting the workflow or dry-running a deploy), matching anchor 3 rather than 4.

3 / 5

Progressive Disclosure

Section structure is good and the reference is clearly signaled one level deep (dedicated Resources section plus an inline pointer), but the sole referenced file 'resources/implementation-playbook.md' does not exist in the bundle — the reference is broken, so navigation fails and the score cannot reach 4-5.

3 / 5

Total

12

/

20

Passed

Description

78%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.

A strong description with an explicit and specific 'Use when' clause and natural trigger terms covering the core CI/CD vocabulary. Its main weakness is buzzword-laden purpose language ('reduce manual work and accelerate delivery while maintaining quality and security') that pads the capability statement without adding concrete actions.

DimensionReasoningScore

Specificity

Names the domain with concrete actions ('Design efficient CI/CD pipelines, GitHub Actions workflows'), but 'automated development processes' is generic and 'reduce manual work and accelerate delivery while maintaining quality and security' is buzzword purpose-language rather than a capability — anchor 3 fits better than 4, which expects several distinct concrete actions.

3 / 5

Completeness

Explicitly answers both 'what' (design CI/CD pipelines, GitHub Actions workflows, automated dev processes) and 'when' with concrete triggers ('Use when creating or improving build, test, and deployment automation'), matching anchor 5; the when-clause is already specific, so anchor 4's 'could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Includes natural terms users would say — 'CI/CD', 'GitHub Actions', 'build, test, and deployment automation' — matching anchor 4; not 5 because common variants like 'DevOps', 'release pipeline', or 'workflow automation' are absent.

4 / 5

Distinctiveness Conflict Risk

The CI/CD / GitHub Actions niche is mostly distinct with clear triggers, but there is minor overlap risk with general GitHub or DevOps-adjacent skills, matching anchor 4 rather than 5's 'minimal conflict risk'.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/cicd-automation-workflow-automate/SKILL.md

Reviewed

Table of Contents

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.