tmux-init

Set up tmux notification system for Claude Code sessions

Quality

58%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/claude-code-dev/skills/tmux-init/SKILL.md

Quality

Discovery

40%

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 identifies a specific technical domain (tmux notifications for Claude Code) which provides good distinctiveness, but it lacks the completeness needed for effective skill selection. The absence of explicit trigger conditions and limited action specificity make it difficult for Claude to know when to choose this skill over others.

Suggestions

Add a 'Use when...' clause with trigger terms like 'notify me when done', 'tmux alerts', 'background task notifications', or 'terminal notifications'

Expand the action specificity by listing concrete capabilities such as 'configure terminal bell alerts, set up visual notifications, integrate with system notifications'

Include common user phrases like 'alert when complete', 'notify on finish', or 'long-running task notifications'

Dimension	Reasoning	Score
Specificity	Names the domain (tmux notification system) and a general action (set up), but doesn't list specific concrete actions like configuring hooks, setting alert types, or defining notification triggers.	2 / 3
Completeness	Describes what (set up tmux notification system) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'tmux', 'notification', and 'Claude Code sessions', but misses common variations users might say like 'alerts', 'terminal notifications', 'background tasks', or 'notify when done'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'tmux notification system' and 'Claude Code sessions' creates a clear, specific niche that is unlikely to conflict with other skills.	3 / 3
	Total	8 / 12 Passed

Implementation

77%

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

This is a solid, actionable skill with clear workflows and executable code throughout. The main weakness is some verbosity in the status-checking bash scripts that could be tightened. The troubleshooting section is well-structured with specific diagnostic commands.

Suggestions

Consider condensing the --status bash script by removing redundant echo statements and combining related checks

The 'What Gets Installed' section could be more concise - Claude doesn't need detailed explanations of what LaunchAgents or shell environment variables are

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundancy between the status check section and troubleshooting. The detailed bash scripts for --status could be more concise since Claude can infer standard patterns.	2 / 3
Actionability	Provides fully executable bash commands throughout, including complete status checking scripts, installation commands, and troubleshooting curl commands. All code is copy-paste ready.	3 / 3
Workflow Clarity	Clear multi-step workflows with explicit validation: installation via `forge webhook init`, status checking via `forge webhook status`, and troubleshooting steps with specific commands to verify each component. The --status flag provides comprehensive validation checkpoints.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but the skill is somewhat monolithic. The detailed bash scripts for status checking could potentially be referenced rather than inline. However, the structure is logical with Usage → What Gets Installed → Prerequisites → Execution → Troubleshooting.	2 / 3
	Total	10 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

Reviewed: 29 days ago

Table of Contents

Discovery Implementation Validation

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.