report

File bug reports and user feedback from Hermes sessions to a triage board.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/TechNickAI/hermes-config --skill report-technickai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report
Source: https://github.com/TechNickAI/hermes-config/tree/main/skills/report
Command: npx skills add https://github.com/TechNickAI/hermes-config --skill report-technickai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables users to file bugs or feedback from any Hermes platform session and routes the report to a shared triage board, with automated closed-loop notifications back to the reporter when resolved.

Core Features & Use Cases

  • Load automatically when the user signals such as "/report", "file a bug", "report a bug", "something's broken", "something's wrong", "that's weird", or similar phrases, across Telegram, Discord, Slack, and the CLI.
  • Build a structured markdown body including the exact user words, session context, and a transcript excerpt, and file it to the triage board with an idempotent submission. It also subscribes the reporter for done/blocked notifications.
  • Supports dual delivery paths: local board ownership (direct kanban API) or remote delivery via a webhook, with safe fallbacks to drop a local file if posting fails.
  • Provides privacy and triage guidance in knowledge references (triage runbook).

Quick Start

Say '/report' to file a bug or feedback from your Hermes session.

Frequently Asked Questions about report

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

FAQPage Schema
How do I file a bug report from a Hermes session across Telegram, Discord, or Slack?

To file a bug report from a Hermes session, trigger the Skill using phrases like "/report" or "file a bug". It captures your context and transcript, routing the structured report to a shared triage board.

What is the best way to route user feedback to a shared triage board?

Routing user feedback to a triage board is handled automatically by capturing session context and submitting it via a local kanban API or a remote webhook, ensuring structured delivery with safe fallbacks.

Does the bug triage process support automated closed-loop notifications upon resolution?

The bug triage process supports closed-loop notifications by automatically subscribing the reporter. When a report is resolved or blocked, a notification is wired back to the user across their original platform.

How do duplicate bug reports handle idempotency during submission?

Duplicate bug reports are managed through idempotent submissions within a short time window. This validates structured payloads and prevents redundant triage entries from being filed repeatedly.

What happens if posting a feedback report to the webhook fails?

If posting a feedback report to the remote webhook fails, the system uses safe fallbacks to drop a local file. This ensures the report is preserved even when the remote delivery path is unavailable.

Can I use this reporting tool with the CLI or is it limited to chat platforms?

You can use this reporting tool with the CLI as well as Telegram, Discord, and Slack. It loads automatically across all these contexts when you signal to file a bug or feedback.