CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

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.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is macios-reviewer in dotnet/macios

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

The content is a high-quality PR-review workflow with concrete commands, a real one-level reference, and explicit validation feedback loops. Its main limitation is that the actionable review heuristics are deferred to the reference file while a fair amount of inline priority/constraint detail remains in the overview.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explanations of what a PR or binding is), though sections like the 9-item prioritized list and the constraints block could be tightened slightly; minor over-explanation in the Copilot prefix note keeps it just below 5.

4 / 5

Actionability

Provides concrete, executable `gh` commands, a JSON issue schema, and an exact comment format template; the "Load review rules" step points to a real reference file (references/review-rules.md), but the actual review heuristics live in that reference rather than being copy-paste executable inline, leaving minor gaps.

4 / 5

Workflow Clarity

A clearly sequenced 7-step workflow with explicit validation checkpoints: form an independent assessment before reading the PR narrative (step 2), reconcile claims against evidence in step 3, verify CI before posting (step 4), and the constraint "Never post ✅ LGTM if any required CI check is failing" closes the feedback loop.

5 / 5

Progressive Disclosure

The SKILL.md body is a well-organized overview that offloads the bulky rule catalog to a single one-level-deep reference (references/review-rules.md, confirmed present), but the body still inlines substantial review-priority and constraint material that could arguably live in the reference, keeping it just below the score-5 anchor.

4 / 5

Total

17

/

20

Passed

Description

83%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.

The description is strong: it names a specific repo, lists concrete review domains, and gives explicit trigger phrases. It is concise and distinct, with only minor specificity gaps in how each review domain translates to concrete actions.

DimensionReasoningScore

Specificity

Lists several concrete review domains ("bindings, MSBuild, nullable, formatting, performance, testing, native runtime code, and Apple platform patterns") but each is a category rather than a discrete action verb, leaving minor coverage gaps versus the score-5 anchor's enumerated actions.

4 / 5

Completeness

Explicitly states what it does ("Review dotnet/macios PRs against established rules") and provides a 'when' clause ("Trigger on..."); the 'when' is concrete but lists only trigger formats rather than richer situational triggers, so it sits just below the score-5 anchor.

4 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ("review this PR", "GitHub PR URL", "code review requests") plus the concrete repo target, giving comprehensive coverage of likely phrasings.

5 / 5

Distinctiveness Conflict Risk

The narrow repo-specific target ("dotnet/macios") and Apple-platform/binding terminology create a clear niche with minimal overlap risk against generic review skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dotnet/macios
Reviewed

Table of Contents

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.