Name: gentle-ai-collab-perfect
Rating: 69.6 (1 reviews)
Author: Gentleman-Programming

gentle-ai-collab-perfect

Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the contribution flow is in scope: opening an issue, drafting or editing a PR body, splitting a change into chained/stacked PRs, or auditing a PR before requesting review.

Quality

84%

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

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 body is highly actionable and workflow-clear with concrete commands, regexes, and validation checkpoints, and it is well-structured with clearly signaled references. Its main weakness is conciseness: the honesty and scope rules are restated across six sections and could be consolidated.

Suggestions

Consolidate the PR-body honesty rules: state them once in 'PR body honesty' and reference that section from 'Hard rules', 'Anti-patterns', and the self-audit checklist instead of restating each rule.

Merge the 'Source of truth' table and the 'References' section into a single source/reference list to remove the duplicated file enumeration.

Trim the 'How to apply this skill' section, which largely rephrases rules already given in 'Hard rules' and 'Contributor vs maintainer scope'.

Dimension	Reasoning	Score
Conciseness	The body is dense and domain-specific rather than padding basic concepts, but the same honesty/scope rules recur across 'Hard rules', 'PR workflow', 'PR body honesty', 'Standard honest-rewrite pattern', 'Anti-patterns', and the self-audit checklist, so it could be tightened considerably.	3 / 5
Actionability	Provides copy-paste-ready gh/git commands with exact JSON field lists, concrete branch-name and title regexes, and filled-in PR body section templates covering the common contribution cases.	5 / 5
Workflow Clarity	The PR workflow is a clear numbered sequence with explicit validation checkpoints (local validation, post-open `gh pr checks`), a verification protocol with feedback loops, and a pre-PR self-audit checklist for a process with label/permission mutations.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections with one-level-deep references to repo source files (CONTRIBUTING.md, skills/*/SKILL.md) and a dedicated References block; the only gap is redundancy between the 'Source of truth' table and the 'References' section, and no bundle files exist to offload detail.	4 / 5
	Total	17 / 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.

The description is well-constructed: it states concrete capabilities, provides an explicit repo-scoped load trigger with natural contributor phrases, and is tightly scoped to avoid conflicts. Minor improvement is possible by framing capabilities as verbs and adding a couple of common synonyms.

Dimension	Reasoning	Score
Specificity	Lists several specific capabilities ('Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage') but they read as domain topics rather than crisp verb-based actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' (the enumerated contribution capabilities) and 'when' ('Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the contribution flow is in scope: ...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural contributor phrases ('opening an issue', 'drafting or editing a PR body', 'chained/stacked PRs', 'auditing a PR before requesting review') with the chained/stacked synonym pair, though a few common variations are absent.	4 / 5
Distinctiveness Conflict Risk	Scoped to a single named repo and the external-collaborator role, giving it a clear niche with distinct triggers and minimal conflict risk with other skills.	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: Gentleman-Programming/gentle-ai
Path: skills/gentle-ai-collab-perfect/SKILL.md
Commit: 71cf25f

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