jira-auth
Authenticate with Jira Cloud REST API using API tokens. Use when setting up Jira connections, validating credentials, or handling rate limiting.
67
58%
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-auth/SKILL.mdQuality
Discovery
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.
The description is well-structured with a clear 'Use when' clause that explicitly defines trigger scenarios, and it occupies a distinct niche around Jira authentication. However, the specificity of concrete actions could be improved (e.g., mentioning token generation, header configuration, retry logic), and trigger terms could include more natural user language variations.
Suggestions
Add more specific concrete actions like 'generate API tokens, configure authentication headers, implement retry logic for rate-limited requests'.
Include additional natural trigger terms users might say, such as 'Jira login', 'Atlassian API', 'Jira API key', or 'Jira connection error'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jira Cloud REST API) and some actions (authenticate, validate credentials, handle rate limiting), but doesn't list comprehensive concrete actions like creating issues, querying boards, or managing projects. | 2 / 3 |
Completeness | Clearly answers both 'what' (authenticate with Jira Cloud REST API using API tokens) and 'when' (setting up Jira connections, validating credentials, or handling rate limiting) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Jira', 'API tokens', 'credentials', and 'rate limiting', but misses common user variations like 'Jira login', 'Jira setup', 'Jira connection issues', 'Atlassian', or 'Jira API key'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific to Jira Cloud REST API authentication, which is a clear niche unlikely to conflict with other skills. The focus on authentication/credentials/rate limiting distinguishes it from general Jira usage skills. | 3 / 3 |
Total | 10 / 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.
The skill provides highly actionable, executable code for Jira authentication across multiple languages, which is its main strength. However, it is excessively verbose—repeating similar patterns in three languages inline, including boilerplate Claude can generate, and lacking any progressive disclosure to separate files. The workflow structure is disjointed with inconsistent step numbering.
Suggestions
Move language-specific implementations (Node.js, Python, TypeScript) into separate referenced files and keep only one canonical example inline (e.g., the curl test or a single language pattern).
Remove boilerplate Claude already knows how to write (e.g., the Python .env loader, basic base64 encoding explanations, the full JiraClient class) and focus on Jira-specific details like the exact auth header format and API endpoint paths.
Establish a clear numbered workflow: 1) Configure .env → 2) Test with curl → 3) Verify success response, with explicit validation at each step.
Cut the 'Common Mistakes' section to just the Jira-specific gotcha (API token vs password) since the others (base64 encoding, 'Basic ' space) are general HTTP knowledge.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is very verbose. It includes three full implementation patterns (Node.js, Python, TypeScript) with significant overlap, a full JiraClient class, a load_env helper Claude could write trivially, and explains basic concepts like environment variables. The Python .env loader and TypeScript class are boilerplate Claude already knows how to produce. Much of this could be cut to essential patterns only. | 1 / 3 |
Actionability | The skill provides fully executable code in multiple languages, concrete curl commands for testing, specific environment variable names, and copy-paste ready authentication headers. The code examples are complete and runnable. | 3 / 3 |
Workflow Clarity | There's a reasonable sequence (set up env vars → implement auth → validate connection), but the steps are not explicitly numbered as a workflow. The TypeScript section awkwardly introduces 'Step 2' and 'Step 3' without a 'Step 1', suggesting structural confusion. There's no explicit validation checkpoint after credential setup before proceeding to API calls. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to separate files for detailed implementations. The three full language implementations, rate limiting details, and the JiraClient class could all be split into referenced files. Everything is inline, making the skill very long for what should be an authentication overview. | 1 / 3 |
Total | 7 / 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.
- Repository
- NeverSight/skills_feed
- Commit
e437c3c
- 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.