jira-auth
Authenticate with Jira Cloud REST API using API tokens. Use when setting up Jira connections, validating credentials, or handling rate limiting.
73
66%
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
89%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 solid, well-structured description with a clear 'Use when' clause and good trigger terms specific to Jira authentication. Its main weakness is that the capability actions are somewhat narrow — it focuses on authentication/connection rather than listing broader concrete operations, though this may be intentional if the skill is genuinely scoped to authentication only.
| 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 projects, etc. The actions mentioned are somewhat narrow and focused on connection setup. | 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 strong natural keywords users would say: 'Jira', 'API tokens', 'credentials', 'rate limiting', 'Jira Cloud', 'REST API'. These are terms a user would naturally use when needing help with Jira authentication. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets Jira Cloud REST API authentication, which is a clear niche. Unlikely to conflict with general API skills or other Jira skills focused on issue management, since this is scoped to authentication and connection setup. | 3 / 3 |
Total | 11 / 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 across multiple languages but suffers significantly from verbosity and poor organization. Three full language implementations for the same authentication pattern is excessive for a skill file, and the content would benefit greatly from being split into a concise overview with references to language-specific implementation files. The workflow structure is inconsistent, with TypeScript steps numbered but disconnected from the Node.js and Python sections.
Suggestions
Reduce to one primary implementation language (e.g., Node.js) inline, and move Python/TypeScript variants to separate referenced files like PYTHON.md and TYPESCRIPT.md.
Remove the 'Common Mistakes' section — Claude already knows about base64 encoding and HTTP header formatting.
Create a clear, unified numbered workflow: 1) Set up .env, 2) Run test script, 3) Validate connection, 4) Handle errors — rather than mixing setup, implementation, and testing sections.
Move the rate limiting implementation and JiraClient class to separate reference files, keeping only the rate limit table and a brief note in the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is very verbose, providing three separate language implementations (Node.js, Python, TypeScript) for essentially the same authentication pattern. The Python .env loader, the full JiraClient class, and the TypeScript reference pattern are redundant. The 'Common Mistakes' section explains things Claude already knows (base64 encoding, 'Basic ' header format). Much of this could be condensed to a single implementation pattern plus a curl example. | 1 / 3 |
Actionability | The skill provides fully executable code in multiple languages, concrete curl commands for testing, specific environment variable setup, and expected response formats. All code is copy-paste ready with real API paths and headers. | 3 / 3 |
Workflow Clarity | The TypeScript section has numbered steps (Step 2, Step 3) but Step 1 is missing (it's implied by the earlier sections). The overall flow from setup to validation is present but not cleanly sequenced as a unified workflow. There's no explicit validation checkpoint for credential setup before making API calls, though the validateJiraConnection function partially addresses this. | 2 / 3 |
Progressive Disclosure | The skill is a monolithic wall of text with all implementation details inline. Rate limiting, multiple language implementations, the full JiraClient class, and curl examples could all be split into separate reference files. No bundle files are provided despite the content being long enough to warrant splitting. The structure mixes concerns (env setup, three language implementations, rate limiting, curl testing) without clear navigation. | 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
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.