deslopify
Removes AI-generated slop in two modes: (1) rewrites prose to sound natural and human — strips filler phrases, hollow transitions, passive constructions; (2) removes AI-generated comments from code diffs — clears over-explained, restatement-style comments from changed lines without touching code. Make sure to use this skill whenever the user says "deslopify", "remove AI slop", "make this sound human", "this sounds like ChatGPT", "clean up this text", "remove AI comments", "clean up comments in this diff", "rewrite without the fluff", or pastes text or a diff that reads as AI-generated.
What this skill does
# Deslopify
Strip the patterns that mark text as AI-generated. Preserve all factual
content and the author's intended tone — change the delivery, not the message.
## The Slop Patterns
Scan for these before rewriting. The more you find, the more aggressive the
edit.
**Opening filler** (cut 80% of the time — start with the actual point):
- "In today's fast-paced world..."
- "It's important to note that..."
- "As we navigate the complexities of..."
**Hollow transitions**:
- "Furthermore,", "Moreover,", "Additionally," — usually just "Also," or delete
- "In conclusion," — end without announcing you're ending
- "It's worth noting that..." — just say the thing
**Emphasis inflation**:
- "Importantly,", "Crucially,", "Significantly," — earn emphasis with content
- "It goes without saying..." — then don't say it
**AI vocabulary** (replace with the plain word):
- "leverage" → "use"
- "utilize" → "use"
- "delve into" → "look at" or "explore"
- "in terms of" → restructure the sentence
- "moving forward" → cut
- "at the end of the day" → cut
**Excessive hedging**:
- "It seems that", "One might argue", "It could be said" — commit to the claim
or cut it
**Nominalization** (convert to verb):
- "make a decision" → "decide"
- "provide assistance" → "help"
- "conduct an analysis" → "analyze"
- "have a discussion" → "discuss"
**Bullet lists where prose would be clearer**: not every list needs to be a
list. Three related sentences often read better as a paragraph.
**En-dash used as em-dash**: `–` should be `—` (or just a comma)
## What Good Looks Like
- Short sentences land hard. Longer ones build context. Vary them.
- Active voice: "We shipped X" not "X was shipped by the team"
- Specific beats general: "increased conversion by 18%" not "improved results"
- The first sentence is the most important — if it's filler, cut it
## Process
1. Read the full text
2. Identify which slop patterns appear
3. Rewrite: cut the filler, verb-ify the nominalizations, activate the passive
4. Present the revised version
5. Add a 2–3 line note on the key changes made (not a list of every single fix)
## Code Comment Mode
When the input is a diff (or the user asks to remove AI comments from code):
**What to remove:**
- Comments restating what code clearly does (`// increment counter` above `counter++`)
- Overly verbose explanations of obvious code
- Generic placeholders (`// TODO: implement`, `// Handle error`)
- Comments with AI phrasing ("This function...", "The following code...")
- Inline docs inconsistent with the file's existing comment style
**What to keep:**
- Doc comments for public APIs (JSDoc, docstrings)
- Comments explaining WHY (business logic, workarounds, edge cases)
- Comments matching the file's existing style and density
- License headers and attribution
**Hard constraint: DO NOT modify any code.** Only remove comments. No refactoring, no style changes, no removing try/catch or null checks. If you spot code slop, note it in the summary but leave it.
Output: report 1–3 sentences on what was removed and any code issues noticed but left unchanged.
## Hard Rules (Prose Mode)
- Never change factual content — only how it's expressed
- Never add new claims or examples not in the original
- Preserve the author's stance and intended audience
- If the text is mostly fine, say so — don't invent problems to fix
Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.