github-operations

Full contribution lifecycle: branch naming, conventional commits, GitHub issues, PRs, Actions, and releases. MCP-first with gh CLI fallback. USE FOR: commit, push, PR, branch, issue, release, GitHub operations. DO NOT USE FOR: Azure infrastructure, Bicep/Terraform code, architecture decisions.

Quality

92%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Discovery

100%

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 a strong skill description that covers all key dimensions well. It provides specific actions, natural trigger terms, explicit use/don't-use guidance, and clear boundaries to avoid conflicts with related skills. The inclusion of both positive and negative trigger guidance is particularly effective for skill selection in a large skill library.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: branch naming, conventional commits, GitHub issues, PRs, Actions, and releases. Also specifies the tooling approach (MCP-first with gh CLI fallback).	3 / 3
Completeness	Clearly answers both 'what' (full contribution lifecycle with specific actions) and 'when' (explicit USE FOR and DO NOT USE FOR clauses providing clear trigger guidance and boundary conditions).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: 'commit', 'push', 'PR', 'branch', 'issue', 'release', 'GitHub operations'. These are exactly the words developers use in daily workflow.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with explicit negative boundaries ('DO NOT USE FOR: Azure infrastructure, Bicep/Terraform code, architecture decisions') that prevent conflicts with infrastructure or architecture skills. The GitHub-specific focus creates a clear niche.	3 / 3
	Total	12 / 12 Passed

Implementation

85%

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

This is a well-structured skill that covers a complex multi-step workflow with clear sequencing, concrete tool references, and appropriate progressive disclosure to reference files. The actionability is strong with specific MCP tool names, CLI commands, and required parameters. Minor weaknesses include some redundancy between sections (Smart PR Flow appears twice, DO/DON'T partially restates earlier guidance) and the Devcontainer Reliability Rule feels somewhat niche for the main skill file.

Dimension	Reasoning	Score
Conciseness	Generally efficient with good use of tables and structured formatting, but some sections are slightly redundant (e.g., Smart PR Flow appears both in the reference index and as its own section, the MCP Priority Protocol restates what's already implied). The DO/DON'T section partially repeats guidance from earlier sections.	2 / 3
Actionability	Provides concrete tool names, exact CLI commands, required parameters for PR/issue creation, specific branch naming patterns, and clear validation commands (e.g., `git rev-parse --abbrev-ref HEAD`, `git branch -m`). The MCP tool tables with exact function names are directly usable.	3 / 3
Workflow Clarity	The contribution lifecycle is clearly sequenced at the top, with explicit validation checkpoints throughout: branch name validation before commits, pre-flight checks before PR creation, scope verification for domain branches, and a clear 'stop and fix' instruction for invalid branch names. The MCP-first fallback protocol is well-defined.	3 / 3
Progressive Disclosure	Excellent structure with a clear overview in the main file and well-signaled one-level-deep references to four specific reference files (branch-strategy.md, commit-conventions.md, smart-pr-flow.md, detailed-commands.md). The reference index table at the bottom provides easy navigation, and each section includes just enough detail to be actionable without overloading.	3 / 3
	Total	11 / 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: jonathan-vella/azure-agentic-infraops
Commit: ec7b8ff

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.