Name: macios-reviewer
Rating: 71.2 (1 reviews)
Author: dotnet

macios-reviewer

Review dotnet/macios PRs against established rules. Trigger on "review this PR", a GitHub PR URL, or code review requests. Checks bindings, MSBuild, nullable, formatting, performance, testing, native runtime code, and Apple platform patterns.

Quality

86%

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

86%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 well-structured, highly actionable review workflow with concrete commands, explicit validation guards, and appropriate offloading of detailed rules to a verified reference file. Minor conciseness trims and an explicit error-recovery loop would make it fully optimal.

Suggestions

Trim motivational prose like 'Even clean PRs have opportunities for improvement — code consolidation, missing edge-case tests, documentation gaps, or binding improvements' to a terse directive, since the constraint is already captured.

Add an explicit error-recovery feedback loop for the CI step (e.g., 'If CI fails, list the failing checks and the likely responsible diff lines before posting') to push workflow_clarity to 5.

Consider moving the inline 'What to look for' priority list into references/review-rules.md if it duplicates content there, keeping the body focused on process.

Dimension	Reasoning	Score
Conciseness	The body is lean and mostly assumes Claude's competence, using concrete commands and tight lists, but a few prose sentences ('Even clean PRs have opportunities for improvement — code consolidation, missing edge-case tests...') could be trimmed without losing actionability, placing it just below the fully lean 5-anchor.	4 / 5
Actionability	Provides copy-paste-ready gh commands with explicit syntax, a concrete JSON issue format, severity markers, a comment-format template, and a categorized list — fully executable guidance covering the common cases per the 5-anchor.	5 / 5
Workflow Clarity	A clearly sequenced 7-step workflow with explicit checkpoints (form an independent assessment before reading the PR description; check CI before posting; 'Never post ✅ LGTM if any required CI check is failing'), but it lacks an explicit error-recovery feedback loop, keeping it just below the 5-anchor.	4 / 5
Progressive Disclosure	SKILL.md serves as a process/workflow overview and offloads the detailed rules to a real, clearly signaled one-level-deep reference ('Read references/review-rules.md from this skill's directory' — verified to exist at 240 lines), matching the well-signaled single-level 5-anchor.	5 / 5
	Total	18 / 20 Passed

Description

87%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 clearly states both what the skill does and when to trigger it, anchored to a narrow niche (dotnet/macios) that minimizes conflict risk. The only gap is action-verb variety and synonym/extension coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain ('Review dotnet/macios PRs against established rules') and lists several concrete check areas ('bindings, MSBuild, nullable, formatting, performance, testing, native runtime code, and Apple platform patterns'), but these are topics under a single 'Checks' verb rather than multiple distinct action verbs, so it falls just below the comprehensive 5-anchor.	4 / 5
Completeness	Explicitly answers both what ('Review dotnet/macios PRs... Checks bindings, MSBuild...') and when ('Trigger on "review this PR", a GitHub PR URL, or code review requests') with concrete trigger phrases, matching the 5-anchor.	5 / 5
Trigger Term Quality	Includes natural trigger phrases a user would actually say ('review this PR', 'a GitHub PR URL', 'code review requests'), giving good keyword coverage, though it lacks synonyms and file/extension variants that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The 'dotnet/macios' niche is highly specific with distinct triggers, making overlap with other skills minimal and clearly matching the clear-niche 5-anchor.	5 / 5
	Total	18 / 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: dotnet/macios
Path: .github/skills/macios-reviewer/SKILL.md
Commit: d259b5f

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