cs-project-manager

Project Manager agent for sprint planning, Jira/Confluence workflows, Scrum ceremonies, and stakeholder reporting. Orchestrates project-management skills. Use when running delivery operations — e.g., planning a sprint with capacity and carry-over math in Jira, or assembling a portfolio health report for stakeholders from ticket and velocity data.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/cs-project-manager/SKILL.md

Quality

Content

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

A thorough, highly actionable agent skill with well-structured workflows and copy-paste commands, weakened mainly by verbosity from re-documenting the orchestrated sub-skills and by the absence of validation checkpoints in batch/config-mutating workflows.

Suggestions

Trim the Skill Integration section to locations and a one-line purpose per sub-skill; let each sub-skill's own SKILL.md document its tools/references rather than duplicating them inline.

Add explicit validation checkpoints to the batch/config workflows — e.g., after Jira workflow/automation setup, verify the rule fired on a test issue before onboarding the team; after creating retro action-item tickets, confirm they landed in the next sprint backlog.

Move the "Last Updated / Version / Status" date metadata out of the body or into a clearly delimited footer-only block so time-sensitive info doesn't pad the operational content.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and actionable, but the Skill Integration section re-lists every sub-skill's tools (purpose/path/usage/features) and knowledge bases — content that already lives in those referenced skills — making the ~500-line body noticeably padded in places.	3 / 5
Actionability	Fully executable guidance throughout: concrete `python ../../project-management/.../script.py sample.json` invocations with paths, per-step commands, and copy-paste bash pipelines in the Integration Examples that cover the common sprint/retro/portfolio cases.	5 / 5
Workflow Clarity	All four workflows have clearly numbered, sequenced steps with Expected Output and time estimates, but none include validation/verification checkpoints — and Workflow 4 (Jira/Confluence setup) and the retro workflow perform batch write operations (creating projects, workflows, automation rules, Jira tickets), so the destructive/batch cap of 3 applies.	3 / 5
Progressive Disclosure	Structure is good with a dedicated References section and one-level-deep, clearly signaled links to the orchestrated sub-skills; the main gap is that sub-skill tool/reference detail is inlined in the body rather than left to those sub-skills.	4 / 5
	Total	15 / 20 Passed

Description

88%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, third-person description that concretely names capabilities and gives explicit "Use when" triggers with worked examples. It is well above the midpoint on every dimension, with only minor gaps in trigger-term synonyms and some inherent overlap with its orchestrated sub-skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "sprint planning, Jira/Confluence workflows, Scrum ceremonies, and stakeholder reporting" — plus concrete worked examples (capacity and carry-over math, portfolio health report from ticket/velocity data), giving comprehensive coverage of the PM domain.	5 / 5
Completeness	Explicitly answers both what ("Project Manager agent for sprint planning, Jira/Confluence workflows...") and when ("Use when running delivery operations — e.g., planning a sprint... or assembling a portfolio health report...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keywords a PM would actually say ("sprint planning", "Jira/Confluence", "Scrum ceremonies", "stakeholder reporting", "delivery operations"), but a few common synonyms (agile, retrospective, backlog grooming) are absent, so it stops just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The Atlassian/agile-delivery niche is clear and unlikely to trigger for unrelated skills, but as an agent that "orchestrates project-management skills" it has minor overlap risk with the very sub-skills it delegates to.	4 / 5
	Total	18 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (516 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 9 suspicious	Warning

	Total	13 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/cs-project-manager/SKILL.md
Commit: 19392f7

Reviewed: ~3 hours 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.