CtrlK
BlogDocsLog inGet started
Tessl Logo

lirantal/gh-bulk-repo-edit

Perform identical, surgical edits across many GitHub repositories without cloning them locally — using the `gh` CLI's Contents API to read files, create branches, commit changes, and open PRs in bulk. Use this skill whenever the user wants to make the same small change (update a README, remove a deprecated badge, fix a link, bump a config) across more than a handful of repos they own or maintain. Trigger this skill on phrases like "across all my repos", "in each of these repos", "bulk update", "open PRs for all of them", "without cloning", "deprecated X in many repos", or any task where the work is mechanically identical and spans 5+ repositories. Even when the user describes the task in domain terms (e.g. "the Snyk badge is deprecated everywhere") rather than "multi-repo edit", trigger this skill — it's the right tool whenever cloning N repos to make a one-line change would be wasteful.

72

Quality

90%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with an excellent, well-validated workflow, but loses points on conciseness and progressive disclosure because the SKILL.md is a long monolithic document with extensive inline examples and pitfalls rather than a lean overview deferring detail to reference files.

Suggestions

Move the longer worked examples (dependabot YAML edits, webhook audit) and selected Pitfalls entries into reference files, keeping SKILL.md as a lean overview that links out — this would lift both conciseness and progressive_disclosure.

Tighten the Phase 2.5 CI-triage prose and the "Pitfalls" list to the highest-impact items; several entries repeat guidance or run long and could be condensed without losing signal.

Consider extracting the full "Recommended script structure" template detail into references/script-template.sh and summarizing only its key invariants in SKILL.md.

DimensionReasoningScore

Conciseness

The body is accurate and high-signal, but lengthy — extensive worked examples (dependabot YAML, webhook audit, CI triage) and a long "Pitfalls" section make it more verbose than the rubric's lean top anchor, even though it mostly avoids explaining concepts Claude already knows.

2 / 3

Actionability

Provides fully executable `gh api` calls, a complete bash script template, exact jq filters, and copy-paste-ready transform snippets — concrete and copy-paste ready throughout.

3 / 3

Workflow Clarity

A clear three-phase sequence (Scan → Verify → Apply) with explicit validation checkpoints (sample approval gate, smoke-test + CI green, refetch-then-commit, sanity-check, continue-on-error) and feedback loops for batch/destructive operations.

3 / 3

Progressive Disclosure

The overview points to two real, clearly-signaled one-level-deep references (api-recipes.md, script-template.sh) that exist on disk, but the body itself is a large monolithic doc with many inline worked examples and pitfalls that could live in reference files.

2 / 3

Total

10

/

12

Passed

Description

100%

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 with explicit capability listing, natural trigger terms, and a clear when-to-use clause. Its only weakness is verbosity relative to the concise examples in the rubric, but the description rubric has no conciseness dimension so all dimensions score at the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "read files, create branches, commit changes, and open PRs in bulk" — plus specific example edits ("update a README, remove a deprecated badge, fix a link, bump a config"), matching the top anchor for listing multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (identical surgical edits via the Contents API) and when via an explicit "Use this skill whenever..." trigger clause plus concrete trigger phrases, satisfying the top anchor.

3 / 3

Trigger Term Quality

Includes a rich set of natural phrases users would actually say — "across all my repos", "bulk update", "open PRs for all of them", "without cloning", "deprecated X in many repos" — giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — bulk multi-repo edits without cloning — with distinct, specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents