project-session-manager

Manage isolated dev environments with git worktrees and tmux sessions

Quality

58%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/project-session-manager/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 clear technical niche combining git worktrees and tmux sessions, which provides good distinctiveness. However, it lacks concrete action verbs describing what operations can be performed and critically missing explicit trigger guidance for when Claude should use this skill.

Suggestions

Add a 'Use when...' clause with trigger terms like 'worktree', 'parallel development', 'multiple branches simultaneously', 'tmux workspace'

List specific concrete actions such as 'create worktrees for feature branches', 'set up tmux sessions per worktree', 'clean up stale worktrees'

Include common user phrases like 'work on multiple branches', 'isolated development', 'switch between features'

Dimension	Reasoning	Score
Specificity	Names the domain (dev environments) and mentions specific tools (git worktrees, tmux sessions), but doesn't list concrete actions like 'create worktrees', 'switch sessions', or 'clean up environments'.	2 / 3
Completeness	Describes what it does at a high level 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 technical terms 'git worktrees' and 'tmux sessions' that users familiar with these tools would use, but misses common variations like 'parallel branches', 'multiple working directories', 'terminal sessions', or 'workspace isolation'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'git worktrees' and 'tmux sessions' creates a clear, specific niche that is unlikely to conflict with other skills - these are distinct tools with a specific workflow pattern.	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 well-structured, highly actionable skill with excellent workflow clarity and concrete executable examples. The main weakness is its length - the detailed implementation protocol and multiple provider configurations make it verbose. Splitting implementation details into separate reference files would improve token efficiency while maintaining the strong actionability.

Suggestions

Move the detailed Implementation Protocol section (bash scripts for each subcommand) to a separate IMPLEMENTATION.md file, keeping only a summary in the main skill

Consolidate the repeated session creation patterns (steps 5-9 are nearly identical across review/fix/feature) into a single reusable reference

Consider moving Jira-specific configuration and examples to a separate PROVIDERS.md file to reduce main document length

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some redundancy (e.g., similar patterns repeated across subcommands, verbose bash examples that could be condensed). The PSM vs Teleport comparison table and multiple configuration examples add bulk that could be streamlined.	2 / 3
Actionability	Excellent actionability with fully executable bash commands, complete JSON configuration examples, and copy-paste ready code blocks throughout. Every command has concrete examples with expected outputs.	3 / 3
Workflow Clarity	Clear numbered steps for each subcommand with explicit validation points (checking if worktree exists, verifying PR/issue status). Error handling table provides recovery guidance. The Implementation Protocol section provides unambiguous sequencing.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but the document is monolithic at ~400 lines. The Implementation Protocol section with detailed bash scripts could be split into a separate reference file. Internal anchor links help but external file references would improve navigation.	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
skill_md_line_count	SKILL.md is long (566 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: Yeachan-Heo/oh-my-claudecode
Commit: 48ffaac

Reviewed: 4 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.