portman

Port management for local development with git worktrees. Use when setting up local development environments, booking ports for services to avoid collisions between parallel worktrees, or configuring docker-compose with dynamic ports.

Quality

83%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

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 excellent executable examples and clear workflows. The main weakness is verbosity - the 'Why Portman?' section and some explanatory text could be trimmed, and the extensive patterns section could be moved to a separate reference file to keep the main skill leaner.

Suggestions

Remove or significantly condense the 'Why Portman?' section - Claude understands port conflicts without explanation

Move 'Common Patterns' and 'CI/CD Considerations' sections to a separate PATTERNS.md file, linking from the main skill

Trim explanatory sentences like 'Each worktree gets its own context, ensuring port isolation' that state the obvious

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary explanation (the 'Why Portman?' section explains concepts Claude can infer) and could be tightened, but most content is practical and useful.	2 / 3
Actionability	Provides fully executable commands, complete code examples for docker-compose.yml, .envrc, Makefile, and shell scripts that are copy-paste ready with clear context.	3 / 3
Workflow Clarity	Clear numbered sequences for setup, well-organized sections for different use cases, and includes troubleshooting with explicit recovery steps (release and rebook pattern).	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but the skill is quite long (~200 lines) and could benefit from splitting detailed patterns (CI/CD, Makefile integration) into separate reference files.	2 / 3
	Total	10 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted description with strong completeness and distinctiveness. It includes an explicit 'Use when' clause with relevant trigger scenarios and carves out a clear niche. The main weakness is that the capabilities could be more specific about what concrete actions the skill enables beyond the general domain.

Suggestions

Add more specific concrete actions like 'allocate ports', 'release reserved ports', 'list port assignments', or 'detect port conflicts' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (port management, git worktrees) and some actions (setting up environments, booking ports, configuring docker-compose), but doesn't list comprehensive concrete actions like 'allocate ports', 'release ports', 'list reserved ports', or 'check for conflicts'.	2 / 3
Completeness	Clearly answers both what (port management for local development with git worktrees) and when (explicit 'Use when' clause covering setup, booking ports to avoid collisions, and docker-compose configuration).	3 / 3
Trigger Term Quality	Good coverage of natural terms users would say: 'port', 'local development', 'worktrees', 'booking ports', 'collisions', 'docker-compose', 'dynamic ports'. These are terms developers would naturally use when needing this functionality.	3 / 3
Distinctiveness Conflict Risk	Very specific niche combining port management with git worktrees context. The combination of 'worktrees', 'port collisions', and 'dynamic ports' creates a distinct trigger profile unlikely to conflict with general docker or git skills.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

Reviewed: 5 months 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.