Consult Bug Ticket

npx skills add https://github.com/peter-tu-zynkr/zynkr-skill-builder --skill consult-bug-ticket

When a client reports a defect — in a delivered assistant, in the platform, on the website — the report tends to die in the inbox. This skill turns one bug report into three artifacts in a single pass: a well-formed GitHub issue in the right repo, a CRM follow-up task on the client's deal so the sales side sees the open loop, and a threaded acknowledgment reply waiting as a Gmail draft so the client knows they were heard.

It is deliberately gated: nothing external is written until Peter approves the target repo, issue title, complete body, and severity at one hard gate. The public issue and the private CRM record carry different halves of the story — company + defect in the issue, person + thread in the CRM task — by design.

How this differs from its neighbours