gather-ticket-metadata

Collect ticket metadata into a JSON payload via a single shell call.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/qmu/workaholic --skill gather-ticket-metadata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gather-ticket-metadata
Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/gather-ticket-metadata
Command: npx skills add https://github.com/qmu/workaholic --skill gather-ticket-metadata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates the process of collecting and formatting essential ticket metadata (created_at, author, filename_timestamp) into a single, deterministic shell call, reducing manual steps and ensuring consistency.

Core Features & Use Cases

  • Single-call metadata gathering for ticket frontmatter.
  • Produces a JSON payload containing created_at, author, and filename_timestamp for seamless integration into ticket workflows.
  • Works in CI or local development environments to standardize ticket generation and auditing.

Quick Start

bash .claude/skills/gather-ticket-metadata/sh/gather.sh

Frequently Asked Questions about gather-ticket-metadata

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

FAQPage Schema
How do I gather ticket metadata for frontmatter in a single shell call?

You can gather ticket metadata for frontmatter by running a shell script that reads system time and git config, producing a JSON payload with created_at, author, and filename_timestamp without external libraries.

How do I automate collecting created_at and author fields for ticket creation?

Automate collecting created_at and author fields by executing a bash script that reads the system clock and git config to generate a deterministic JSON payload for ticket creation workflows.

Does this ticket metadata generation script work in CI environments?

Yes, the ticket metadata generation script works in CI environments, reading standard system time and git config to output consistent frontmatter data locally or during automated pipelines.

Do I need external libraries to generate a filename timestamp and author metadata?

No external libraries are needed to generate filename timestamps and author metadata, as the shell script relies solely on native bash commands, system time, and git configuration.

What's the best way to standardize ticket frontmatter across local and CI environments?

The best way to standardize ticket frontmatter is using a single shell call that deterministically extracts author and timestamp data from git config and the system clock, ensuring consistent JSON payloads.

Why does my ticket frontmatter metadata lack consistent author and timestamp fields?

Ticket frontmatter metadata lacks consistency when gathered manually, but a dedicated shell script resolves this by automatically extracting author and timestamp values from git and system time.