methodic-feedback

Submits user feedback and gap reports to Chronicle's feedback endpoint and GitHub issues.

1|1|Updated May 9, 2026
One-click install
npx skills add https://github.com/methodic-research/skills --skill methodic-feedback-methodic-research
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: methodic-feedback
Source: https://github.com/methodic-research/skills/tree/main/plugins/chronicle/skills/feedback
Command: npx skills add https://github.com/methodic-research/skills --skill methodic-feedback-methodic-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires methodic-research.

What problem does it solve? When working with the Chronicle experiment platform, users and agents encounter SDK gaps, misbehaving MCP tools, or confusing APIs with no structured way to report them. This Skill captures that feedback immediately as a private Markdown report to Methodic's backend and optionally mirrors it as a public GitHub issue. ## Core Features & Use Cases - Proactive gap reporting: Automatically files feedback to Chronicle's private endpoint the moment an SDK, MCP, or API gap is encountered mid-task, limited to one report per distinct gap per session. - Error routing: Sends reproducible errors with type, message, and HTTP details to a fingerprinted error pipeline instead of plain feedback. - Confirmed public mirror: Drafts a GitHub issue on methodic-research/skills via the user's own gh auth, checks for duplicates, and only posts after explicit user confirmation. - Use Case: While running an experiment upload, the SDK cannot express a required workflow; the agent files a categorized gap report with a Markdown body and later offers to open a public issue. ## Quick Start Ask the agent to report a problem or request a feature with the Chronicle platform, for example by saying "file feedback that the dataset upload flow is confusing".

Frequently Asked Questions about methodic-feedback

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

FAQPage Schema
How do I report a bug or request a feature for the Chronicle platform?▼

Ask the agent to file feedback, and it submits a Markdown report to Chronicle's private feedback endpoint using chronicle.feedback.submit with a category of feedback, gap, or feature_request. At the end of the turn it can also offer to open a public GitHub issue with your confirmation.

How does the skill handle reproducible errors versus general feedback?▼

Reproducible errors with an error type, message, and HTTP details are routed to chronicle.feedback.report_error so they get fingerprinted and triaged. Everything else, such as impressions, gaps, and feature requests, goes through the plain feedback submit path.

Does the feedback skill post to GitHub automatically?▼

No. The private backend report is filed immediately, but the public GitHub issue on methodic-research/skills is only drafted and posted via your own gh auth after you explicitly confirm. If gh is missing or unauthenticated, the step is skipped silently.

What dependencies are required to submit Chronicle feedback?▼

You need pip install methodic-research with a version that ships the chronicle.feedback namespace, plus valid credentials in ~/.methodic created through the Methodic UI API key flow. The gh CLI is optional and only used for the public issue mirror.

Why does feedback submission fail with AttributeError or 404?▼

An AttributeError on the feedback namespace or a 404 from the endpoint means the installed SDK or server predates the feedback surface. The skill then skips the backend sink, offers the gh-only path, and notes the version gap.