New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Jira Issue

by sillsdev in sillsdev/FieldWorks

Write and file an LT Jira issue -- bug, feature or task -- that a triager can act on from the first line.

Custom licenceAuto-check passed

Install Jira Issue

skills CLI
$ npx skills add sillsdev/FieldWorks --skill jira-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sillsdev/FieldWorks jira-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sillsdev/FieldWorks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/jira-issue .claude/skills/jira-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
jira-issue
GitHub stars
110
Token cost
~1.1k tokens
SKILL.md length
564 words
Files
7 (incl. references)
Skills in repo
29
Repo updated
First seen
Licence
Custom licence

At a glance

Write and file an LT Jira issue -- bug, feature or task -- that a triager can act on from the first line.

  • Works in 3 steps: the duplicate table (Phase 2) → the three lede lines (Phase 3) → permission to post (Phase 5)
  • Create a Jira issue
  • SKILL.md covers Phases, The checks, Non-negotiable and Lede labels, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Jira Issue is an agent skill from sillsdev/FieldWorks. Write and file an LT Jira issue -- bug, feature or task -- that a triager can act on from the first line. Use whenever asked to file, raise, report or create a Jira issue or LT ticket, to turn a user report or a finding into a ticket, or to restructure a ticket that buries its point. Interviews, hunts duplicates before drafting, gets a three-line lede approved, and moves the analysis to a comment.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/bug-track.md`, `references/duplicates.md` and `references/examples.md`).

It works with Jira. The repository describes itself as: FieldWorks is a suite of software tools for language and cultural data, with support for complex scripts.

When your agent uses it

  • Create a Jira issue
  • Turn a user report
  • A finding into a ticket
  • Restructure a ticket that buries its point

Example prompts

  • “/jira-issue”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. the duplicate table (Phase 2)
  2. the three lede lines (Phase 3)
  3. permission to post (Phase 5)

What it can do on your machine

Read from SKILL.md and the folder at commit 44b1d04. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Jira Issue loads about 1.1k tokens when it runs, and up to ~6k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 564 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~103
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 564 words (~1,144 tokens).

“Jira Data Center has no {expand}. Nothing folds away, so length in the description is length on the screen for every reader, permanently. Keep the description short and put the depth in the first comment.”

— opening of SKILL.md by sillsdev, Custom licence
name
jira-issue
argument-hint
Optional: the raw report, a finding, or an existing LT-XXXXX to restructure
user-invocable
true

Read the full SKILL.md on GitHub

Files

SKILL.md and 6 other files (references) in .claude/skills/jira-issue of sillsdev/FieldWorks.

  • SKILL.md
  • references/bug-track.md
  • references/duplicates.md
  • references/examples.md
  • references/feature-track.md
  • references/format.md
  • references/publish.md

Open the folder on GitHubat commit 44b1d04

Compare with similar skills

Jira Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Jira Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jira Issue this skillsillsdev/FieldWorks110—~1.1kAutomated safety check: PassCustom licence
Management Talkthananon/9arm-skills3.2k—~3.2kAutomated safety check: PassNone
YugabyteDB Issue Creatoryugabyte/yugabyte-db11k—~2kAutomated safety check: PassCustom licence
Dynamo Jira TicketDynamoDS/Dynamo2k—~1.1kAutomated safety check: PassApache-2.0
Code Reviewcroffasia/itsaplan895—~2kAutomated safety check: PassAGPL-3.0
Connect Apps with ComposioComposioHQ/awesome-claude-skills77k3 repos~557Automated safety check: PassNone

Similar skills

  • Management Talk

    thananon/9arm-skills

    Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…

    3.2k GitHub stars~3.2k tokensUpdated 3 mo ago
    Productivity & AutomationAuto-check passed

  • YugabyteDB Issue Creator

    yugabyte/yugabyte-db

    Creates a GitHub issue or JIRA ticket for a YugabyteDB change or bug, after scrubbing customer data, secrets and unreleased details from anything public.

    11k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed

  • Dynamo Jira Ticket

    DynamoDS/Dynamo

    Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.

    2k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Code Review

    croffasia/itsaplan

    A skill your agent uses when reviewing code — a diff, a merge request, a file, a directory, or a feature.

    895 GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed

  • Connect Apps with Composio

    ComposioHQ/awesome-claude-skills

    Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.

    77k GitHub starsUsed in 3 repos~557 tokens
    Productivity & AutomationAuto-check passed

  • PR Body

    SAP/spartacus

    Official

    A skill your agent uses when the user asks to generate, write, or draft a pull request (PR) body or description for the current branch.

    784 GitHub stars~499 tokensUpdated today
    DevelopmentAuto-check passed

More from sillsdev/FieldWorks

All 29 skills in this repo

  • Atlassian Readonly Skills

    sillsdev/FieldWorks

    Read-only Python utilities for Jira (SIL Data Center): fetch an issue, search with JQL, read transitions, links, worklogs, agile boards and projects.

    110 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Atlassian Skills

    sillsdev/FieldWorks

    Python utilities for Jira (SIL Data Center) covering issue management, JQL search, workflows and transitions, links, agile boards, worklogs and projects.

    110 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Fieldworks Winapp

    sillsdev/FieldWorks

    Control and document the FieldWorks desktop application with WinForms MCP or WinApp MCP.

    110 GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Convert Slice

    sillsdev/FieldWorks

    Drive the conversion of one legacy slice type to the Avalonia detail view through analysis, developer alignment, integration-test planning, route/exemplar mapping, design, and scaffold/implement.

    110 GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Dependabot Consolidation

    sillsdev/FieldWorks

    Combine several open Dependabot pull requests into a single branch and PR: enumerate the open Dependabot PRs, cherry-pick them onto fresh main, rewrite commit messages to satisfy…

    110 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Fieldworks Semantic Render Parity

    sillsdev/FieldWorks

    Capture or review FieldWorks parity evidence: semantic snapshots, render/visual baselines, layout parity, failure artifacts, XML view definitions, and the Avalonia presentation IR.

    110 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Works with

Questions about Jira Issue

What does Jira Issue do?

Write and file an LT Jira issue -- bug, feature or task -- that a triager can act on from the first line. Jira Issue is an agent skill from sillsdev/FieldWorks. Write and file an LT Jira issue -- bug, feature or task -- that a triager can act on from the first line.

When should I use Jira Issue?

Jira Issue fits situations like: create a Jira issue; turn a user report; A finding into a ticket; restructure a ticket that buries its point.

How do I install Jira Issue in Claude Code?

Run `npx skills add sillsdev/FieldWorks --skill jira-issue -a claude-code`. Or copy the skill folder (.claude/skills/jira-issue in sillsdev/FieldWorks) into .claude/skills/jira-issue in your project. Claude Code loads it when a task matches its description.

How do I install Jira Issue in Codex?

Run `npx skills add sillsdev/FieldWorks --skill jira-issue -a codex`. Or copy the skill folder (.claude/skills/jira-issue in sillsdev/FieldWorks) into .agents/skills/jira-issue in your project. Codex loads it when a task matches its description.

Can I use Jira Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sillsdev/FieldWorks --skill jira-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jira-issue, .gemini/skills/jira-issue, .github/skills/jira-issue and .opencode/skills/jira-issue in your project.

What does Jira Issue need to run?

SKILL.md names no scripts, command-line tools or credentials: Jira Issue is instructions for the agent only.

Does Jira Issue access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Jira Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Jira Issue use?

Jira Issue has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Jira Issue use?

About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.9k tokens, read only when the agent opens those files.

What are the alternatives to Jira Issue?

Skills that share tags, products or a category with Jira Issue: Management Talk (thananon/9arm-skills, 3.2k stars), YugabyteDB Issue Creator (yugabyte/yugabyte-db, 11k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars) and Code Review (croffasia/itsaplan, 895 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jira Issue?

sillsdev (a GitHub organization) maintains it in sillsdev/FieldWorks, which has 110 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 7, 2026.

Source: sillsdev/FieldWorks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.