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 reads as a placeholder or auto-generated stub, containing only the skill's identifier and invocation syntax without describing any capabilities, use cases, or trigger conditions.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Manages GitHub Actions CI/CD pipelines, configures workflows, 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, workflow configuration, build failures, deployment automation, or .github/workflows files.'

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

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for ops-cicd-github' is entirely vague and does not describe what the skill actually does.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. It only states it's an 'agent skill' with an invocation command, providing no functional or contextual information.	1 / 3
Trigger Term Quality	The only potentially relevant terms are 'ops', 'cicd', and 'github', but these are embedded in a hyphenated identifier rather than presented as natural keywords a user would say. There are no natural trigger terms like 'CI/CD pipeline', 'GitHub Actions', 'deployment', etc.	1 / 3
Distinctiveness Conflict Risk	The description is so generic that it could conflict with any CI/CD, GitHub, or ops-related skill. There is nothing to distinguish it from other potential skills in the same domain.	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 long YAML frontmatter block that provides no instructional value, while the actual body content is a thin collection of generic best practices and a single basic workflow example. The skill lacks concrete, step-by-step guidance for creating CI/CD pipelines, has no validation checkpoints, and doesn't leverage progressive disclosure to cover the breadth of topics it claims to specialize in.

Suggestions

Remove or drastically reduce the YAML frontmatter and move the actual instructional content into the body with concrete, executable examples for common pipeline patterns (Node.js, Python, Go deployment workflows).

Add a clear step-by-step workflow for creating a pipeline: analyze project type → create workflow file → validate YAML syntax → test with a dry run → iterate on failures.

Replace vague best-practice bullets ('implement proper secret management') with specific, actionable instructions (e.g., show how to use `${{ secrets.MY_SECRET }}` and configure environment protection rules).

Use progressive disclosure by creating separate reference files for advanced topics (e.g., MATRIX_TESTING.md, CACHING.md, COMPOSITE_ACTIONS.md) and linking to them from the main skill.

Dimension	Reasoning	Score
Conciseness	The vast majority of this skill is YAML frontmatter configuration (triggers, hooks, metadata, capabilities, constraints, 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. The skill lists responsibilities and best practices but never sequences them into a process. There are no validation checkpoints (e.g., validating YAML syntax, testing workflows locally with act, verifying deployment). For a task involving creating deployment pipelines, this lack of workflow structure 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 configurations, deployment patterns, matrix strategies, 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/ruflo
Commit: 3d8f171

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.