agentleFS
Sign inStart free
icarloscornejoicarloscornejo/doer/skills/jira/SKILL.md

jira

Skill0 starsChanged 7 days agoMITView on GitHub

Sets the Jira base URL for the current project. Invoke as "/wk:jira <url>" (e.g. /wk:jira https://jira.example.com). Per-project, not global: different repos can point at different Jira instances. Does not touch the token; use "/wk:setup" for the full guided flow including the token env var name.

62 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use confluence, meet and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SpillwaveSolutionsSkill

    confluence

    Manage Confluence documentation with downloads, uploads, conversions, and diagrams. Use when asked to "download Confluence pages", "upload to Confluence", "convert Wiki Markup", "sync markdown to Confluence", "create Confluence page", or "handle Confluence images".

    Also in 9 projects that use this

  • kv0906Skill

    meet

    Process meeting notes into structured notes with extracted decisions, blockers, and action items. Use for "/meet project type title" then paste notes.

    Also in 3 projects that use this

  • er1chuSkill

    monday

    Full Monday morning setup. Creates week folder, pulls carry-forward, and generates briefing in one pass. Use on Monday mornings or when the user says "monday", "start my week", or "monday morning".

    Also in 3 projects that use this

  • refly-aiSkill

    hubspot

    Integrate with HubSpot for CRM management. Use when you need to: (1) manage contacts and deals, (2) track sales pipelines, or (3) automate marketing and CRM workflows.

    Also in 4 projects that use this

  • koderoverSkill

    jenkins

    Jenkins CI/CD 操作。用于：(1) 触发 Jenkins 任务构建 (2) 查询任务状态和构建历史 (3) 获取构建日志 (4) 操作 Jenkins 节点和配置

    Also in 3 projects that use this

  • SentrySkill

    datadog

    Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository/source-code work, or ticketing.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 56 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run "${CLAUDE_PLUGIN_ROOT}/lib/helpers/jira.sh" set-url "<url>" from the repo root.

    line 17
  2. Very specific:

    If no <url> was given, ask for one (plain chat).

    line 19

“Common” is measured: kept by at least 6 in 10 of the 56 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/wk:jira - set this project's Jira base URL

Per-project, git-excluded. Run "${CLAUDE_PLUGIN_ROOT}/lib/helpers/workspace-guard.sh" acquire --no-lock first (steps 1-3 of lib/workspace-guard.md, not the per-ticket lock: this command is not ticket-scoped) so .doer/ is excluded before writing config.json.

  1. Run "${CLAUDE_PLUGIN_ROOT}/lib/helpers/jira.sh" set-url "<url>" from the repo root. Persists to this project's ./.doer/config.json.
  2. Confirm the saved URL.
  3. If no <url> was given, ask for one (plain chat); there is nothing sensible to default to.

This does not set or check the token. The token is full-env only ($JIRA_PAT by default, or whatever jira_token_env names) and is never persisted; use /wk:setup for the guided flow that also covers the token env var name, the Atlassian Cloud auth email (set-auth-email, required for *.atlassian.net), and verification.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free