Arkiv Feedback

Walk the user through reporting a bug or feature request to Arkiv-Network/reported-issues, then submit it on their behalf — without making them touch GitHub's UI.

The skill mirrors the two GitHub issue forms hosted on the repo (1-bug.yml, 2-feature-request.yml). Keep the questions, options, and required/optional split aligned with those files. If they change, update references/bug-form.md and references/feature-form.md.

When to invoke

Trigger on any of these signals from the user:

• "I want to report a bug in Arkiv" / "file an issue" / "Arkiv is broken"
• "the network is down" / "the SDK is throwing X" / "Kaolin/Braga is unreachable"
• "I have an idea for Arkiv" / "I'd like a feature" / "Arkiv should support X"

Do not invoke for:

• General usage questions — point the user to the Arkiv Discord or docs instead.
• Issues with applications built on Arkiv — those go to the application's own team.
• Security disclosures — those need the private channel; tell the user to email or open a private security advisory directly, do not file a public issue.