UZI-Skill

冰冷的钱就这样流进我温暖的口袋-游资(UZI)Skills, 让我们欢迎,股海贼王!66位投资大佬帮你看盘 · 22维数据 × 180条量化规则 × 17种机构分析方法 · A股/港股/美股

Runssource: GitHubPythonMITcommit 650788c54a9b

Python, MIT licensed.

UZI-Skill runs. An Argusic agent installed it in 2.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Stock analysis pipeline runs end-to-end: install completes, 808/808 tests pass, CLI generates full HTML report with share-card and war-report PNGs for AAPL

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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
2
last tested
stars
7,634
forks
1,065
open issues
3
watchers
29
size
11 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . 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.

Time lost to each failure while testing UZI-Skill, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Python externally-managed environment blocked system pip install0.2 minutes
  • pytest not pre-installed0.1 minutes
  • 8 critical self-review items in lite mode (dimensions not fetched) and missing agent_analysis.json
Install time
3 minutes
Cold machine to finish
9 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
pytest tests/ exited 0, 808 passed; stage1('AAPL') collected data in 14.3s; stage2('AAPL') generated complete HTML report (695 KB standalone) with valid PNG images
Model tokens used
45,362
Exact commit tested
650788c54a9b
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.

tokens used
45,362
Alright, now I have all the data I need. Let me compile the final report.
Here's the full summary of what was done and verified:
**Install** — `pip install -r requirements.txt` succeeded in a venv with all 47 packages (akshare, …
**Tests** — 808 passed, 0 failed, 31 warnings (all deprecation warnings from pandas/exchange-calend…
**App launch** — Ran a full pipeline on `AAPL` (Apple Inc.), which:
1. Stage 1 collected data and scored all dimensions (14.3s)
2. Stage 2 generated a complete HTML report with all assets (4.5s)
3. Outputs: HTML report (695 KB standalone), PNG share-card (1.1 MB), PNG war-report (280 KB)
All files verified: HTML has proper structure (332 heading/score elements), PNGs are valid RGB imag…
The 8 critical self-review failures are expected — they're dimensions that weren't fetched in lite …

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 3 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.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 2.5 minutes to install, slower than the median of the 46 comparable projects Argusic has measured.

Of the 47 Python projects Argusic has installed and timed, UZI-Skill was the 27th fastest to reach a running state, and 32 of 47 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.
  • A quick evaluation: it was running 2.5 minutes after the clone.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.06
Argusic Runner1/3Runs with mocks92.000.05

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/UZI-Skill.svg)](https://argusic.com/subject/uzi-skill)

Questions

Does UZI-Skill run?
Yes. UZI-Skill runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test UZI-Skill?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 650788c54a9b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test UZI-Skill?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does UZI-Skill take to install?
2.5 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 UZI-Skill need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing UZI-Skill?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does UZI-Skill compare with the alternatives?
Of the 47 Python projects Argusic has installed and timed, UZI-Skill was the 27th fastest to reach a running state, and 32 of 47 reached one at all.
Where is the evidence for UZI-Skill?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion