CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pm-skills

Use when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin, templates, meeting analysis, team comms. Triggers on 'our sprints feel off', 'project health report', 'audit our Jira permissions', 'when will it be done', 'run the delivery loop'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a full goal→plan→execute→verify→close delivery loop through the repo-wide agent-harness with Jira MCP data bridged into the domain's analytics tools. Distinct from product-team (what to build vs how to deliver it), business-operations (internal ops), and engineering/agent-harness (the generic loop engine this orchestrator plugs into).

68

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is pm-skills in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 a lean, highly actionable orchestrator playbook: a deterministic router with exit-code semantics, a gated delivery loop with explicit validation and escalation caps, and hard governance rules. Its main weaknesses are the incomplete loop_controller command and the fact that every referenced file (references/ and scripts/) is absent from the bundle, leaving the disclosure structure unresolvable.

Suggestions

Ship the referenced bundle files — references/flow_forecasting_canon.md, references/agentic_delivery_governance.md, references/pm_loop_playbook.md, and the scripts (pm_goal_router.py, jira_snapshot_bridge.py, delivery_loop_gate.py) — or remove the links; as delivered, the References section and the core routing/verification workflow point at files that do not exist.

Complete the loop_controller.py example: replace 'init|next|record|verify|close ...' with at least the argument shapes for the two most common invocations (init and record), matching the copy-paste readiness of the router and gate commands.

Fold the symptom table into a single line of pointer text (or move it to the router's --help output), since the routing logic section already mandates using the script rather than the table — this trims redundant tokens and removes a source of drift between table and router.

DimensionReasoningScore

Conciseness

The body is dense and operational — tables for symptoms and output artifacts, one-line canon citations ('refuses on < 10 completed items — thin history forecasts are lies'), and no explanations of concepts Claude already knows. Not 5: minor trimming is possible — the symptom table overlaps the deterministic router ('do not eyeball the table when a script can decide'), and a few rationale asides ('same locked-evaluator invariant as autoresearch-agent', 'that diff finds watermelon projects') are denser than needed to act.

4 / 5

Actionability

Most guidance is copy-paste ready with exit-code semantics: 'python3 scripts/pm_goal_router.py --text "<the goal>" --output json' with 'Exit 0 → route_to… Exit 2 → ask ONE clarifying question… Exit 3 → no signal', and both delivery_loop_gate.py invocations with 'exit 2 = blocked' / 'exit 4 = close refused'. Not 5: 'loop_controller.py init|next|record|verify|close ...' trails with an ellipsis and no argument list, so that step is not executable as written.

4 / 5

Workflow Clarity

The delivery loop is explicitly sequenced (Observe → Choose → Act → Verify → Record → Repeat-or-stop) with machine-run validation gates at plan and close, sub-skill gates layered on top ('scrum-master's ≥ 3-sprints rule, atlassian-admin's VERIFY steps'), explicit feedback control ('Max 3 attempts per task, 12 loop iterations per goal — then escalate'), and 'Never adjudicate your own verification'. This matches the anchor for explicit validation steps with feedback loops and error-recovery escalation.

5 / 5

Progressive Disclosure

The body itself is well-sectioned and defers canon material to three clearly signaled references (flow_forecasting_canon.md, agentic_delivery_governance.md, pm_loop_playbook.md), but none of those reference files — nor any of the scripts the workflow depends on (pm_goal_router.py, jira_snapshot_bridge.py, delivery_loop_gate.py) — exist in the bundle, so the navigation structure cannot be verified and the links are dangling. It also leans on repo-external paths ('../scrum-master/scripts/velocity_analyzer.py', 'engineering/agent-harness/…', 'project-management/references/atlassian-mcp-tools.md') that fall outside the skill's own directory. Not 4: missing referenced files is more than a minor organization gap, since the References section and the core workflow depend on them.

3 / 5

Total

16

/

20

Passed

Description

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

A strong description in third-person voice: it explicitly states what the orchestrator does, gives five natural concrete trigger phrases, and preemptively disambiguates from three neighboring skills. The only notable gap is missing common PM synonyms (scrum, agile, backlog, retrospective) in the trigger set.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Forks context to route to one sub-skill via a deterministic signal router and returns a digest', 'drive a full goal→plan→execute→verify→close delivery loop', 'Jira MCP data bridged into the domain's analytics tools' — and enumerates the full 8-sub-skill domain coverage (sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin, templates, meeting analysis, team comms). Not the level below (4): coverage is comprehensive for the domain, not just several actions with gaps.

5 / 5

Completeness

Both questions are answered explicitly: what it does ('coordinating project-delivery work across the 8 project-management sub-skills', routing, digests, delivery loops) and when to use it ('Use when coordinating...' plus five concrete quoted trigger phrases). Matches the anchor for explicit what AND when with concrete triggers; the level below (4) applies only when 'when' is less explicit.

5 / 5

Trigger Term Quality

Explicit natural trigger phrases are strong — 'our sprints feel off', 'project health report', 'audit our Jira permissions', 'when will it be done', 'run the delivery loop' — plus keyword coverage across all sub-domains. Not 5: common natural variations a user would say, such as 'scrum', 'agile', 'kanban', 'backlog', 'retrospective', or 'standup', are absent from the trigger set.

4 / 5

Distinctiveness Conflict Risk

It proactively distinguishes itself from three adjacent skills — 'Distinct from product-team (what to build vs how to deliver it), business-operations (internal ops), and engineering/agent-harness (the generic loop engine this orchestrator plugs into)' — and the triggers are niche-specific PM delivery phrases with minimal overlap risk.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 missing

Warning

referenced_paths_exist

Referenced path issues: 12 missing

Warning

Total

13

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/pm-skills/SKILL.md

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.