CtrlK
BlogDocsLog inGet started
Tessl Logo

warp-closing-issue

Use when the user provides Warp commit SHA(s) and GitHub issue number(s) to assess, draft issue comments, post progress updates, or recommend whether issue threads should stay open or close.

75

Quality

92%

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

85%Weight 40%Scale 1-3

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

A well-structured, highly actionable workflow skill with clear sequencing and validation checkpoints and appropriate one-level-deep reference splitting. Its main weakness is verbosity from redundant restating of key rules across sections.

Suggestions

Consolidate the repeated gh api body=@file prohibition: state it once in Hard Rules and reference it from Red Flags and commands.md rather than re-explaining in each place.

Trim the Public API behavior worked example (the cuBQL block) to a shorter illustration or move it into commands.md, keeping the SKILL.md body leaner.

Consider folding the probe 'Avoid' bullets into the 'Prefer' bullets as a single compact list to reduce duplicated framing.

DimensionReasoningScore

Conciseness

The body is dense and information-rich but long; while mostly efficient and free of obvious concept re-explanation, the repeated restating of rules (e.g. the gh api body=@file prohibition appears in Hard Rules, Red Flags, and commands.md) and elaborate sectioning could be tightened to respect the token budget.

2 / 3

Actionability

It provides concrete executable guidance: exact gh/git commands and shell snippets in commands.md, a fill-in draft template, comment-shape blocks, and specific classification tables, all copy-paste ready.

3 / 3

Workflow Clarity

A numbered nine-step Checklist sequences the process with explicit validation checkpoints (draft-before-write, confirm-before-post, verify posted body before closing, stop-and-report on failure), matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

The SKILL.md body serves as a well-organized overview that signals a single one-level-deep reference (commands.md) for executable snippets, with the reference path verified as a real file and clearly linked.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, third-person description that clearly states capabilities and an explicit trigger condition. It is concise yet comprehensive and clearly distinct from other skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('assess', 'draft issue comments', 'post progress updates', 'recommend whether issue threads should stay open or close') rather than vague language, matching the highest anchor.

3 / 3

Completeness

It explicitly answers both 'what' (assess/draft/post/recommend) and 'when' via a clear 'Use when...' clause, satisfying the top anchor for completeness.

3 / 3

Trigger Term Quality

It uses natural trigger phrasing ('Use when the user provides Warp commit SHA(s) and GitHub issue number(s)') with terms a user would actually say, giving good coverage of natural trigger keywords.

3 / 3

Distinctiveness Conflict Risk

The narrow Warp + GitHub-issue workflow with SHA/issue-number triggers carves a distinct niche unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NVIDIA/warp
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.