Menu
Use Jirali to inspect, create, transition, reconcile, report on, and audit Jira work from an agent-safe CLI.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
macOS clipboard intelligence CLI for agents and power users. Use when working with the system clipboard, generating formatted Excel tables from CSV or JSON, editing clipboard table cells, building or editing nested HTML/Markdown lists, managing reusable HTML templates, or converting between RTF, HTML, plain text, and Jinja2. Triggers on clipboard read/write/inspect operations, Excel-pasteable HTML/SVG/PNG table generation, nested list generation/editing, reusable template capture/render/paste, privacy-aware clipboard history/watch/filter/prune/restore workflows, previewing rendered HTML without touching the clipboard, shell completions, doctor readiness checks, and agent-command templatization or batch rendering. Requires macOS. Binary must be built first with cargo build --release.
Use xli for deterministic, JSON-first Excel workbook operations: inspect, read, write, format, validate, template, batch edits, sheet management, and workbook creation from CSV/Markdown/JSON. Trigger on `.xlsx` automation, report generation, workbook validation, table import, formula edits, or atomic spreadsheet mutations.
Manage a file-based knowledge vault with YAML frontmatter, sidecar markdown, and JSONL indexing. Use when initializing or maintaining a knowledge base, attaching metadata to markdown or non-markdown assets, rebuilding or validating INDEX.jsonl, or searching vault records by metadata. Trigger on: "knowledge base", "vault", "frontmatter", "sidecar", "INDEX.jsonl", "document this query/template/skill", "search the vault", or "set up KB docs".
Use notionli for agent-safe Notion workspace operations: search, page reads, block edits, database/data-source inspection, row upserts, comments, users, files, snapshots, sync, and auditable dry-run writes. Trigger on Notion automation, schema discovery, database row edits, page/block mutations, or any task that needs structured Notion access.
Operate the lira CLI, a local agent-native task system where local tickets are local-first issue records decomposed into acceptance criteria plus atomic tasks. Use when the user wants to break down Jira/GitHub/local work into agent tickets; create, claim, work, comment on, sync, query, or close local tickets; manage acceptance criteria and atomic tasks; resolve GitHub sync conflicts; or expose local candidates and normalized issue projections for a Symphony-style runner through ~/.lira/.
Use barli to build and operate a macOS menu bar automation app that discovers Python functions via decorators and configures menus from YAML. Use when the user wants local menubar actions, hot-reloaded Python plugins, YAML-driven command menus, or lightweight GUI launchers for agent tools.
| name | jirali |
| description | Use Jirali to inspect, create, transition, reconcile, report on, and audit Jira work from an agent-safe CLI. |
Use jirali when Jira state needs to be read or changed from a shell workflow.
0: success2: fix command syntax3: search or update assumptions4: stop and ask a human for auth/permission help5: idempotent desired state already holds6: back off and retry later7: retry with validator-required fields8: narrow the query or increase timeoutjirali issue view ENG-123 --view-profile dev
jirali issue list --jql 'project = ENG ORDER BY updated DESC' --limit 20
jirali issue create --project ENG --type Task --summary 'Follow up'
jirali issue transition ENG-123 'In Progress'
jirali jql lint 'project = ENG AND status != Done'
jirali plan jira-state.yaml
jirali apply jira-state.yaml
jirali report velocity --jql 'project = ENG'
Use Markdown for ordinary comments and descriptions:
jirali comment add ENG-123 --markdown 'Ready for @reviewer'
Use raw ADF only when you already have valid ADF JSON:
jirali comment add ENG-123 --body-adf @comment.adf.json
When a named command does not yet expose a Jira endpoint directly, use:
jirali api GET /rest/api/3/issue/ENG-123
jirali graphql --query '{ ... }'
Credentials come from the active profile configured with jirali auth login.
For Atlassian Cloud, configure --site-url with the site root:
jirali auth login \
--method api-token \
--site-url https://example.atlassian.net \
--email you@example.com
Do not use the browser UI URL ending in /jira/ in docs or scripts. Jirali
normalizes that path defensively, but REST APIs live under the site root. Cloud
API tokens use Basic auth with email:api_token; personal API tokens are not
Bearer tokens.
If a Cloud token appears valid but REST calls return Client must be authenticated to access this resource, check whether it is a scoped token. The
scoped-token Jira gateway base is:
https://api.atlassian.com/ex/jira/{cloudId}/rest/api/3/...
Configure gateway mode with:
jirali auth login \
--method api-token \
--site-url https://example.atlassian.net \
--gateway \
--email you@example.com
--gateway discovers the cloudId. Agents can pass --cloud-id directly when
it is already known. The discovery endpoint is:
curl https://example.atlassian.net/_edge/tenant_info