agent-ops-cicd-github

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

1.00x

Quality

18%

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 critically deficient across all dimensions. It provides only a skill name and invocation command without any explanation of capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a list of available skills.

Suggestions

Add concrete actions describing what the skill does (e.g., 'Creates and manages GitHub Actions workflows, configures CI/CD pipelines, sets up automated testing and deployment')

Include a 'Use when...' clause with natural trigger terms (e.g., 'Use when the user mentions GitHub Actions, CI/CD pipelines, automated deployment, workflow configuration, or continuous integration')

Remove the invocation syntax from the description and replace with functional content that helps Claude understand the skill's purpose

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for ops-cicd-github' is completely abstract and doesn't describe what the skill actually does.	1 / 3
Completeness	Missing both 'what does this do' and 'when should Claude use it'. The description only provides an invocation command, not any functional information or usage triggers.	1 / 3
Trigger Term Quality	Contains only technical jargon ('ops-cicd-github', '$agent-ops-cicd-github') that users would never naturally say. No natural keywords like 'CI/CD', 'pipeline', 'deployment', 'GitHub Actions', or 'workflow'.	1 / 3
Distinctiveness Conflict Risk	While the name 'ops-cicd-github' hints at a specific domain, the lack of any actual description means Claude cannot distinguish when to use this versus other DevOps or GitHub-related skills.	1 / 3
	Total	4 / 12 Passed

Implementation

37%

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

The skill provides a basic foundation for GitHub Actions work with one concrete example, but lacks the depth and workflow clarity needed for reliable pipeline creation. It lists responsibilities and best practices that Claude already knows, while missing actionable multi-step guidance and validation checkpoints for the actual pipeline creation process.

Suggestions

Add a clear numbered workflow for creating pipelines: 1) Analyze project type, 2) Create workflow file, 3) Validate YAML syntax with specific command, 4) Test workflow locally with act, 5) Verify on push

Replace generic best practices with specific, executable patterns for common scenarios (deployment to different environments, matrix testing, caching strategies)

Add validation checkpoint: include specific command to validate workflow syntax before committing (e.g., using actionlint or yamllint)

Remove explanatory content Claude already knows (what GitHub Actions is, generic advice like 'use appropriate runners') and replace with project-specific workflow templates

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some unnecessary explanation (e.g., 'You are a GitHub CI/CD Pipeline Engineer' is redundant given the context). The best practices list contains items Claude already knows (like 'use appropriate runners').	2 / 3
Actionability	Provides one concrete workflow example that is executable, but the guidance is mostly high-level bullet points rather than specific, copy-paste ready patterns for different scenarios. The example is basic and doesn't cover the deployment stage mentioned in responsibilities.	2 / 3
Workflow Clarity	No clear multi-step process for creating pipelines. Lists responsibilities but doesn't sequence them. Missing validation steps for workflow syntax checking, no feedback loops for error recovery when workflows fail validation.	1 / 3
Progressive Disclosure	Content is reasonably organized with sections, but everything is inline in one file. Could benefit from references to separate files for different workflow patterns (Node.js, Python, Go) mentioned in the hooks but not provided as examples.	2 / 3
	Total	7 / 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: b2618f9

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.