jira-project-management
Administer Jira projects. Use when creating/archiving projects, managing components, versions, roles, permissions, or project configuration.
60
71%
Does it follow best practices?
Impact
—
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 related skills like Jira issue management.
| 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) and 'when' (explicit 'Use when' clause listing specific triggers: 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 project administration tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Jira project administration, which is a distinct niche. The focus on project-level configuration (components, versions, roles, permissions) distinguishes it 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 API reference document masquerading as a skill file. While highly actionable with executable code and concrete examples, it is extremely verbose and redundant — presenting the same information in TypeScript functions, curl examples, AND an endpoint summary table. The content would benefit enormously from splitting into a concise overview SKILL.md with references to detailed API files, and adding validation/confirmation workflows for destructive operations.
Suggestions
Split into SKILL.md (overview + quick start + common patterns) and separate reference files like API_REFERENCE.md (endpoint table), TYPESCRIPT_HELPERS.md (full function implementations), and CURL_EXAMPLES.md
Remove TypeScript type definitions and full function bodies from SKILL.md — Claude can construct these from the API endpoint table alone. Keep only 1-2 representative examples.
Add explicit validation/confirmation workflows for destructive operations (delete project, delete component, delete version) with checkpoints like 'verify issue counts before deletion'
Eliminate the triple-redundancy of TypeScript code + curl examples + endpoint table — pick one primary format and reference the others in supplementary files
| 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 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 proper HTTP methods, headers, and request bodies. | 3 / 3 |
Workflow Clarity | Steps are numbered (Step 1-9) but they represent API surface areas, not a sequential workflow. Destructive operations like deleteProject and deleteComponent lack explicit validation checkpoints or confirmation steps. The 'Common Mistakes' section partially compensates but there are no feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | Monolithic wall of content with no bundle files to offload detail. The full type definitions, all CRUD operations, curl examples, endpoint summary table, and reference tables are all inline. The type definitions and detailed function implementations should be in separate reference files, with SKILL.md providing a concise overview and links. | 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
df877a9
- 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.