noob-ticket-cache

Name: noob-ticket-cache
Availability: InStock
Author: ganeshgaxy

Cache and reuse Jira/Confluence ticket context data with TTL-managed access.

Updated Apr 4, 2026

Search Tags:#context #mcp #cache #jira #confluence #data-fetch #ticket-context

Ready to run

npx skills add https://github.com/ganeshgaxy/apps-for-testing --skill noob-ticket-cache

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: noob-ticket-cache
Source: https://github.com/ganeshgaxy/apps-for-testing/tree/main/.claude/skills/noob-ticket-cache
Command: npx skills add https://github.com/ganeshgaxy/apps-for-testing --skill noob-ticket-cache

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetch and cache ALL ticket context in one pass. Other skills call this first instead of fetching individually.

Core Features & Use Cases

Cache-first rule: NEVER call Jira/Confluence MCP tools directly. Always check cache first, only call MCP on a miss, then save immediately.
Unified ticket context types: ticket_info, remote_links, comments, parent_issue, grandparent_issue, linked_tickets, confluence:<pageId>.
Use case: Preload all relevant ticket data before downstream skills to reduce latency and API calls.

Quick Start

From an orchestrator or any skill, run noob-tester ticket-context get <TICKET-ID> to load and cache all context types for that ticket.

Frequently Asked Questions about noob-ticket-cache

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I cache Jira and Confluence ticket context to avoid repeated API calls?▼

You can cache Jira and Confluence ticket context in one pass by fetching all relevant ticket data types simultaneously and storing them for downstream skills to reuse, avoiding individual API calls.

What ticket context types can I fetch and cache from Jira and Confluence?▼

You can cache unified ticket context types including ticket_info, remote_links, comments, parent_issue, grandparent_issue, linked_tickets, and specific Confluence pages identified by pageId.

How do I preload ticket data before running downstream Jira workflows?▼

Run the ticket-context get command with your target ticket ID to load and cache all context types in one pass, preloading data before downstream skills execute to reduce latency.

When should I invalidate or purge cached Jira ticket data?▼

Use the provided invalidate and purge commands when ticket data becomes stale or needs complete removal, utilizing TTL-managed cache to automatically handle expiration for Jira and Confluence context.

Does this cache-first approach work with existing Jira and Confluence MCP tools?▼

This approach works alongside Jira and Confluence MCP tools by enforcing a cache-first rule: it checks the cache before any MCP tool call, only fetching from MCP on a miss and saving immediately.