CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

github-wake

Register an existing GitHub issue so the current Codex or Claude Code session is woken when its first future comment arrives. Use when work is genuinely blocked on a GitHub reply and the session must resume asynchronously.

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

92%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 model of a compact, single-purpose operational skill: copy-paste-ready commands for both agent platforms, explicit error-recovery branches, and management commands, with no filler. Its only ding is the inline version-gated instruction, which will age.

DimensionReasoningScore

Conciseness

Lean and operational throughout — no padding or explanations of concepts Claude already knows — but the time-sensitive version reference "In Claude Code 2.1.98 or later" sits inline rather than in a versioned/deprecated section, which the guidelines penalize.

4 / 5

Actionability

Fully executable, copy-paste-ready commands for every common case: `github-wake ISSUE_URL`, `github-wake --codex-home ~/.codex-rja ISSUE_URL`, `github-wake --claude-monitor ISSUE_URL`, plus `--status` and `--cancel WATCH_ID`, with a concrete example directory value.

5 / 5

Workflow Clarity

Clear sequence from precondition checklist to per-agent command to management and post-delivery behavior, with explicit feedback loops for error recovery ("If it reports that none or several do, pass the actual account directory"; "If `Monitor` is unavailable, explain that Claude Code must be upgraded") and `--status` for verification.

5 / 5

Progressive Disclosure

Self-contained skill with no bundle files and no external references; ~60 well-organized lines with clean section headers (Codex, Claude Code, Both agents) — the simple-skill case where well-organized sections alone merit full credit.

5 / 5

Total

19

/

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 description: it states a concrete capability in third person, gives an explicit and conditional "Use when" clause, and carves out a distinct niche. The only room for improvement is broader trigger-term coverage (synonyms like "notification" or "response").

DimensionReasoningScore

Specificity

Names several concrete actions and effects — "Register an existing GitHub issue", "woken when its first future comment arrives", "resume asynchronously" — but as a single-purpose tool it does not list the multiple distinct actions of the anchor-5 example.

4 / 5

Completeness

Explicitly answers both what ("Register an existing GitHub issue so the current Codex or Claude Code session is woken when its first future comment arrives") and when ("Use when work is genuinely blocked on a GitHub reply and the session must resume asynchronously") with concrete conditions.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — "GitHub issue", "comment", "reply", "blocked on a GitHub reply" — but misses a few synonyms and variations like "notification", "response", or "wake me when".

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — asynchronous wake-on-reply registration for a live session — with trigger conditions unlikely to match any other skill.

5 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

pchalasani/claude-code-tools

Path

plugins/dynamic-workflow/skills/github-wake/SKILL.md

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.