project-shepherd
Expert project manager specializing in cross-functional project coordination, timeline management, and stakeholder alignment. Focused on shepherding projects from conception to completion while managing resources, risks, and communications across multiple teams and departments.
37
22%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./pm-project-shepherd/skills/SKILL.mdQuality
Discovery
32%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 reads more like a job title or resume summary than a skill description for Claude's skill selection. It uses first-person-adjacent framing ('Expert project manager specializing in...') rather than third-person action verbs, and completely lacks explicit trigger guidance ('Use when...'). The capabilities listed are high-level categories rather than concrete, actionable tasks.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'project plan, timeline, milestone tracking, resource allocation, status report, risk assessment, cross-team coordination.'
Replace the persona-style opening ('Expert project manager specializing in...') with concrete action verbs in third person, e.g., 'Creates project plans, tracks milestones and deadlines, manages resource allocation, generates status reports, and identifies project risks.'
Include specific deliverables or artifacts this skill produces (e.g., 'Gantt charts, project timelines, RACI matrices, risk registers, stakeholder communication plans') to improve specificity and distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (project management) and some actions like 'cross-functional project coordination, timeline management, and stakeholder alignment,' but these are more like category labels than concrete actions. It lacks specific actionable verbs like 'create Gantt charts, assign tasks, track milestones.' | 2 / 3 |
Completeness | Describes what it does at a high level but completely lacks any 'Use when...' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause should cap completeness at 2, and since the 'what' is also vague and abstract, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'project coordination,' 'timeline management,' 'stakeholder alignment,' 'resources,' 'risks,' and 'communications,' but misses many natural user terms like 'project plan,' 'deadline,' 'milestone,' 'task tracking,' 'status update,' 'roadmap,' or 'sprint.' | 2 / 3 |
Distinctiveness Conflict Risk | The project management domain is somewhat specific, but terms like 'managing resources, risks, and communications' are broad enough to overlap with general management, team coordination, or communication skills. It lacks distinct file types, tools, or narrow triggers. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is a persona/role description rather than an actionable skill. It extensively describes what a project manager should be and do using concepts Claude already understands, without providing any concrete, executable guidance, specific tools, or novel methodology. The templates are generic placeholders, and the entire document could be replaced with a few lines of specific instructions about what tools to use and what outputs to produce.
Suggestions
Replace the persona description with concrete, actionable instructions - specify exact tools/commands to use for project tracking, what file formats to produce, and specific frameworks with examples rather than abstract principles.
Remove sections that describe general project management knowledge Claude already has (identity, mission, success metrics, advanced capabilities) and focus only on project-specific conventions, templates, or tooling unique to this workspace.
Add concrete, filled-in examples of deliverables (e.g., a complete sample status report or risk register) instead of bracket-placeholder templates.
Split the templates and detailed methodology into separate referenced files, keeping SKILL.md as a concise overview with clear navigation to supporting documents.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive content Claude already knows - project management concepts, stakeholder management principles, communication styles, and success metrics are all general knowledge. The file is a personality/role description rather than a skill with actionable instructions, filled with aspirational statements and padding like emoji headers. | 1 / 3 |
Actionability | No concrete, executable guidance whatsoever. The templates are generic markdown placeholders with bracketed fill-in-the-blank fields. There are no specific commands, tools, code, or concrete steps Claude can execute - just abstract descriptions of what a project manager should do. | 1 / 3 |
Workflow Clarity | The 4-step workflow process is sequenced and logically ordered, but lacks any validation checkpoints, feedback loops, or concrete verification steps. Steps are described at a high level without specific actions or decision criteria for when to proceed. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files for detailed content. Everything is inline in one massive document. The final line references 'core training' which is vague and unhelpful. Content that could be split (templates, advanced capabilities) is all crammed into one file. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%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
- OpenRoster-ai/awesome-openroster
- Commit
09aef5d
- Reviewed
Table of Contents
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.