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 could benefit from slightly more detail about what specific authentication tasks it covers (e.g., token generation, OAuth setup, connection testing). Overall it performs well for skill selection purposes.
| 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 is highly actionable with executable code and concrete examples, but is severely bloated by including three full language implementations of the same basic auth pattern inline. The content would benefit greatly from picking one canonical implementation and linking to alternatives, and from extracting the JiraClient class and rate limiting into separate reference files. The workflow structure is inconsistent with orphaned 'Step 2/3' headers.
Suggestions
Pick one primary language implementation inline and move alternatives to a separate EXAMPLES.md or IMPLEMENTATIONS.md file to dramatically reduce token usage.
Remove the Python load_env() helper and the TypeScript JiraClient class from the main skill - Claude can write these trivially. Focus on the auth header pattern and validation endpoint only.
Fix the orphaned 'Step 2' and 'Step 3' headers by either adding 'Step 1' or restructuring as a coherent numbered workflow with a validation checkpoint after credential setup.
Extract rate limiting details and the retry handler into a separate RATE_LIMITING.md file, referenced from the main skill with a one-line summary.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity: includes three full language implementations (Node.js, Python, TypeScript) for the same basic auth pattern, a full JiraClient class, a load_env helper Claude could write trivially, and explains concepts like base64 encoding that Claude already knows. The Python .env loader is boilerplate Claude doesn't need spelled out. | 1 / 3 |
Actionability | Provides fully executable code in multiple languages, concrete curl commands, expected response JSON, and specific environment variable setup. Everything is copy-paste ready with real patterns. | 3 / 3 |
Workflow Clarity | The TypeScript section has numbered steps (Step 2, Step 3) but Step 1 is missing (it's buried in the earlier 'Implementation Pattern' section). The overall flow from setup to validation is present but not cleanly sequenced. There's no explicit validation checkpoint for credential setup before proceeding to API calls. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content (~200 lines) with three full language implementations inline. The rate limiting handler, JiraClient class, and detailed Python .env loader could all be in separate reference files. No content is split out despite clear opportunities. | 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
f772de4
- 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.