file-feedback

Submit and track feedback on automated-researcher scaffold tooling and operations.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/antondelafuente/automated-researcher --skill file-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-feedback
Source: https://github.com/antondelafuente/automated-researcher/tree/main/plugins/feedback-loop/skills/file-feedback
Command: npx skills add https://github.com/antondelafuente/automated-researcher --skill file-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of reporting operational issues, tooling friction, and providing feedback on the automated-researcher scaffold, allowing users to efficiently document and track improvements.

Core Features & Use Cases

  • Report Operational Issues: File feedback about tooling or documentation friction.
  • File Product Bugs or Ideas: Document and route product bugs or feature requests to the configured issue tracker.
  • Experiment Close Retro: Use to summarize lessons learned from an experiment's execution.
  • Use Case: After completing an experiment, use the file-feedback skill to submit a report on encountered issues or suggestions for improvement.

Quick Start

Submit a feedback report for the 'experiment close retro' by running the command: file-feedback report experiment close retro

Frequently Asked Questions about file-feedback

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

FAQPage Schema
How do I report operational issues and tooling friction for the automated-researcher scaffold?

You can report operational issues and tooling friction for the automated-researcher scaffold by submitting a feedback report through the file-feedback skill to document and track improvements.

What is the best way to file product bugs or feature requests for automated-researcher experiments?

The best way to file product bugs or feature requests for automated-researcher experiments is using the file-feedback skill, which routes your reports to a configured issue tracker for product development.

Can I summarize lessons learned from an experiment's execution using a feedback report?

Yes, you can summarize lessons learned from an experiment's execution by running the file-feedback skill to submit an experiment close retro report on encountered issues and suggestions.

Do I need access to an issue tracking system to submit feedback on automated-researcher?

Yes, you need access to an issue tracking system and configured feedback channels, because the file-feedback skill requires these to properly route and track product feedback and bug reports.

When should I document experimental analysis and operational feedback during product development?

You should document experimental analysis and operational feedback during product development immediately after completing an experiment, using the file-feedback skill to submit reports on encountered operational issues.