valaxy
🌌 为表达而生的静态博客框架 · A static blog framework for your voice. Vue 3 + Vite, AI-ready (Skills / MCP / llms.txt)
Runssource: GitHubTypeScriptMITcommit 3e13c49d364c
TypeScript, MIT licensed. The project labels itself: agent skills, blog, blog framework, hexo alternative, llms txt, mcp, site and ssg.
valaxy runs. An Argusic agent installed it in 28 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Valaxy monorepo builds successfully, all 718 unit tests pass, all 56 SSG Playwright E2E tests pass across 4 project configurations (docs desktop, docs mobile, yun-footnote desktop, yun-footnote mobile), demo and docs SSG builds produce complete static sites with RSS feeds and search indices.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- release.test.ts fails because npm_execpath env var is set by vitest to npm-cli.js instead of pnpm, causing release script to run wrong command10 minutes
- Node.js v18.19.1 required >=22.12.05 minutes
- pnpm not found on PATH1 minute
- OOM during devtools unbuild with default heap1 minute
- Install time
- 28 minutes
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- vitest --run: 103 test files, 718 passed, 1 pre-existing container-env failure. npx playwright test --config playwright.ssg.config.ts --project=ssg-desktop --project=ssg-mobile --project=yun-footnote-desktop --project=yun-footnote-mobile: 56 passed, 6 skipped, 0 failed over 62 tests. pnpm run build: demo SSG builds and produces demo/yun/dist/posts/hello-valaxy.html (48KB) and valaxy-fuse-list.json (166KB). pnpm run docs:build produces docs/dist/index.html and 404.html.
- Model tokens used
- 766,845
- Exact commit tested
- 3e13c49d364c
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
2. pnpm not found - fixed by npm install -g pnpm 3. OOM during build (devtools unbuild) - fixed by NODE_OPTIONS=--max-old-space-size=4096 4. release.test.ts failure - pre-existing container env issue (npm_execpath set by vitest) - cannot… Verified how: - vitest --run: 718/718 non-release tests pass, 1/719 release test fails due to container env - playwright ssg tests: 56 passed, 6 skipped, 0 failed - demo SSG build produces posts/hello-valaxy.html and valaxy-fuse-list.json - docs SSG build produces docs/dist/index.html and 404.html Now let me compute install_minutes. Install started at ~07:45 UTC and final verification at ~08:13 … tokens used 766,845 Now let me compute install_minutes. Install started at ~07:45 UTC and final verification at ~08:13 …
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 28 minutes to install, slower than the median of the 104 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 105 agent-skills projects Argusic has installed and timed, valaxy was the 97th fastest to reach a running state, and 75 of 105 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agent-skillsblogblog-frameworkhexo-alternativellms-txtmcpsitessgstaticstatic-site-generatorvalaxyvitevueyun
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/valaxy)Questions
- Does valaxy run?
- Yes. valaxy runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test valaxy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3e13c49d364c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test valaxy?
- The run that produced this verdict cost $0.30: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does valaxy take to install?
- 28 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does valaxy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing valaxy?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does valaxy compare with the alternatives?
- Of the 105 agent-skills projects Argusic has installed and timed, valaxy was the 97th fastest to reach a running state, and 75 of 105 reached one at all.
- Where is the evidence for valaxy?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.