Individual skill

unslop-academic-writing

Remove AI slop from research writing so papers, theses, grant proposals, reviews and rebuttals read as written by a careful human expert. Covers stock vocabulary (delve, tapestry, pivotal, underscores), empty emphasis, hedge stacks, formulaic signposting, "not only X but also Y" constructions, em-dash pileups, monotone rhythm, and claims vaguer than the data. Use when drafting or revising academic text with an AI assistant, when a draft "sounds like ChatGPT", before submission, or to match an author's own voice. Includes a zero-dependency slop linter for Markdown, LaTeX, text and Word files.

plugins/KalarisLabs/research-agent-skills/skills/unslop-academic-writing/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Unslop Academic Writing

Slop is prose that is fluent but says less than it seems to. Readers, reviewers and
editors now recognize it on sight, and it costs credibility even when the science
is sound. The fix is **specificity**: every sentence should carry information a
generic paper on the topic would not.

This skill is about **clarity and authorship, not about disguising AI use**. Follow
the venue's policy on AI assistance (most require disclosure, see `reproducibility-statement`).
The author remains responsible for every claim.

## Workflow

1. **Measure.** Run the linter on the draft (or a section):