← ClaudeAtlas

to-articlelisted

Use when asked to generate, draft, or rewrite a scientific/technical article in Computer Science (conference paper, journal paper, or survey) from a topic/idea plus the repository's code, experiments, and results. Also use when asked to structure, review, or de-slop an existing draft. Triggers: "write the paper", "write an article", "generate the article from the repo", "turn this experiment into a paper", "review/reformat my draft".
samuhs/mad-science · ★ 3 · Code & Development · score 80
Install: claude install-skill samuhs/mad-science
# to-article Produce a complete, submission-ready scientific article in the correct template, written with human, anti-slop prose and grounded in the actual code and results present in the working directory — never invented from memory. ## Core principles 1. **Ground in the repo.** The article's theory, method, and numbers come from files in the target directory (docs, code, experiment outputs). If evidence is missing, say so and stop — do not fabricate metrics, datasets, or claims. 2. **Derive before writing.** Complete the derivation (references/derivation.md) BEFORE generating prose. Without it the model defaults to the slop register. 3. **Anti-slop is a post-pass, not an avoidance list.** Never load "words to avoid" into context while generating (that primes them). Write to a positive register; run the anti-slop audit on the finished draft (references/anti-slop.md). 4. **One section at a time, spec-first.** For each section, first state what it must contain (references/section-spec.md), then write it against the derived register. No filler paragraphs. ## When to use / when not - Use: creating a new article from repo evidence, or reviewing/reformatting an existing draft. - Not for: narrative blog posts, marketing copy, or non-scientific writing. ## Workflow ### 1. Detect target template - If the user names a venue (conference/journal), use it. - Else infer from context: target repo language pt-BR or Brazilian venue → SBC; arXiv/acmart or Eng