jira-project-management

Administer Jira projects. Use when creating/archiving projects, managing components, versions, roles, permissions, or project configuration.

Install with Tessl CLI

npx tessl i github:NeverSight/skills_feed --skill jira-project-management

What are skills?

Quality

82%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Optimize this skill with Tessl

npx tessl skill review --optimize ./data/skills-md/01000001-01001110/agent-jira-skills/jira-project-management/SKILL.md

SKILL.md

Review

Evals

Discovery

100%

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 skill description that follows best practices. It uses third person voice, provides specific concrete actions, includes an explicit 'Use when...' clause with relevant trigger terms, and clearly defines its administrative scope within Jira. The description effectively distinguishes itself from potential overlapping skills like Jira issue management or general project tools.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'creating/archiving projects, managing components, versions, roles, permissions, or project configuration' - these are distinct, actionable capabilities.	3 / 3
Completeness	Clearly answers both what ('Administer Jira projects' with specific actions listed) and when ('Use when creating/archiving projects, managing components, versions, roles, permissions, or project configuration').	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'Jira', 'projects', 'components', 'versions', 'roles', 'permissions', 'project configuration' - good coverage of domain-specific terms users would naturally mention.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused on Jira project administration specifically - distinct from general project management, issue tracking, or other Atlassian tools. The combination of 'Jira' + 'administer' + specific admin tasks creates a unique trigger profile.	3 / 3
	Total	12 / 12 Passed

Implementation

64%

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

This skill provides highly actionable, executable code for Jira project management with excellent coverage of CRUD operations, components, versions, and roles. However, it's overly verbose for Claude's context window, includes extensive type definitions that could be inferred, and lacks explicit validation workflows for destructive operations. The content would benefit from being split into a concise overview with references to detailed implementation files.

Suggestions

Split detailed type definitions and CRUD implementations into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with quick-start examples

Add explicit validation checkpoints for destructive operations (e.g., 'Before deleteProject: 1. Verify project exists, 2. Check issue count, 3. Confirm with user, 4. Use enableUndo=true')

Remove verbose inline comments that explain obvious parameters (e.g., '// 2-10 uppercase letters' repeated multiple times)

Consolidate the curl examples section - show 2-3 representative examples and reference a separate file for the complete set

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but overly verbose for Claude's needs. Type definitions and basic CRUD patterns are extensively documented when Claude could infer much of this from a few examples. The 600+ lines could be condensed significantly.	2 / 3
Actionability	Excellent actionability with fully executable TypeScript code, complete curl examples, and copy-paste ready implementations. Every operation has concrete, working code with proper types and parameters.	3 / 3
Workflow Clarity	Individual operations are clear, but multi-step workflows like setupProject lack validation checkpoints. Destructive operations (deleteProject, deleteComponent, deleteVersion) don't emphasize verification steps before execution.	2 / 3
Progressive Disclosure	Content is monolithic with everything inline. The API endpoints summary table and references at the end are helpful, but detailed type definitions and all CRUD operations could be split into separate reference files, with SKILL.md providing a concise overview.	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
skill_md_line_count	SKILL.md is long (834 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Reviewed: about 19 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.