jira-projects
Manage Jira projects. Use when listing projects, getting project configuration, retrieving issue types, or managing components and versions.
Install with Tessl CLI
npx tessl i github:NeverSight/skills_feed --skill jira-projects76
Quality
70%
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-projects/SKILL.mdDiscovery
75%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 functional description that covers the basics well with explicit 'Use when' guidance and clear Jira-specific focus. However, it could benefit from more specific action verbs and broader trigger term coverage to help users find it with natural language queries.
Suggestions
Add more specific concrete actions like 'create projects', 'configure workflows', 'add/remove components' instead of generic 'manage'
Include additional trigger terms users might naturally say such as 'JIRA', 'project settings', 'issue type schemes', or 'release versions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jira projects) and lists some actions (listing projects, getting configuration, retrieving issue types, managing components and versions), but the actions are somewhat generic and could be more concrete about specific operations. | 2 / 3 |
Completeness | Clearly answers both what ('Manage Jira projects') and when ('Use when listing projects, getting project configuration, retrieving issue types, or managing components and versions') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Jira', 'projects', 'issue types', 'components', 'versions', but misses common user variations like 'JIRA', 'project settings', 'sprints', 'boards', or specific actions users might request. | 2 / 3 |
Distinctiveness Conflict Risk | The Jira-specific focus with explicit mention of project configuration, issue types, components, and versions creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 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 solid, actionable code examples with good API coverage and helpful curl alternatives. However, it's verbose with repetitive interface definitions that inflate token count, and the numbered 'steps' are actually independent operations rather than a true workflow. The skill would benefit from consolidation and clearer separation between quick-start content and reference material.
Suggestions
Move TypeScript interface definitions to a separate REFERENCE.md file, keeping only essential function signatures in SKILL.md
Add error handling examples and validation patterns (e.g., checking if project exists, handling pagination exhaustion)
Consolidate the 5 'steps' into a Quick Start section with one example, then list other operations as an API reference table
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes verbose interface definitions that Claude could infer. The TypeScript types add bulk without being strictly necessary for understanding the API patterns. | 2 / 3 |
Actionability | Provides fully executable TypeScript code and curl examples that are copy-paste ready. Each function is complete with proper typing and parameter handling. | 3 / 3 |
Workflow Clarity | Steps are labeled 1-5 but they're independent operations, not a sequential workflow. The 'Common Mistakes' section hints at validation concerns (pagination, archived projects) but doesn't provide explicit validation checkpoints or error handling patterns. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic with all code inline. The interface definitions and multiple similar functions could be split into a reference file, with SKILL.md showing just the quick-start pattern. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.