Jira Rules Builder

    4

    Build, patch, and fix Jira Cloud automation JSON files for advanced rules, unique lookup variables, and HTML emails.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    jira-rules-builder

    Example session with this skill installed

    Create a Jira automation JSON for a weekly digest rule. Use a scheduled trigger with nosearch mode and a lookup issues action named tasks.

    • Read your context and instructions
    • Compiled the jira-rules-builder
    {
      "cloud": true,
      "rules": [{
        "name": "Weekly Digest",
        "state": "DISABLED",
        "trigger": { "type": "jira.jql.scheduled", "value": { "executionMode": "nosearch" } },
        "components": [{ "type": "jira.lookup.issues", "value": { "id": "_custom_tasks", "name": "tasks" } }]
      }]
    }
    

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Automate Jira Like a Pro

    Creating complex Jira Cloud automation rules via the standard UI can be limiting and error-prone. The Jira Rules Builder skill empowers developers to programmatically generate, patch, and fix Jira automation JSON files, enabling advanced configurations that are impossible through the web interface alone.

    What it does

    • Beyond UI Limits: Assign unique names to multiple lookup variables (Jira's UI defaults everything to `lookupIssues`), preventing data overwrites.
    • Smart Value Optimization: Corrects common syntax errors in smart values, such as improper prefixes inside iteration blocks.
    • Bug Prevention: Automatically fixes known Jira import issues, like the "convertLineBreaks" flag that destroys HTML email layouts or incorrect schema versions for email actions.
    • Structure Validation: Ensures the output JSON includes site-specific constants (ARIs, Account IDs) required for a successful import.

    Why use this skill?

    Prompting a generic AI to write Jira JSON often results in schema version mismatches or invalid triggers. This skill uses a specialized knowledge base of Jira's import/export schema—including specific fixes for Scheduled triggers, Rovo Agent steps, and complex JQL patterns for different project types (Team-managed vs. Classic).

    Supported Components

    • Triggers: Scheduled digests (CRON/Basic), Issue transitions, and JQL-based events.
    • Actions: Lookup Issues, Create Variable, Send Email (HTML supported), and Rovo Agent invocation.
    • Cross-Platform: Works with both Next-gen (Team-managed) and Classic Jira project architectures.

    • Sites must manually provide ARI/Account IDs from an existing export for successful import.
    • Cannot bypass Jira's internal API limits or project permission restrictions.
    • HTML emails require manual CSS inlining.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 7 months ago

    Permissions

    Read Files

    File Scopes

    *.json

    Reads user-provided Jira export JSON files. Writes patched JSON to local filesystem. No external API calls made by the skill itself.

    Listed7 months ago

    What's inside

    Frequently Asked Questions

    This skill allows you to programmatically define multiple 'Lookup Issues' variables with unique names, overcoming the Jira UI limitation where all lookup results are forced into a single, overwriting variable named `lookupIssues`.

    The skill includes a specialized fix for the 'convertLineBreaks' flag, ensuring that imported JSON maintain original HTML formatting for emails rather than having layout-breaking line breaks automatically inserted.

    Yes, it is fully compatible with both Team-managed (Next-gen) and Classic project architectures, and it correctly maps the specific ARIs and Account IDs required for cross-project functionality.

    This skill is designed for use within AI agent platforms; you provide the automation logic requirements, and the skill generates a validated, import-ready JSON file that you can upload directly to your Jira Cloud global automation settings.

    Unlike generic AI, this skill utilizes a specialized knowledge base of Jira's internal schema versions and smart value syntax rules to prevent common errors in Scheduled triggers and complex JQL patterns.

    New in Workflow Automation