jira-auth
Authenticate with Jira Cloud REST API using API tokens. Use when setting up Jira connections, validating credentials, or handling rate limiting.
82
Quality
77%
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-auth/SKILL.mdDiscovery
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 well-structured skill description with a clear 'Use when' clause and good trigger terms specific to Jira authentication. The main weakness is that the capabilities could be more specific about what authentication actions are supported (e.g., token generation, refresh, storage). Overall, it effectively communicates its purpose and when to use it.
Suggestions
Add more specific concrete actions like 'generate tokens', 'store credentials securely', or 'refresh expired tokens' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jira Cloud REST API) and mentions some actions (authenticate, setting up connections, validating credentials, handling rate limiting), but doesn't list comprehensive concrete actions like specific authentication methods or token management operations. | 2 / 3 |
Completeness | Clearly answers both what (authenticate with Jira Cloud REST API using API tokens) and when (setting up Jira connections, validating credentials, handling rate limiting) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Jira', 'API tokens', 'credentials', 'rate limiting', 'Jira connections'. These are terms users would naturally use when needing authentication help with Jira. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Jira Cloud authentication specifically. The combination of 'Jira Cloud REST API', 'API tokens', and 'rate limiting' creates distinct triggers unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 authentication guidance with executable code examples and useful curl commands for testing. However, it suffers from verbosity by including multiple language implementations and could benefit from clearer workflow sequencing. The content would be stronger if trimmed to focus on one primary implementation with others in referenced files.
Suggestions
Consolidate to one primary language implementation (e.g., Node.js) and move Python/TypeScript alternatives to a separate IMPLEMENTATIONS.md file
Add a clear numbered workflow at the top: 1) Set up .env, 2) Validate with test script, 3) Integrate pattern into code
Remove the TypeScript 'reference pattern' section which duplicates the Node.js example without adding value
Move the JiraClient class and rate limiting retry logic to a separate ADVANCED.md or PATTERNS.md file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary verbosity - explaining what environment variables are, showing both Node.js and Python implementations when one would suffice, and the TypeScript 'reference pattern' adds redundancy. The content could be tightened significantly while preserving utility. | 2 / 3 |
Actionability | Provides fully executable code examples in multiple languages, concrete curl commands for testing, specific environment variable setup, and copy-paste ready authentication patterns. The code is complete and runnable. | 3 / 3 |
Workflow Clarity | Steps are present but not clearly sequenced as a workflow. The document jumps between setup, implementation patterns, and testing without a clear numbered sequence. Missing explicit validation checkpoints between credential setup and API usage. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the document is monolithic with ~200 lines that could benefit from splitting. The TypeScript client class and rate limiting could be separate reference files. References at the end are good but inline content is heavy. | 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.