CtrlK
BlogDocsLog inGet started
Tessl Logo

jira-projects

Manage Jira projects. Use when listing projects, getting project configuration, retrieving issue types, or managing components and versions.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

A highly actionable, well-structured reference whose TypeScript and curl examples are copy-paste ready and cover the common cases. Main gaps are the absence of validation/error-handling guidance and a single inlined file where some reference material could be split out.

Suggestions

Add a brief error-handling note for the workflow (e.g., how to detect a 404 on a bad project key, or pagination exhaustion) so Step 1–5 form a feedback-aware sequence.

Consider moving the TypeScript interface definitions and/or curl examples into a references/ file, keeping SKILL.md as a concise overview that links out.

Trim the redundant "Purpose" line, which restates the frontmatter description verbatim in slightly different words.

DimensionReasoningScore

Conciseness

The body is dominated by lean, executable TypeScript and curl with no padding about what Jira is, though the "Purpose" line restates the description and the Version History date is mildly time-sensitive.

4 / 5

Actionability

Copy-paste-ready TypeScript functions and curl commands cover all five common operations, with typed interfaces and a concrete endpoint summary table.

5 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced and each retrieval is concrete, but there are no validation/error-handling checkpoints; acceptable since the operations are read-only GETs rather than destructive or batch ops.

4 / 5

Progressive Disclosure

Well-organized into labeled sections (Purpose, Prerequisites, Implementation Pattern, curl Examples, API Summary, Common Mistakes) with one external reference link, though everything is inlined in a single ~210-line file with no bundle files.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concisely covers what the skill does and when to use it with concrete, natural trigger phrases. Only minor weakness is the lack of synonyms/alternate phrasings for the trigger terms.

DimensionReasoningScore

Specificity

"Manage Jira projects" plus four concrete actions ("listing projects, getting project configuration, retrieving issue types, or managing components and versions") gives comprehensive, specific coverage of the skill's capabilities.

5 / 5

Completeness

It explicitly states both what ("Manage Jira projects" with the enumerated actions) and when ("Use when listing projects...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"listing projects, getting project configuration, retrieving issue types, ... components and versions" are natural Jira terms users would say, but synonyms and alternate phrasings are absent, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Manage Jira projects" carves a clear niche distinct from sibling skills like jira-auth, with triggers (projects, issue types, components, versions) unlikely to fire for the wrong skill.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.