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 distinctive enough to avoid conflicts with other skills while covering the key actions users would request.
| 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 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 general project management or other tool skills. | 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 a comprehensive but extremely verbose API reference document rather than a concise, actionable skill. It provides excellent executable code and curl examples, but the sheer volume of redundant content (TypeScript functions + curl examples + endpoint table all covering the same operations) wastes token budget significantly. It would benefit enormously from splitting into a concise overview with references to detailed sub-files for each resource type.
Suggestions
Reduce the main 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 and full CRUD functions into separate reference files (e.g., COMPONENTS.md, VERSIONS.md, ROLES.md).
Remove redundant representations — choose either TypeScript functions OR curl examples OR the endpoint table, not all three covering the same operations.
Add explicit validation/verification steps for destructive operations: before deleteProject, check issue counts; before deleteComponent, verify moveIssuesTo target exists; before releaseVersion, check unresolved issue count.
Remove the TypeScript interface definitions entirely — Claude can infer these from the API responses and function signatures. Focus on the non-obvious details like project key rules and permission requirements.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. The full TypeScript type definitions, every CRUD function signature, curl examples duplicating the same information, 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 copy-pasted into a skill file. | 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 no pseudocode or vague instructions. | 3 / 3 |
Workflow Clarity | Steps are numbered (Step 1-9) providing a logical sequence, and the setupProject helper shows a multi-step workflow. However, there are no validation checkpoints or error-handling feedback loops for destructive operations like deleteProject, deleteComponent, or deleteVersion — operations that should have explicit verification steps. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with everything inline. The type definitions, all CRUD operations for 5+ resource types, curl examples, endpoint summary, and reference tables should be split into separate files. The skill references external docs but doesn't split its own content despite being extremely long. | 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
f772de4
- 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.