Files
stack/skills/glpi-create/SKILL.md
Jason Woltje 7bc2dfb6c8
All checks were successful
ci/woodpecker/pr/ci Pipeline was successful
skills: add glpi-* family (solve, followup, sweep, list, create)
GLPI helpdesk workflow skills written against the portable
tools/glpi/ tooling (session-init.sh, ticket-list.sh, ticket-create.sh),
cross-linked via [[glpi-*]]:

- glpi-solve    — close a ticket by setting status Solved (5); GLPI auto-closes
- glpi-followup — add a followup via the top-level /ITILFollowup endpoint
- glpi-sweep    — read-only hunt for done-but-open tickets needing Solve
- glpi-list     — query tickets by status/recency
- glpi-create   — open a new ticket

Core rule encoded: completing work means setting status Solved, not just
posting a resolution followup (a followup documents; only Solved auto-closes).

Note: illustrative examples in the bodies are USC-flavored (M2M / helpdesk
ticket numbers) and can be genericized in review if preferred.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019GjBgrb9tHgvq414Fqj37c
2026-07-20 18:04:53 -05:00

1.2 KiB

Skill: glpi-create — Open a New GLPI Ticket

Create a new GLPI helpdesk ticket. Mutates GLPI — confirm the details before running.

When to use

  • Logging a new incident or request that should live in the helpdesk queue.

Required information

  • title — short subject line.
  • content — description of the issue / request.

Optional

  • priority1=VeryLow, 2=Low, 3=Medium (default), 4=High, 5=VeryHigh, 6=Major.
  • type1=Incident (default), 2=Request.

Command

Wraps the existing tooling:

~/.config/mosaic/tools/glpi/ticket-create.sh \
  -t "<title>" \
  -c "<content>" \
  [-p <priority>] \
  [-y <type>] \
  [-f json]

Example:

~/.config/mosaic/tools/glpi/ticket-create.sh \
  -t "Paint-area camera install" \
  -c "Ordered 2 cameras for Paint and stock; schedule mounting + NVR config." \
  -p 3 -y 2

After creating

  • Note the returned ticket ID — you'll need it for glpi-followup and glpi-solve.
  • If it should also be tracked as brain work, add a matching task (see the add-task skill).

Guardrails

  • Confirm title/content/priority with the user before creating — a ticket is outward-facing.
  • Never echo GLPI tokens.