Skip to content
Back to skills

Autoresearch Mlx

ASecurity

Create and inspect science projects in the autoresearch-mlx Harness workspace, including its local starter and optional upstream integration.

  • 1,124 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 19, 2026
ai-agentsapi

Works with

  • api

Security analysis

A100/100

Scanned September 19, 2026

npx -y skills add autonomous-ai/openharness --skill autoresearch-mlx --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Autoresearch Mlx?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Autoresearch Mlx
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/autonomous-ai-autoresearch-mlx/badge)](https://www.skillsdirectory.com/skills/autonomous-ai-autoresearch-mlx)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: autoresearch-mlx
description: Create and inspect science projects in the autoresearch-mlx Harness workspace, including its local starter and optional upstream integration.
---

# Research notebook

Read `studio.json` to understand the current controls; `"$STUDIO_TOOLCHAIN/../studio.config.json"`
describes their ranges. Run `"$STUDIO_TOOLCHAIN/run.sh" train` to make a new result.
Successful artifacts and their measurements are in `out/runs/<id>/`; `out/latest.json` names the
current result. A failed run preserves the last success and records the error in the verdict.

The local starter trains a small character transition model with NumPy on a bundled, original text corpus. It uses real training and held-out cross-entropy, not generated metrics. It is a CPU baseline, distinct from upstream MLX transformer training, which requires Apple Silicon and its prepared dataset.

Use `"$STUDIO_TOOLCHAIN/../README.md"` for the integration contract and commands. Read the relevant
files under `$STUDIO_UPSTREAM` before using an upstream API. Keep controls within their documented
ranges, preserve the data needed to reproduce a comparison, and distinguish preview results from
native service or hardware output. The viewer supports history and artifact downloads; tell the
user which run contains the result, and what was actually measured.

## Run a controlled experiment

Read `train.py`, `train.txt`, and `holdout.txt`. Save a baseline. Change one training choice
or the editable training code, then run `train`. Inspect `evaluation.json`, the saved model,
and `learning.csv`. Keep the holdout unchanged; the runner independently reopens the model
with pickle disabled and computes its score. Data hashes define which earlier runs compare.
Repeat promising changes with several seeds before presenting a conclusion.

For Apple Silicon, read `$STUDIO_UPSTREAM/program.md` and `README.md`. Prepare a separate
workspace `mlx/` checkout and its environment/data before running `mlx`. The CPU starter's
bits-per-character score and the upstream bits-per-byte metric are different experiments.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…