improve-existing-project

Enters an autonomous research pipeline from an existing runnable project to improve it through verified experiments.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill improve-existing-project-nitrogen216
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve-existing-project
Source: https://github.com/Nitrogen216/awesome-dsh-mods/tree/main/modes/dsh-autoresearch/skills/improve-existing-project
Command: npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill improve-existing-project-nitrogen216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you already have a working codebase with an evaluation path but want to improve its results, it is unclear how to enter a structured research workflow without losing the original objective. This Skill establishes the correct entry point into the dsh_autoresearch pipeline, preserving whether the goal ends at a promoted method or also requires a paper. ## Core Features & Use Cases - Entry Decision Management: Confirms the workspace contains a runnable method and evaluation path, then persists entry_mode, deliverable (method or paper), and optional target_venue based strictly on the direct human request. - Baseline-First Initialization: Inspects implementation, configs, and prior results, loads baseline-assessment, and initializes canonical research state via transition_guard.py only after a baseline artifact exists. - Pipeline Handoff: Delegates the scientific work to depth-research-loop and routes to paper-writing when the guard's next_action requires it, without widening the original deliverable. - Use Case: You have a machine learning repository with training code and a benchmark script but weak results. Use this Skill to baseline the current method, then autonomously iterate on experiments until a verified improvement is promoted. ## Quick Start Use the improve-existing-project skill to autonomously improve this existing project through confirmed evidence.

Frequently Asked Questions about improve-existing-project

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

FAQPage Schema
How do I autonomously improve an existing research codebase?▼

Load this Skill when your workspace already contains a runnable method and evaluation path. It inspects the implementation, runs or reuses baseline evidence, initializes research state with transition_guard.py, and hands off to the depth-research-loop for iterative experimentation.

When should I use improve-existing-project versus discover-research-idea?▼

Use improve-existing-project when a comparable implementation and evaluation path already exist in the workspace, even if results are weak. Use discover-research-idea when only a broad research direction exists and no comparable implementation can be identified.

Does this Skill always produce a paper at the end?▼

No. The deliverable is set to paper only when the human objective explicitly asks for a paper, manuscript, PDF, or the full research-to-paper lifecycle. Otherwise it is method-only and may complete at the frozen stage without paper writing.

How is the research state initialized before experiments begin?▼

State is initialized by running transition_guard.py with the init command after a baseline artifact exists. It records entry mode, deliverable, objective, primary metric, metric direction, target delta, and the baseline run identifier.

Can the deliverable change from method to paper during research?▼

No. The Skill never changes entry_mode, deliverable, or target_venue based on experiment outcomes. Only a later direct human request can explicitly start paper writing; ordinary research output cannot widen the original deliverable.