CtrlK
BlogDocsLog inGet started
Tessl Logo

dependabot-stack

Group all open Dependabot PRs on a repository into a single ordered stack using gh-stack. Run weekly, after Dependabot's batch of grouped-update PRs lands. Use when asked to stack, organize, or clean up Dependabot PRs.

71

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 a tightly written, fully executable multi-step workflow with strong validation checkpoints for its destructive operations. It could split some reference material into bundle files and trim a little explanatory prose, but otherwise earns its tokens.

DimensionReasoningScore

Conciseness

The body is efficient and dominated by executable commands with minimal padding, but it carries several explanatory prose paragraphs (e.g. the rationale for excluding major bumps) that, while justified, could be trimmed slightly, placing it just below fully lean.

4 / 5

Actionability

Every step ships copy-paste-ready bash with real flags and a concrete ordered-list example, covering the common cases fully; placeholders like <branch-1> are inherent to the task rather than pseudocode.

5 / 5

Workflow Clarity

A clear Step 0-5 sequence with explicit validation checkpoints (stop on 0-1 PRs, stop and resolve on rebase conflict, a Verify section) and feedback loops for the destructive force-push/rebase operations, satisfying the batch/destructive validation requirement.

5 / 5

Progressive Disclosure

The content is well-organized into clearly signaled sections with no deep nesting, but no bundle files exist and all material is inline in a ~150-line file; structure is good though a couple of sections (ordering rules, conflict resolution) could optionally be split out.

4 / 5

Total

18

/

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 specific, third-person, and clearly answers both what the skill does and when to invoke it, with concrete trigger phrases. Its only soft spot is enumerating one primary action rather than multiple distinct capabilities.

DimensionReasoningScore

Specificity

Names the domain and a concrete action ("Group all open Dependabot PRs ... into a single ordered stack using gh-stack") with the specific tool; it is more concrete than a single generic action but only one main action is enumerated, so it sits just below comprehensive coverage.

4 / 5

Completeness

It explicitly answers both 'what' (group Dependabot PRs into one ordered stack) and 'when' ("Use when asked to stack, organize, or clean up Dependabot PRs" plus a weekly cadence note), matching the explicit what-and-when anchor.

5 / 5

Trigger Term Quality

Natural user phrases are present ("stack, organize, or clean up Dependabot PRs") alongside the tool name; good coverage with a few synonymous phrasings a user might say missing, fitting the 'a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The Dependabot + gh-stack niche is narrow with distinct triggers ("Dependabot PRs", "stack"), giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

18

/

20

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
RoleModel/rolemodel-skills
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.