Name: apply-renovate-prs
Rating: 71.2 (1 reviews)
Author: sivaprasadreddy

apply-renovate-prs

Apply the changes from all open Renovate bot pull requests of a GitHub repository into the local working tree. Use this skill when asked to apply, merge locally, consolidate, batch, or try out Renovate/dependabot-style dependency update PRs so the combined upgrade can be built and tested in one go. This skill only modifies local files; it never commits, pushes, merges, or closes anything on GitHub.

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

85%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 highly actionable, well-sequenced procedural skill with strong validation feedback loops. Its main weakness is progressive disclosure: substantial detail is inlined in SKILL.md with no external reference files to offload it.

Suggestions

Move the per-ecosystem lockfile regeneration table and the TestcontainersConfig special-case examples into a reference file (e.g. references/special-cases.md) and link to it from step 5/6 to reduce inline bulk.

Extract the .sdkmanrc and Docker-image companion-edit rules into a short references/companion-edits.md, keeping only the decision summary in the body.

Tighten the special-cases prose by replacing explanatory sentences with imperative rules, cutting tokens without losing the executable guidance.

Dimension	Reasoning	Score
Conciseness	Dense, procedural, and free of padding about what Renovate/GitHub is, though some special-case prose and example literals (e.g. Java Testcontainers declarations) could be tightened; sits above the 'mostly efficient' anchor but not at fully lean.	4 / 5
Actionability	Provides fully executable, copy-paste-ready gh/git commands, a per-ecosystem lockfile regeneration table, concrete grep patterns, and real code examples covering the common cases.	5 / 5
Workflow Clarity	An 8-step sequenced workflow with explicit validation checkpoints (conflict-marker grep, git status, build/test feedback loop) and error-recovery paths; the batch/destructive-operation validation cap is satisfied, so it is not capped.	5 / 5
Progressive Disclosure	Well-sectioned and self-contained, but with no bundle files all ~270 lines are inlined, including the lockfile regen table, Testcontainers Java literals, and .sdkmanrc rules that could plausibly live in reference files; structure is good but content that could be separate is inline.	3 / 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.

A strong, specific description that clearly states what it does and when to use it, with natural trigger terms and a distinct niche. Minor additional concrete-action enumeration is the only gap.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("Apply the changes", "into the local working tree", "built and tested in one go") with an explicit scope boundary, but does not enumerate a broad set of distinct actions, so it sits below the comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both what ("Apply the changes from all open Renovate bot pull requests...into the local working tree") and when ("Use this skill when asked to apply, merge locally, consolidate, batch, or try out...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases users would say ("apply, merge locally, consolidate, batch, or try out", "Renovate/dependabot-style dependency update PRs") give good coverage with synonyms, missing only a few broader variations.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Renovate/dependabot PRs applied locally) with distinct triggers and minimal overlap with unrelated 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: sivaprasadreddy/sivalabs-agent-skills
Path: skills/apply-renovate-prs/SKILL.md
Commit: 031ea5c

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.