Use the skill-run feedback issue form for one factual observation about activation, routing, evidence use, recipe discovery, content diagnosis, handoff, verification, or a required stop.
Describe what the agent did, missed, or made difficult. Include the intended outcome, relevant environment, server-visible behavior, and impact only when those details are safe to publish.
Do not publish prompts, outputs, or logs containing credentials, private identities, local paths, customer data, private repository material, account state, or proprietary server details.
When a report needs editing or privacy review, use the ignored tmp/ directory for a local draft. Remove restricted material and review the exact public title and body before creating the issue.
Do not maintain a second repository backlog or feedback ledger. GitHub Issues remains the source of truth for durable reports and their status.
- Use a bug report for deterministic validation, packaging, workflow, schema, or documentation defects.
- Use a feature request for a public skill, catalog, result-contract, or maintenance capability proposal.
- Use GitHub Discussions for questions and early ideas that are not yet actionable reports.
- Use private vulnerability reporting for credentials, private data exposure, or release security problems.