CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-prs

Review recent BuilderIO/agent-native human pull requests, approve eligible internal PRs, and identify PRs ready for the user's final decision. Outside Factory governance, merge only when the user explicitly requests it for that PR. Factory governance is approval-only. Use for scheduled or manual PR sweeps; flag external work needing a major product call or new framework API, and unresolved major product or UX decisions, to a maintainer.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/review-prs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 an unusually rigorous governance policy with excellent validation checkpoints and mostly executable commands, but it pays for that rigor in redundancy: key rules are restated across many sections and the whole policy lives in a single monolithic file with no progressive disclosure. Tightening the repetition and splitting detailed policies into reference files would materially improve it.

Suggestions

Deduplicate the repeated non-waivable-gate lists, Factory-vs-manual restrictions, and thread-silence rules into one authoritative section that other sections reference instead of restating, which should cut the body's length substantially.

Split the detailed material into one-level-deep reference files (e.g., owner/doc exception policies, the merge gate and queue procedures, and reply-drafting rules), keeping SKILL.md as a concise decision-flow overview with clearly signaled links.

Specify the exact membership verification command (e.g., `gh api orgs/BuilderIO/memberships/<login>`) since it is required at multiple decision points, and either add `scripts/agent-friction-report.mjs` to the bundle or remove the reference to it.

DimensionReasoningScore

Conciseness

The ~750-line body restates the same policies many times: the non-waivable-gate list ("does not waive … the ultra-scary safety gate … the independent-review requirement for PRs changing review or approval policy …") appears nearly verbatim in at least four sections, "Factory governance never merges" and the external-author approval prohibition repeat throughout, and the thread-silence rule is stated three or more times. It is not a 1 because the text is operational policy rather than explanations of concepts Claude already knows, but the padding and repetition are substantial.

2 / 5

Actionability

Guidance is mostly executable with concrete commands: the paginated rulesets query (`gh api --paginate 'repos/BuilderIO/agent-native/rulesets?includes_parents=true'`), the pinned approval procedure (`event=APPROVE` and `commit_id=$reviewed_head_sha` with response verification), guarded merges (`gh pr merge <number> … --squash --admin --match-head-commit <verified-head-oid>`), the dequeue GraphQL mutation, and recap/reply templates. It is not a 5 because the repeatedly required "organization membership API" is never given as a concrete command, and `scripts/agent-friction-report.mjs` is referenced but does not exist in the bundle.

4 / 5

Workflow Clarity

The pipeline (selection → author/external gates → evidence sweep → approval → readiness → merge → recap) is sequenced with exceptional validation checkpoints: membership verification, re-reading the live head before acting, verifying the returned `commit_id`, the 10-minute stable-head gate with explicit reset causes, dequeuing stale entries, and verifying the merge commit is an ancestor of `origin/main`. It is not a 5 because the Factory-vs-manual branching is scattered across roughly eight sections, so a single flow (e.g., handling a fork PR) must be reassembled from fragments.

4 / 5

Progressive Disclosure

There are no bundle files at all — everything, including per-owner exception policies, merge-gate and queue procedures, and reply-drafting rules that clearly belong in separate reference files, is inlined in one 750-line SKILL.md. It is not a 2 because the section headers do provide navigable structure, matching the anchor "content that should be separate is inline"; it is not a 4 because a skill of this size should split its detailed policy material into well-signaled one-level-deep references.

3 / 5

Total

13

/

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 description: third-person voice, concrete repo-scoped actions, an explicit "Use for" trigger clause, and a distinct niche that is unlikely to fire for the wrong skill. The only weakness is moderate keyword synonym coverage, which could include more natural phrasings users might say.

DimensionReasoningScore

Specificity

The description lists multiple concrete, repo-scoped actions — "Review recent BuilderIO/agent-native human pull requests, approve eligible internal PRs, and identify PRs ready for the user's final decision", plus conditional merging ("merge only when the user explicitly requests it for that PR") and escalation ("flag external work needing a major product call or new framework API … to a maintainer") — comprehensively covering the skill's capabilities. It is not a 4 because there are no meaningful gaps in the action coverage.

5 / 5

Completeness

The "what" is explicit ("Review … pull requests, approve eligible internal PRs, and identify PRs ready for the user's final decision") and the "when" is an explicit trigger clause with concrete phrases ("Use for scheduled or manual PR sweeps"). It is not a 4 because the when-clause is specific and concrete, not merely present or weakly implied.

5 / 5

Trigger Term Quality

Natural keywords users would say are present: "pull requests", "PRs", "PR sweeps", "approve", "merge", "scheduled or manual". It is not a 5 because common variations such as "code review", "check PRs", or "open PRs" are missing, leaving keyword coverage good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The description is tightly scoped to "BuilderIO/agent-native", "human pull requests", "Factory governance", and "PR sweeps" — a clear niche with distinct triggers and minimal conflict risk against generic review or merge skills. It matches the top anchor: a clear niche with distinct triggers.

5 / 5

Total

19

/

20

Passed

Validation

62%

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

Validation — 10 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (766 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

10

/

16

Passed

Repository

BuilderIO/agent-native

Path

.agents/skills/review-prs/SKILL.md

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.