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 critically deficient across all dimensions. It provides no information about what the skill does, when it should be used, or what user requests should trigger it. It reads as a placeholder rather than a functional description.

Suggestions

Add concrete actions the skill performs, 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, automated testing, or workflow configuration.'

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

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. The description is essentially just an invocation instruction with no functional or contextual information.	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 'workflow'.	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 contains configuration metadata, hooks, and examples that don't serve as actionable instructions. The actual body content is a thin collection of generic best practices and a single basic workflow example. It lacks concrete multi-step guidance, validation checkpoints, and any progressive disclosure structure for the complex domain of CI/CD pipeline engineering.

Suggestions

Remove or drastically reduce the YAML frontmatter and move actionable content into the body — the hooks, examples, and configuration metadata are not useful instruction content.

Add a clear multi-step workflow for creating a CI/CD pipeline (e.g., 1. Analyze project type, 2. Create workflow file, 3. Validate YAML syntax with `actionlint` or similar, 4. Verify job dependencies, 5. Test with a dry run).

Replace generic bullet points like 'implement proper secret management' with concrete examples showing `${{ secrets.MY_SECRET }}` usage, environment protection rules configuration, and GITHUB_TOKEN permission scoping.

Add progressive disclosure by referencing separate files for advanced topics (e.g., MATRIX_TESTING.md, DEPLOYMENT_STRATEGIES.md, COMPOSITE_ACTIONS.md) rather than listing everything superficially.

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 syntax, how to test locally with act, how to verify deployments). For a skill involving potentially destructive deployment workflows, the absence of any verification 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/ruflo
Commit: 398f7c2

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.