agent-ops-cicd-github

Agent skill for ops-cicd-github - invoke with $agent-ops-cicd-github

1.00x

Quality

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-ops-cicd-github/SKILL.md

Quality

Discovery

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

This description is essentially a placeholder that provides no useful information about the skill's capabilities or when it should be selected. It fails on every dimension: no concrete actions, no natural trigger terms, no 'what' or 'when' guidance, and no distinguishing details. It would be nearly impossible for Claude to correctly select this skill from a list of available skills.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Configures GitHub Actions workflows, manages CI/CD pipelines, sets up automated deployments and testing.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about GitHub Actions, CI/CD pipelines, continuous integration, continuous deployment, build automation, or workflow configuration.'

Remove the invocation syntax ('invoke with $agent-ops-cicd-github') from the description and replace it with capability-focused language that helps Claude distinguish this skill from other DevOps or GitHub-related skills.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. It only names a tool invocation pattern ('invoke with $agent-ops-cicd-github') without describing what the skill actually does.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause and no description of capabilities.	1 / 3
Trigger Term Quality	The only potentially relevant terms are 'ops', 'cicd', and 'github' buried in a hyphenated identifier. There are no natural language keywords a user would say, such as 'CI/CD pipeline', 'GitHub Actions', 'deployment', or 'continuous integration'.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it could overlap with any ops, CI/CD, or GitHub-related skill. There are no distinct triggers or scoping details to differentiate it.	1 / 3
	Total	4 / 12 Passed

Implementation

14%

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

This skill is dominated by an extremely large YAML frontmatter block that constitutes most of the file, while the actual instructional body is thin and generic. The content lists responsibilities and best practices Claude already knows without providing concrete, step-by-step guidance for creating or optimizing CI/CD pipelines. It lacks validation workflows, error recovery steps, and progressive disclosure to more detailed resources.

Suggestions

Replace generic bullet points ('implement proper secret management', 'cache dependencies effectively') with concrete, executable examples showing specific configurations for each practice.

Add a clear multi-step workflow for creating a CI/CD pipeline: e.g., 1) Detect project type, 2) Generate workflow file, 3) Validate YAML syntax with a specific tool/command, 4) Verify job dependencies, 5) Confirm with user before committing.

Split advanced topics (matrix strategies, composite actions, deployment patterns, security hardening) into separate referenced files to keep the main skill lean and navigable.

Remove or drastically reduce the YAML frontmatter — most of it (hooks, optimization, integration, examples) is not standard SKILL.md content and adds no actionable value to the body instructions.

Dimension	Reasoning	Score
Conciseness	The vast majority of the file is YAML frontmatter configuration (triggers, hooks, capabilities, constraints, integration, optimization, examples, etc.) that is not actionable instruction content. The actual body content is thin and padded with generic best practices Claude already knows (e.g., 'never hardcode secrets', 'use appropriate runners'). The responsibilities list is vague filler.	1 / 3
Actionability	There is one concrete, executable YAML workflow example which is helpful, but the rest of the guidance is abstract bullet points like 'implement proper secret management' and 'cache dependencies effectively' without specific commands or configurations. The example is a basic starter template rather than covering the claimed specializations.	2 / 3
Workflow Clarity	There is no clear multi-step workflow for creating or modifying CI/CD pipelines. No validation steps are provided (e.g., how to validate workflow YAML, how to test locally with act, how to verify deployments). For a skill involving potentially destructive production deployment workflows, the absence of any validation or feedback loop is a significant gap.	1 / 3
Progressive Disclosure	The content is a monolithic mix of massive YAML frontmatter and a short body with no references to external files for advanced topics like security hardening, deployment strategies, matrix configurations, or composite actions. Everything is either superficially mentioned inline or not covered at all.	1 / 3
	Total	5 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/claude-flow
Commit: 01070ed

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