github-agentic-workflows

Authors, reviews, installs, and debugs GitHub Agentic Workflows in repositories, including workflow markdown, frontmatter, gh aw compile and run flows, safe outputs, security guardrails, and operational patterns. Use when creating or maintaining GH-AW automation. Don't use for standard deterministic GitHub Actions YAML, generic CI pipelines, or non-GitHub automation systems.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%Weight 40%Scale 1-5

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

A high-quality, token-efficient procedural skill with executable commands, explicit validation checkpoints, recovery feedback loops, and clean one-level-deep references to a verified bundle. No significant weaknesses across any dimension.

Dimension	Reasoning	Score
Conciseness	Lean and directive throughout with no padding explaining what GitHub Actions or Agentic Workflows are; every step earns its place and assumes Claude's competence.	5 / 5
Actionability	Dense with concrete, copy-paste-ready commands (gh aw validate --strict, gh aw compile --verbose, gh aw trial with the explicit ./ path, gh secret list -R) plus version- and scope-specific gotchas covering the common cases.	5 / 5
Workflow Clarity	A clear six-step sequence with explicit validation checkpoints (validate --strict before ready, recompile after frontmatter changes, verify host secrets before trial) and a dedicated Error Handling section providing validate-fix-retry feedback loops.	5 / 5
Progressive Disclosure	The body is an overview/procedure pointing to well-signaled one-level-deep references (authoring.md, examples.md, security-and-operations.md, troubleshooting.md), an asset template, and a script tool; all referenced paths verified to exist as real bundle files.	5 / 5
	Total	20 / 20 Passed

Description

92%Weight 40%Scale 1-5

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

A strong, specific description that covers what and when clearly and draws a sharp boundary against adjacent skills. The only gap is slightly technical trigger phrasing that misses a few natural synonyms a user might say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Authors, reviews, installs, and debugs') plus enumerated sub-capabilities (workflow markdown, frontmatter, gh aw compile/run, safe outputs, security guardrails, operational patterns), giving comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers what (author/review/install/debug with scope) and when ('Use when creating or maintaining GH-AW automation') with concrete trigger phrasing, and adds a negative boundary for when not to use it.	5 / 5
Trigger Term Quality	Includes a natural trigger phrase ('Use when creating or maintaining GH-AW automation') but leans technical and omits common synonyms or extensions a user might naturally say, so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	A clear niche (GitHub Agentic Workflows) with an explicit exclusion boundary against standard GitHub Actions YAML, generic CI pipelines, and non-GitHub automation, giving minimal conflict risk.	5 / 5
	Total	19 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: webmaxru/ai-native-dev
Path: skills/github-agentic-workflows/SKILL.md
Commit: 0ddb6a6

Reviewed: 1 day 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.