kube-agents-feedback

Skill: kube-agents-feedback

When this skill applies

• A kanban card asks you to file a kube-agents report for the user — not to explain where reports go. For "how do I report a bug in kube-agents?", answer from the persona bullet and do not touch this skill.
• The submission target is the public feedback form behind https://gke-labs.github.io/kube-agents/feedback. It needs no GitHub or Google credential, so this path works even when the install's GitHub credential path is degraded.

The confirmation gate

• File only what the user has seen and approved. The card must carry the exact submission text and the line user-confirmed: yes — the front door's assertion that it showed the user this text and got a yes.
• No user-confirmed: yes, or a card that asks you to compose or improve the text yourself: do not file. Complete the card saying the front door must show the user the exact text and dispatch again with the confirmation line.
• Never edit the confirmed text — no trimming, no added environment detail, no rewording. If it looks wrong, that is a reason to send the card back, not to fix it yourself.

Redaction

• The broker refuses secret-shaped content (keys, tokens) outright. Cluster names, project ids, and log excerpts are your judgment: a submission is a public issue, so if the text carries identifiers the user did not visibly type themselves, stop and complete the card saying what would be exposed.

Filing

• Write the confirmed text, verbatim, as JSON in the card workspace:

  {
    "title": "<one-line summary, at most 120 characters>",
    "kind": "Bug | Feature request | Question | Other",
    "happened": "<what happened>",
    "expected": "<optional>",
    "environment": "<optional>",
    "user_confirmed": true
  }
  

• Run the helper once, from the card workspace so a rerun finds its own earlier attempt:

  python3 "$HERMES_HOME"/skills/kube-agents-feedback/scripts/file_feedback.py \
      submit --payload-file payload.json --state-dir .