vc:autoresearch

Orchestrate iterative optimization loops over measurable software metrics with Git-backed rollback.

Updated May 10, 2026
One-click install
npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill vc-autoresearch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc:autoresearch
Source: https://github.com/cryborg1211/quant_trading_telegram_bot/tree/main/.agents/skills/vc-autoresearch
Command: npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill vc-autoresearch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Autonomous iterative optimization loop for measurable metrics in software projects. Use when repeated experiments can be judged by a mechanical score.

Core Features & Use Cases

  • Autonomous iteration over measurable metrics (e.g., coverage, bundle size, ESLint errors, Lighthouse scores) with deterministic evaluation and Git-backed history.
  • Automatic rollback on regression and traceable experiment lineage to support reproducible research.
  • Clear guidance on when to apply autoresearch and how to interpret results across iterations.

Quick Start

Initiate the autoresearch loop with a clear Goal, Scope, and Verify to observe measurable improvements.

Frequently Asked Questions about vc:autoresearch

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

FAQPage Schema
How do I automate metric optimization for test coverage and bundle size?

Automate metric optimization by configuring an autonomous iterative loop that runs repeated experiments, evaluates a mechanical score, and logs results. The loop automatically rolls back Git commits if a regression is detected, ensuring measurable metrics like test coverage or bundle size improve traceably.

What is an autonomous optimization loop and how does it work with Git?

An autonomous optimization loop iteratively applies metric experiments and uses Git to back experiment history. It creates commits for each trial, evaluates the metric score, and automatically rolls back the Git history if a regression occurs, providing traceable lineage for reproducible research.

Do I need a clean Git working tree to run automated metric experiments?

Yes, you need a clean Git working tree to run automated metric experiments. The loop requires a Git repository to back experiment history and execute rollbacks on regression, along with a SKILL.md frontmatter defining the Scope and a Verify command outputting a single numeric metric.

How do I set up a Verify command for autonomous metric optimization?

Set up a Verify command by defining a shell command in your SKILL.md that outputs a single numeric metric. The autonomous loop executes this command to judge each iteration, applying changes only if the metric improves and logging the outcomes to loop-results.tsv.

Can I limit the scope of files modified during automated metric experiments?

Yes, you can limit modifications by defining a Scope of editable files in your SKILL.md frontmatter. The autonomous optimization loop restricts its iterative experiments to this specified scope, preventing unintended changes to your repository while optimizing the target metric.

What happens if an autonomous optimization loop iteration causes a metric regression?

If an iteration causes a metric regression, the loop automatically executes a Git rollback to revert the changes. This ensures the mechanical score never degrades, maintaining traceable experiment lineage and preserving the last known optimal state in your repository.