ppt-image-first

PPT image-first skill for Codex/Claude Code/Opencode CLI

Could not verifysource: GitHubPythonApache-2.0commit 87a300a559a2

Python, Apache-2.0 licensed. The project labels itself: office, powerpoint, ppt, slide and slides.

Argusic could not get ppt-image-first running. An Argusic agent installed it in 15 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

The ppt-image-first skill is installed in ~/.codex/skills/, all 4 Python scripts compile and pass basic execution tests, the 3 HTML shell files can be regenerated from their builders, the review markup renderer processes JSON payloads onto slide images, the demo PPTX is a valid 81-entry OPC document, and all 4 sample images are valid PNGs. No tests or app runtime exist to exercise end-to-end.

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

At a glance

verdict
Could not verify
Argusic Score
80 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
2
last tested
stars
1,239
forks
94
open issues
0
watchers
4
size
31 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.

Install time
15 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
skill validated with skill-creator quick_validate; build_preview_html.py, build_candidate_picker_html.py, build_review_html.py all ran cleanly producing valid HTML files; render_review_markup.py successfully rendered markup onto a test slide image; demo PPTX validated as a valid ZIP-based Office document; 4 sample PNG images verified as valid image files (Pillow verify); all Python files compile without syntax errors; codex --help works and tooling is operational
Model tokens used
68,961
Exact commit tested
87a300a559a2
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
Whether it works at all
this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

                    \"4 sample PNG images verified as valid image files (Pillow verify); \"
                    \"all Python files compile without syntax errors; \"
                    \"codex --help works and tooling is operational\",
    \"final_state\": \"The ppt-image-first skill is installed in ~/.codex/skills/, all 4 Python scr…
}
print(json.dumps(result))
PYEOF
/tmp/venv/bin/python /tmp/final_report.py" in /work/repo
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 15, "errors": [], "test_de…
tokens used
68,961

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

  • Installed in 15 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • An agent with no time limit did not get it running.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Unverified80.000.04
Argusic Runner1/3Unverified80.000.05

Topics (from GitHub)

officepowerpointpptslideslides

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/ppt-image-first.svg)](https://argusic.com/subject/ppt-image-first)

Questions

Does ppt-image-first run?
Argusic could not verify that ppt-image-first runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test ppt-image-first?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 87a300a559a2. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test ppt-image-first?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ppt-image-first take to install?
15 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 ppt-image-first need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ppt-image-first?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for ppt-image-first?
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