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 is an extremely weak description that provides virtually no useful information for skill selection. It only names the skill and its invocation command without describing any capabilities, use cases, or trigger conditions. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills based on this description alone.

Suggestions

Add concrete actions the skill performs, e.g., 'Manages GitHub Actions workflows, configures CI/CD pipelines, monitors build status, and troubleshoots deployment failures.'

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

Remove the invocation instruction ('invoke with $agent-ops-cicd-github') from the description and replace it with capability and trigger information that helps Claude decide when to select this skill.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. It only states it's an 'agent skill' and provides an invocation command, with no indication of what the skill actually does.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance.	1 / 3
Trigger Term Quality	The only potentially relevant terms are 'ops', 'cicd', and 'github' embedded in the skill name, but these are not presented as natural keywords a user would say. There are no natural trigger terms like 'pipeline', 'deploy', 'CI/CD', 'GitHub Actions', 'workflow', etc.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it provides no clear niche. While the name hints at GitHub CI/CD operations, the description itself offers nothing to distinguish it from any other ops, CI/CD, or GitHub-related skill.	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 verbose YAML frontmatter block that provides no actionable value to Claude, while the actual body content is thin and generic. The best practices and responsibilities listed are things Claude already knows, and the single workflow example, while concrete, is insufficient to guide complex CI/CD pipeline creation. The skill lacks workflow sequencing, validation steps, and any progressive disclosure structure.

Suggestions

Remove or drastically reduce the YAML frontmatter and focus the body on actionable, specific guidance that Claude doesn't already know (e.g., project-specific conventions, non-obvious patterns, common pitfalls).

Add a clear multi-step workflow for creating pipelines: e.g., 1) Detect project type, 2) Generate workflow file, 3) Validate YAML syntax with a specific command, 4) Verify required secrets are documented.

Provide multiple concrete, executable workflow examples for different project types (Node.js, Python, Go) with specific configurations rather than generic best practice bullets.

Split advanced topics (matrix strategies, composite actions, environment protection rules) into referenced files and add a navigation section in the body.

Dimension	Reasoning	Score
Conciseness	The vast majority of the file is YAML frontmatter configuration that is not actionable skill content. The actual body content is mostly a list of vague best practices and responsibilities that Claude already knows. Bullet points like 'Use appropriate runners (ubuntu-latest, etc.)' and 'Never hardcode secrets' are things Claude inherently understands.	1 / 3
Actionability	There is one concrete, executable YAML workflow example which is helpful, but the rest of the content is vague guidance ('Implement proper secret management', 'Cache dependencies effectively') without specific commands, configurations, or copy-paste ready examples for those topics.	2 / 3
Workflow Clarity	There is no clear multi-step workflow for creating or modifying CI/CD pipelines. The 'Key responsibilities' are listed without sequencing, and there are no validation checkpoints or feedback loops for verifying workflow correctness (e.g., validating YAML syntax, testing workflows locally with act).	1 / 3
Progressive Disclosure	The content is a monolithic mix of massive YAML frontmatter and a short body with no references to supporting files. There is no separation of concerns—security considerations, workflow patterns, and best practices are all crammed together without navigation or external references for deeper topics.	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: 9d4a9ea

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