jira-project-management
Administer Jira projects. Use when creating/archiving projects, managing components, versions, roles, permissions, or project configuration.
76
71%
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 ./data/skills-md/01000001-01001110/agent-jira-skills/jira-project-management/SKILL.mdQuality
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 strong, well-crafted skill description. It concisely identifies the domain (Jira project administration), lists specific capabilities, and includes an explicit 'Use when' clause with natural trigger terms. The description is appropriately scoped to avoid conflicts with related but distinct skills like Jira issue tracking.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating/archiving projects, managing components, versions, roles, permissions, and project configuration. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (administer Jira projects with specific sub-tasks listed) and 'when' (explicit 'Use when' clause with trigger scenarios like 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', 'creating', 'archiving'. These cover the domain well and match how users naturally describe Jira administration tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Jira project administration specifically, which is a distinct niche. The mention of Jira-specific concepts like components, versions, roles, and permissions makes it unlikely to conflict with other skills. It's distinguishable from general Jira issue management or other project management tools. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a comprehensive Jira REST API reference document rather than a focused, concise skill. While the code examples are highly actionable and executable, the content is extremely verbose with significant redundancy (TypeScript functions + curl examples + endpoint summary table all covering the same operations). It lacks validation checkpoints for destructive operations and would benefit greatly from splitting into a concise overview with references to detailed sub-files.
Suggestions
Reduce the SKILL.md to a concise overview with quick-start examples for the most common operations (create project, add component, create version), and move detailed TypeScript interfaces, full CRUD functions, and curl examples into separate reference files like API-REFERENCE.md or EXAMPLES.md.
Remove redundant coverage — choose either TypeScript functions OR curl examples as the primary format, and drop the API endpoint summary table which duplicates information already shown in the code.
Add explicit validation and error-handling checkpoints for destructive operations (delete project, delete component, delete version), including pre-checks like verifying issue counts before deletion and rollback guidance if multi-step operations like setupProject fail partway through.
Eliminate TypeScript interface definitions that Claude can infer from the function signatures and API responses — these consume significant tokens without adding actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. The full TypeScript type definitions, every CRUD function signature, curl examples for every operation, AND an API endpoint summary table create massive redundancy. Claude already knows how to construct REST API calls and TypeScript interfaces — this is essentially API documentation, not a skill. | 1 / 3 |
Actionability | The code is fully executable TypeScript with complete function signatures, concrete curl examples with real payloads, and specific API paths. Every operation is copy-paste ready with proper HTTP methods, headers, and request bodies. | 3 / 3 |
Workflow Clarity | Steps are labeled sequentially (Step 1-9) but there are no validation checkpoints or feedback loops for destructive operations like deleteProject or deleteComponent. The setupProject helper shows a multi-step workflow but lacks error handling or rollback guidance if a step fails mid-sequence. | 2 / 3 |
Progressive Disclosure | Monolithic wall of content with no separation into supporting files. The type definitions, CRUD operations, component management, version management, role management, properties, validation, helpers, curl examples, and API summary table are all inlined. This would benefit enormously from splitting into separate reference files (e.g., COMPONENTS.md, VERSIONS.md, ROLES.md, API-REFERENCE.md). | 1 / 3 |
Total | 7 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (834 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- NeverSight/skills_feed
- Commit
aa009ea
- 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.