Twg Jira

What it does

The source routes known work items, JQL filtering, fuzzy discovery, transitions and field administration to different operations. It distinguishes candidate search results from authoritative item reads and uses live CLI help for command grammar. This is useful when a broad request must resolve to a specific site, item and supported action.

Best for

Teams with an authenticated TWG CLI environment who need to inspect Jira work or prepare a concrete update. The root twg skill supplies shared context; this companion concentrates on Jira semantics rather than every Atlassian product.

Tradeoffs and requirements

Several supported actions write comments, change status or administer configuration. Read access does not imply permission for those changes, and required custom fields may need a user decision. Live help and account permissions affect what is possible. This assessment did not authenticate to an Atlassian tenant, modify issues or test the CLI.

Unknown; inspect source requirements and supporting scripts.

Install from the source

First time installing a skill? Follow the walkthrough →

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/atlassian/twg-cli/tree/35710745f766fd19953d2a8a86e27cd193996598/skills/twg-jira --skill twg-jira

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Shell Or Package Install — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

Offline package integrity

A temporary folder-copy check, not an agent installation or runtime safety verdict.

8 files copied and checksummed from this exact source snapshot. No package code or installation scripts were executed.

Inventory SHA-256: 52580913403daac37ac06b8184453556582bddc481a520e3856a983aa70b607d

AI Craft Pad Skill Score

84/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

25/100

25

Originality

80/100

80

Static Safety

60/100

60

Supporting-file static inspection

Bounded source inspection, not a runtime security audit. This inspection does not execute code.

1 text files inspected at this exact repository snapshot. 6 files outside the inspection budget or type allowlist. Dependencies were not installed or independently audited.

• Network Client: 1 file — inspect context before use.

Absence of a pattern is not proof of safety. Permission needs and runtime behavior remain Unknown.

Suggested workflow

Resolve the site and item keys, read current state and relevant field metadata, then distinguish a proposed change from a completed one. Discover actual transitions and confirm the intended values before a consequential mutation.

How to judge the result

After an authorized change, read the item again and compare the resulting fields and status with the request. Keep candidate duplicate findings separate from confirmed duplicates, and never interpret a broad activity summary as the authoritative backlog.