メニュー
Remove AI writing patterns from prose. This skill should be used when drafting, editing, or reviewing text to eliminate predictable AI tells. Register-aware — handles casual, professional, academic, technical, and narrative writing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
This skill should be used when the user asks to "build a Boolean search", "create search strings", "write LinkedIn search", "X-Ray search", "Google dork for candidates", "source on GitHub", "Stack Overflow search", "search operators", "Boolean operators for recruiting", "platform-specific search syntax", or needs to construct candidate search queries for any sourcing platform.
This skill should be used when the user asks to write a candidate email, rejection message, schedule interview, status update, offer letter, interview confirmation, how to reject, welcome email, interview prep email, candidate update, between rounds email, onboarding email, feedback to candidate, or needs to communicate with candidates at any stage of the interview process.
This skill should be used when the user asks to evaluate candidates, compare candidates, debrief, hiring decision, candidate comparison, synthesize feedback, candidate ranking, who should we hire, summarize interviews, interview debrief, candidate assessment, score this transcript, metaview transcript, score this screen, score this interview, rate this candidate, transcript evaluation, interview scoring, or needs to aggregate interview feedback, score an interview transcript against a scorecard, facilitate hiring decisions, or compare candidates against each other.
Use proactively for craft personalized candidate outreach messages, design multi-touch sequences, and handle responses across all channels. Use proactively when the user asks to write outreach, draft a message, create an InMail, build an outreach sequence, write a follow-up, candidate email, outreach cadence, cold message, connection request message, breakup message, respond to a candidate, handle objections, personalize outreach, outreach templates, multi-channel sequence, nurture sequence, or needs help with any aspect of candidate engagement messaging across LinkedIn, email, GitHub, Twitter/X, Reddit, Discord, or Slack communities.
This skill should be used when the user asks about quality of hire, hiring survey, candidate experience survey, HM satisfaction, retrospective, what did we learn, silver medalist, onboarding checklist, pre-boarding, post-hire, process improvement, hiring quality, search retro, hiring metrics, candidate NPS, how was the process, lessons learned, or needs to measure, analyze, or improve hiring quality at any stage.
This skill should be used when the user asks to design interview process, interview stages, interview structure, assessment plan, interview flow, how many rounds, interview pipeline, what interviews to run, stage design, or needs to architect a multi-stage interview process for any role family or seniority level.
SOC 職業分類に基づく
| name | stop-slop |
| description | Remove AI writing patterns from prose. This skill should be used when drafting, editing, or reviewing text to eliminate predictable AI tells. Register-aware — handles casual, professional, academic, technical, and narrative writing. |
Eliminate predictable AI writing patterns. Produce clear, specific, human-sounding prose across any register.
Infer the register from context before applying rules. Different registers tolerate different patterns.
| Signal | Register |
|---|---|
| Citations, methodology, "we hypothesize" | academic |
| API docs, READMEs, changelogs, error messages | technical |
| Fiction, essays, memoir, creative nonfiction | narrative |
| Blog posts, social media, emails | casual |
| Reports, proposals, business comms | professional |
If the user specifies a register, use it. See references/registers.md for per-register acceptable vs. flagged patterns.
Apply these rules, adjusted for register:
Cut filler phrases and AI vocabulary. Remove throat-clearing openers, chatbot artifacts, significance inflation, and words that appear 100-1,000x more in LLM output than human text. See references/phrases.md.
Break formulaic structures. Avoid binary contrasts, dramatic fragmentation, format slop, synonym cycling, rule-of-three overuse, and generic conclusions. See references/structures.md.
Use simple constructions. Prefer "is" over "serves as." Prefer "has" over "boasts." Prefer "use" over "leverage." Active voice. Positive form.
Be specific. Replace vague claims with dates, names, numbers, sources. "Significant improvement" becomes "latency dropped from 340ms to 90ms."
Vary rhythm. Mix sentence lengths. Two items in a list beat three. End paragraphs differently from each other.
Trust readers. State facts. Skip softening, justification, hand-holding. If a metaphor needs explaining, rewrite the metaphor.
Have a voice. React to facts, don't just report them. Acknowledge complexity. Let personality through.
See references/positive.md for what good writing does (not just what to avoid).
Rate 1-10 on each dimension, adjusted for register:
| Dimension | Question |
|---|---|
| Directness | Statements or announcements? |
| Rhythm | Varied or metronomic? |
| Trust | Respects reader intelligence? |
| Authenticity | Sounds human, not generated? |
| Density | Anything cuttable? |
| Specificity | Claims backed by evidence? |
Below 42/60: revise.
Register adjustments (see references/registers.md):
academic: Do not penalize precise hedging or longer qualified sentencestechnical: Consistent structure in reference docs is not a rhythm flawnarrative: Indirection and dramatic rhythm variation are valid techniquesBefore delivering prose:
You are stongly encouraged to read the reference files
| File | Purpose |
|---|---|
| phrases.md | Words and phrases to cut or replace |
| structures.md | Structural patterns to avoid |
| positive.md | What good writing does |
| registers.md | Per-register rules and tolerances |
| examples.md | Before/after transformations (all registers) |