anti-defensive-writing-Skill
极致轻量｜阻止论文的防御性写作 | Anti-defensive writing for academic papers, 学术写作原则 Skill + prompt pack (CN/EN)
Not yet verifiedsource: GitHubPythonMITcommit 82d31402caa0
Python, MIT licensed. The project labels itself: academic writing, ai writing, claude skill, paper writing and prompt.
anti-defensive-writing-Skill has not been verified yet.
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
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 most recent recorded attempt, which did not reach a verdict. Every line is a recorded value, not an estimate.
- Install time
- 3 minutes
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- python3 scripts/build_plugin.py exited 0 and produced dist/anti-defensive-writing-1.0.0.zip (10770 bytes, 7 files); ZIP testzip() passed; plugin.json valid JSON with correct name/version; all 14 repo files present with expected sizes; SVG valid XML; both SKILL.md files have valid YAML frontmatter with name and description fields; rebuild is deterministic (SHA256 verified).
- Model tokens used
- 111,758
- Exact commit tested
- 82d31402caa0
- 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. .codex-plugin/plugin.json valid: YES 5. SVG valid XML: YES 6. SKILL.md frontmatter valid: YES 7. All 14 repo files present with correct sizes: YES 8. ZIP contains all 7 expected files: YES 9. Rebuild produces deterministic output: YES === METRICS === ZIP size: 10770 bytes All checks passed cleanly. Here's the summary: tokens used 111,758 All checks passed cleanly. Here's the summary:
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.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.01 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/anti-defensive-writing-skill)Questions
- Does anti-defensive-writing-Skill run?
- anti-defensive-writing-Skill has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test anti-defensive-writing-Skill?
- On a fresh, disposable machine, with every command recorded. One attempt is recorded, and the full method is on the methodology page.
- Where is the evidence for anti-defensive-writing-Skill?
- 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.