pm-manager

PM Manager Agent. 프로젝트 관리, 일정 조율, 리소스 관리를 담당합니다. 일정, 스케줄, 마일스톤, 프로젝트 관리 관련 요청 시 사용됩니다.

Quality

44%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/pm-manager/SKILL.md

Quality

Content

22%

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

This skill reads more like a PM reference document than actionable instructions for Claude. It explains what PM activities are rather than how Claude should perform them. The templates are useful but lack context on when/how to use them, and there's no concrete workflow for Claude to follow when asked to manage a project.

Suggestions

Add concrete step-by-step workflows for common PM tasks (e.g., 'When asked to create a project plan: 1. Ask for scope/timeline, 2. Create WBS using this format, 3. Generate schedule file at docs/plans/...')

Remove generic PM framework explanations (Agile, Kanban concepts) that Claude already knows - focus on project-specific conventions and file formats

Add validation checkpoints (e.g., 'Before finalizing schedule, verify: all dependencies mapped, no resource conflicts, milestones have clear acceptance criteria')

Include example inputs and expected outputs showing how Claude should respond to specific PM requests

Dimension	Reasoning	Score
Conciseness	The content is reasonably organized but includes generic PM concepts (Agile, Kanban, WBS) that Claude already knows. The templates add value but the framework explanations are unnecessary padding.	2 / 3
Actionability	The skill describes PM concepts and provides templates but lacks concrete, executable guidance. There are no specific commands, scripts, or step-by-step instructions for Claude to actually perform PM tasks - it's descriptive rather than instructive.	1 / 3
Workflow Clarity	No clear workflow for how Claude should actually manage a project. The Scrum cycle diagram is conceptual, not actionable. Missing validation steps, decision points, or feedback loops for project management activities.	1 / 3
Progressive Disclosure	Content is organized into sections with clear headers, and references output file locations. However, all content is inline in one file without links to detailed references, and some sections (like frameworks) could be separated.	2 / 3
	Total	6 / 12 Passed

Description

67%

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 description provides a functional overview of a project management skill with explicit 'when to use' guidance, which is a strength. However, the capabilities listed are high-level categories rather than concrete actions, and the trigger terms, while relevant, could benefit from broader coverage including common variations and specific tool/methodology references.

Suggestions

Add more specific concrete actions such as 'create project timelines', 'track task dependencies', 'generate status reports', or 'manage sprint backlogs' to improve specificity.

Expand trigger terms to include common variations like 'task', 'deadline', 'sprint', 'backlog', 'Gantt', 'WBS', and consider adding English equivalents for bilingual users.

Dimension	Reasoning	Score
Specificity	Names the domain (project management) and lists some actions (프로젝트 관리, 일정 조율, 리소스 관리 - project management, schedule coordination, resource management), but these are fairly high-level categories rather than concrete specific actions like 'create Gantt charts' or 'assign tasks to team members'.	2 / 3
Completeness	Clearly answers both 'what' (프로젝트 관리, 일정 조율, 리소스 관리를 담당합니다) and 'when' (일정, 스케줄, 마일스톤, 프로젝트 관리 관련 요청 시 사용됩니다) with explicit trigger guidance for when to use the skill.	3 / 3
Trigger Term Quality	Includes relevant Korean keywords (일정, 스케줄, 마일스톤, 프로젝트 관리 - schedule, schedule, milestone, project management) that users might naturally say, but missing common variations like task tracking, deadline, sprint, backlog, or English equivalents for bilingual contexts.	2 / 3
Distinctiveness Conflict Risk	The PM/project management domain is reasonably specific, but terms like '일정' (schedule) and '리소스 관리' (resource management) could overlap with calendar skills, HR skills, or general planning tools. The niche is defined but not sharply bounded.	2 / 3
	Total	9 / 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: shaul1991/shaul-agents-plugin
Commit: 9242c58

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