CF ml-paper-writing
Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. For systems venues (OSDI, NSDI, ASPLOS, SOSP), use systems-paper-writing instead.
Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM.
As a process F 28/100 · No process to follow — References files that are not bundled: ../systems-paper-writing/
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:55High-entropy token-like string (may be an id, hash or a credential) (placeholder value)\cite{PLAC…his} % TODO: Verify this citation existsplaceholder -
low Secrets in code
secret-high-entropy-tokenSKILL.md:805High-entropy token-like string (may be an id, hash or a credential) (placeholder value)\cite{PLAC…ify} % TODO: Could not verify - scientist must confirmplaceholder
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 9211 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../systems-paper-writing/ - note
frontmatter-keyunknown frontmatter key "dependencies"
Process rating: all ten parameters 28/100
- 0Tools and files. 1 referenced file(s) missing: ../systems-paper-writing/
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 15 mutating operations with no state check
- 40Execution cost. Instruction body is 9211 tokens: crowds the task out of the window
- 55Failures and branches. 1 branches
- 60Steps. 142 steps, 4 vague phrases
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 17 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -234 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 289: enough signal without eating the budget
- +4Structure: 47 headings
- +3Step-by-step instructions: 142 items
- +4Has examples (28 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.