project-session-manager

Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/project-session-manager/SKILL.md

Quality

Content

65%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 concrete and largely executable with well-sequenced per-subcommand protocols, but destructive operations lack validation feedback loops and everything is inlined with no reference files for offloading bulk detail. Adding validation checkpoints and splitting the implementation protocol into referenced files would raise the capped dimensions.

Suggestions

Add explicit validation/confirmation checkpoints before destructive actions (e.g., verify session/branch exists and prompt before `git worktree remove --force` and registry deletion).

Move the per-subcommand implementation protocol and Jira configuration details into reference files (e.g., PROTOCOL.md, JIRA.md) and link to them one level deep from the overview.

Fill the stubbed "Update sessions registry" steps with the actual jq commands so every step is copy-paste ready, and de-duplicate the Quick Start versus the Teleport section.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and command-driven with minimal concept explanation, but the Quick Start duplicates the later Teleport section and the review/fix/feature steps repeat similar scaffolding, leaving minor trim opportunities per anchor 4.	4 / 5
Actionability	Heavily executable with concrete gh/git/tmux commands, real flags, and JSON metadata templates, but a few stub steps like bare "Update sessions registry" comments without the matching jq commands introduce minor gaps, fitting anchor 4.	4 / 5
Workflow Clarity	Each subcommand has a clear numbered sequence, but destructive/batch operations (worktree remove --force, cleanup, --dangerously-skip-permissions) lack explicit validate-before-act feedback loops, which per the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist and all content is inlined in one ~580-line SKILL.md; section structure is real and navigable, but the full per-subcommand implementation protocol and Jira config are bulk that could live in separate reference files, matching anchor 3.	3 / 5
	Total	14 / 20 Passed

Description

53%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.

The description conveys a clear, fairly specific niche but omits any explicit "when to use" trigger guidance and uses a generic action verb, capping several dimensions. Adding a Use-when clause with concrete trigger phrases would lift completeness and trigger-term quality.

Suggestions

Append a "Use when..." clause naming concrete triggers (e.g., parallel work on issues/PRs, isolated feature branches, managing tmux dev sessions).

Replace the generic verb "manager" with specific actions like "creates isolated git worktrees and orchestrates tmux sessions for parallel issue/PR/feature work".

Add natural synonyms and file/config references users would say (worktrees, branches, session attach/kill, ~/.psm config) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (dev environments) plus a few concrete capabilities (worktrees, tmux sessions, issues/PRs/features), but the action verb "manager" is generic and coverage is not comprehensive, matching anchor 3.	3 / 5
Completeness	Provides a clear "what" (worktree-first dev environment manager) but no "Use when..." trigger clause; per the rubric guideline a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant natural keywords (worktree, issues, PRs, features, tmux sessions) but they lean technical and miss common synonyms, fitting anchor 3 rather than the fuller coverage of anchor 4.	3 / 5
Distinctiveness Conflict Risk	The worktree-first session-manager niche with tmux is mostly distinct with only minor overlap risk against closely related dev-environment skills, matching anchor 4.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (593 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: Yeachan-Heo/oh-my-claudecode
Path: skills/project-session-manager/SKILL.md
Commit: 5aa678c

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