CtrlK
BlogDocsLog inGet started
Tessl Logo

clawhub-pr-maintainer

Use when reviewing, triaging, validating, or discussing ClawHub GitHub issues or pull requests, including author context, CI, UI proof, evidence, labels, close decisions, and maintainer handoff.

80

Quality

100%

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

100%

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 maintainer review playbook: concrete gh/proof commands, a numbered best-fix loop with validation checkpoints, and clear section navigation without nested references or concept padding. It is executable, well-sequenced, and token-efficient.

DimensionReasoningScore

Conciseness

Lean directive bullets and concrete commands with no padded concept explanation; every section assumes Claude's competence and earns its place.

3 / 3

Actionability

Provides fully executable guidance: exact gh pr view/issue view/api commands with --json field keys, bun run proof:publish invocations, --dry-run and credential-failure handling, and heredoc/--body-file patterns that are copy-paste ready.

3 / 3

Workflow Clarity

Clear sequenced workflow from live-state reading through a 7-step best-fix loop, with explicit validation checkpoints (Remaining uncertainty, publish-before-commenting) and a batch/destructive guardrail (no more than five closes without confirmation).

3 / 3

Progressive Disclosure

Single-file skill with no bundle files; the one external reference (clawhub-ui-proof skill) is clearly signaled and one level deep with no nested indirection, and the body is organized into well-labeled navigable sections.

3 / 3

Total

12

/

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.

The description is concise yet comprehensive, opening with an explicit 'Use when' trigger and enumerating concrete maintainer actions scoped to ClawHub issues/PRs. It clearly answers both what the skill does and when to invoke it with natural trigger terms.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions (reviewing, triaging, validating, discussing issues/PRs) plus sub-actions (author context, CI, UI proof, evidence, labels, close decisions, maintainer handoff), matching the comprehensive anchor.

3 / 3

Completeness

Explicitly answers both 'what' (the action list) and 'when' via the 'Use when ...' trigger clause, satisfying the top anchor.

3 / 3

Trigger Term Quality

Uses natural maintainer vocabulary users would actually say (reviewing, triaging, validating, issues or pull requests, labels, close decisions), with good coverage and no missing common variations.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (ClawHub GitHub issues/PRs) with distinct triggers, making it unlikely to fire for the wrong skill.

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
openclaw/clawhub
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.