← all publishers

forger-labs-hq

@forger-labs-hq source repo

13 published skills

  1. Researchforge Run · forger-labs-hq
    Execute an approved experiment plan through the screening → full benchmark funnel, or resume an interrupted run. Use when the user says run the experiments, or a run was interrupted.
    0
    installs
  2. Researchforge Plan · forger-labs-hq
    Design experiment variants for a hypothesis — write patches, import the plan for validation, and get it approved. Use after a baseline exists, when the user wants to plan or implement experiments.
    0
    installs
  3. Researchforge Ship · forger-labs-hq
    Ship a validated experiment — clean local branch reconstructed from the baseline, engineering report, and optional draft PR. Use when the user wants the winning change as a branch, a report, or a PR.
    0
    installs
  4. Researchforge Paper · forger-labs-hq
    Build the research package — BibTeX citations, related work, evidence matrix, paper outline, reproducibility bundle, and experiment data. Use when the user wants publication materials or a research write-up bundle.
    0
    installs
  5. Researchforge Start · forger-labs-hq
    Start or resume a ResearchForge project — explore a research idea or improve a repository with benchmarked experiments. Use when the user wants to begin research, set up ResearchForge, or asks "where was I?" in an existing project.
    0
    installs
  6. Researchforge Doctor · forger-labs-hq
    Check that ResearchForge's dependencies (git, Python, optionally Docker) are available and explain any failures. Use when setup fails, before starting a project, or when the user asks whether their machine is ready.
    0
    installs
  7. Researchforge Papers · forger-labs-hq
    Search arXiv for papers relevant to the project objective and review what was stored. Use when the user wants literature, related work, or asks what papers ResearchForge found.
    0
    installs
  8. Researchforge Autorun · forger-labs-hq
    Drive the autonomous research loop round after round — ask the engine which node to expand, plan there, run, read the result, repeat. Use when the user wants to keep improving a repository over many rounds, or wants autorun without an AI API key.
    0
    installs
  9. Researchforge Results · forger-labs-hq
    Summarize a run's results — ranking, Pareto trade-offs, constraint violations, and rejected experiments — grounded strictly in recorded measurements. Use when the user asks how the experiments went or which variant won.
    0
    installs
  10. Researchforge Baseline · forger-labs-hq
    Set up the experiment contract and run the frozen baseline benchmark. Use when an improve-repository project needs its evaluation defined, the contract approved, or the baseline measured.
    0
    installs
  11. Researchforge Validate · forger-labs-hq
    Run repeated validation benchmarks on a run's finalists so a result can honestly be called validated. Use after a run has a promising winner, or when the user asks to confirm/validate a result.
    0
    installs
  12. Researchforge Landscape · forger-labs-hq
    Synthesize stored papers into a research landscape — grouped directions with evidence claims — and import it for validation. Use after papers are stored, when the user wants directions, themes, or a map of the literature.
    0
    installs
  13. Researchforge Hypotheses · forger-labs-hq
    Generate testable, evidence-linked hypotheses from the research landscape and import them for validation. Use after the landscape exists, when the user wants hypotheses, experiment ideas, or "what should we try?".
    0
    installs