jira-auth

Authenticate with Jira Cloud REST API using API tokens. Use when setting up Jira connections, validating credentials, or handling rate limiting.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete executable examples, but it is verbose and repeats the auth pattern across four languages. Workflow sequencing and progressive disclosure are adequate but not strong, with inline-heavy content and missing local bundle files.

Suggestions

Trim redundancy by consolidating the auth-header construction into one canonical snippet and referencing it from each language example, and drop explanations of basic concepts like base64 encoding that Claude already knows.

Make the workflow a single explicit numbered sequence (setup env -> build header -> create client -> validate connection) with labels applied consistently across languages, and add an explicit validate->fix->retry checkpoint for credential setup.

Move the full client implementation, rate-limiting details, and curl examples into separate reference files (e.g. CLIENT.md, RATE_LIMITS.md) and ensure the referenced local files (scripts/run.js, .env.example) actually exist in the bundle.

Dimension	Reasoning	Score
Conciseness	The 260-line body re-explains things Claude knows (base64 header encoding, manual .env parsing) and repeats the same auth-header pattern across Node.js, Python, TypeScript, and curl, so it is mostly efficient but padded and could be tightened.	2 / 3
Actionability	Provides fully executable code in multiple languages, concrete commands ('node scripts/run.js test'), real endpoints ('/rest/api/3/myself'), and an expected success response — copy-paste ready.	3 / 3
Workflow Clarity	Steps are present and partially labeled ('Step 2: Create Jira Client', 'Step 3: Validate Connection') with a connection-validation step, but Step 1 is implicit, labels only appear under TypeScript, and the credential-setup path lacks an explicit validate->fix->retry feedback loop.	2 / 3
Progressive Disclosure	At 260 lines the monolithic body inlines client implementation, rate-limiting, and curl examples that could be split out, and the referenced local files (scripts/run.js, .env.example) are not present in the bundle, leaving navigation only loosely signaled.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 concise, concrete, and clearly answers both what the skill does and when to use it, in third-person voice. It is among the stronger examples with explicit trigger guidance and a clear niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Authenticate with Jira Cloud REST API using API tokens' plus 'setting up Jira connections, validating credentials, or handling rate limiting' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Authenticate with Jira Cloud REST API using API tokens') and when ('Use when setting up Jira connections, validating credentials, or handling rate limiting') with explicit triggers.	3 / 3
Trigger Term Quality	Includes natural terms a user would say — 'Jira connections', 'validating credentials', 'API tokens', 'rate limiting' — giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	Scoped to Jira Cloud REST API token authentication with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: NeverSight/skills_feed
Commit: ff6a653

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.