agentleFS
nehasu19nehasu19/job-radar/no-ai-slop/SKILL.md

no-ai-slop

Skill6 starsChanged 9 days agoMITView on GitHub

Write like a sharp human professional, not a chatbot. Use whenever drafting or editing text someone will send or publish as their own — resumes, CVs, cover letters, LinkedIn posts, emails, bios, application answers, reports. Strips generic filler, buzzwords, inflated claims and tell-tale AI phrasing, and keeps only content that is specific, true and relevant to the reader.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use caveman-compress, ponytail and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • huangzidaSkill

    caveman-compress

    Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman:compress <filepath> or "compress memory file"

    Also in 3 projects that use this

  • GoogleSkill

    ponytail

    Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

    Also in 3 projects that use this

  • MicrosoftSkill

    impeccable

    Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android screens. Handles UX review, hierarchy, layout, typography, color, motion, UX copy, accessibility, responsive behavior, edge cases, and capturing or documenting design systems (DESIGN.md, tokens). Also for making bland UI bolder, loud UI quieter, or ambitious visual effects. Not for backend-only or non-UI tasks.

    Also in 3 projects that use this

  • GoogleSkill

    setup-matt-pocock-skills

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 4 projects that use this

  • VercelSkill

    find-skills

    Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

    Also in 4 projects that use this

  • +4 more from google

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. 0 are common, 19 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 19

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before writing, list what the reader needs (for a job application: the posting's key requirements).

    line 12
  2. Distinctive:

    Every claim needs a concrete anchor: a product, a client, a tool, a scope, a result.

    line 21
  3. Distinctive:

    Use numbers only if they are in the source material.

    line 22
  4. Distinctive:

    Do not use these (or close variants) unless quoting the job posting:

    line 27
  5. Distinctive:

    No rule-of-three lists for rhythm ("innovative, scalable and robust").

    line 36
  6. Distinctive:

    No em-dash chains or dramatic dashes.

    line 37
  7. Distinctive:

    No rhetorical questions, no exclamation marks in professional text.

    line 38
  8. Distinctive:

    No restating the same point in the closing paragraph.

    line 39
  9. Distinctive:

    No self-praise adjectives (excellent, outstanding, strong) about the writer.

    line 40
  10. Distinctive:

    No emojis, no bold-for-emphasis inside sentences, no headings in a cover letter.

    line 41
  11. Distinctive:

    No hedging stacks ("I believe I could potentially help").

    line 42
  12. Distinctive:

    Don't mirror every keyword from the posting.

    line 43
  13. Distinctive:

    Never add experience, tools, titles, dates, degrees, certifications or achievements that aren't in the source.

    line 47
  14. Distinctive:

    Write the way the person would say it in an interview: direct, calm, a little understated.

    line 53
  15. Distinctive:

    Search the draft for every banned word and pattern above and rewrite those lines.

    line 58
  16. Distinctive:

    Delete any sentence that would fit any other candidate's letter unchanged.

    line 59
  17. Distinctive:

    Delete any bullet or skill that no requirement points to.

    line 60
  18. Distinctive:

    Read the opening line: if it's generic, replace it with the most specific reason this role fits.

    line 61
  19. Distinctive:

    Check every fact against the source material.

    line 62

“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

No AI slop

Goal: the text should read as if a competent, busy professional wrote it in their own voice. A recruiter should not be able to tell an AI touched it.

1. Relevance first

Before writing, list what the reader needs (for a job application: the posting's key requirements). Then test every sentence, bullet and skill:

  • Does it answer a requirement, or prove seniority or impact the reader cares about? Keep it.
  • Otherwise cut it. Don't soften it, cut it.

Shorter and specific beats longer and complete. Never pad to reach a length.

2. Specific beats generic

  • Every claim needs a concrete anchor: a product, a client, a tool, a scope, a result. "Built Python/Appium automation for a car maker's Android apps" not "Leveraged cutting-edge automation to drive quality".
  • Use numbers only if they are in the source material. Never invent metrics, percentages or results.
  • One idea per sentence. Plain subject–verb–object.

3. Banned words and phrases

Do not use these (or close variants) unless quoting the job posting:

  • leverage, utilize, spearhead, synergy, robust, seamless, cutting-edge, state-of-the-art, game-changer, best-in-class, world-class, holistic, dynamic, innovative (as filler), passionate, thrive, journey, landscape, realm, tapestry, delve, embark, elevate, empower, unlock, harness, foster, navigate (figuratively), pivotal, crucial, paramount, meticulous, testament, showcase, ever-evolving, fast-paced
  • "I am excited to apply", "I am thrilled", "I am writing to express my interest", "I believe I would be a great fit", "I am confident that", "proven track record", "results-driven", "detail-oriented team player", "hit the ground running", "wear many hats", "add value", "go above and beyond"
  • "In today's …", "In the world of …", "When it comes to …", "It's worth noting", "Moreover", "Furthermore", "Additionally" (as sentence openers), "Not only … but also …", "It's not just X, it's Y"
  • "I hope this finds you well", "Thank you for your time and consideration" stacked with other pleasantries — one short polite close is enough.

4. Banned patterns

  • No rule-of-three lists for rhythm ("innovative, scalable and robust").
  • No em-dash chains or dramatic dashes. Use a full stop or comma.
  • No rhetorical questions, no exclamation marks in professional text.
  • No restating the same point in the closing paragraph.
  • No self-praise adjectives (excellent, outstanding, strong) about the writer. Show it with evidence instead.
  • No emojis, no bold-for-emphasis inside sentences, no headings in a cover letter.
  • No hedging stacks ("I believe I could potentially help").
  • Don't mirror every keyword from the posting. Mirror a term only where the experience honestly matches it.

5. Truth

  • Never add experience, tools, titles, dates, degrees, certifications or achievements that aren't in the source.
  • For a gap, name the closest real experience plainly ("I haven't used Playwright in production; my end-to-end suites were Selenium and Appium"). Don't spin it.

6. Voice

  • First person, active voice, past tense for past roles, present for current.
  • Write the way the person would say it in an interview: direct, calm, a little understated.
  • Vary sentence length naturally; avoid every paragraph having the same shape.

7. Final pass (always do this before delivering)

  1. Search the draft for every banned word and pattern above and rewrite those lines.
  2. Delete any sentence that would fit any other candidate's letter unchanged.
  3. Delete any bullet or skill that no requirement points to.
  4. Read the opening line: if it's generic, replace it with the most specific reason this role fits.
  5. Check every fact against the source material.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.