Skill detail

human-writing

General multilingual guidance for natural, human-like writing.

MatchDirectReviewed for human writing
Sourcesyahiidkamil/software-engineer-ai-agent-atlasExternal source
Reported installs7Popularity signal only

Inspect before use

Automated review checks relevance, not safety or endorsement. Read the source instructions before using this skill.

Saved source preview

SKILL.md

The saved excerpt is a snapshot from review. The external source remains the complete and most current version.

---
name: human-writing
description: Write content in any language indistinguishable from a skilled human writer. Avoids AI-sounding phrases, varies sentence structure, creates natural prose. Detects target language and loads language-specific AI-tells, register, and orthography from `languages/`.
---

Activate human-like writing mode. The goal is to pass the Turing test. A human reader should not be able to tell this was written by AI — in whatever language the content is written.

## Step 0.1: Detect Language and Load the Right Module

Before applying the rest of this skill, identify the target language. The body of this SKILL.md covers the **universal philosophy** (sentence rhythm, vocabulary diversity, anti-filler principles) and the **English** AI-tells specifically. For any other language, also read the matching file in `languages/` *before writing*:

| Language | File | Notes |
|---|---|---|
| English | (covered below) | Default — no extra file needed |
| Bahasa Indonesia | `languages/id.md` | EYD, Indonesian filler phrases, register spectrum |

If the target language has a file in `languages/`, **read it now**. The language file overrides only the language-specific sections (AI-tells, register, orthography, anglicisms); universal principles in this SKILL.md still apply.

If the target language does **not** have a file yet, fall back to the universal principles below and apply them in the target language with care for native conventions — but flag this to Boss so a `languages/{code}.md` can be added later.

This is a single skill, single trigger. Adding new languages is a `languages/{code}.md` file plus a row in the table above — no new skill registration needed.

## Step 0: Understand the Context First

Before writing anything, answer two questions:

**Who am I writing as?** Read the context. Am I writing as a brand? As a professional in a specific field? As a casual poster? The voice, vocabulary, and tone all depend on this. A 24-year-old Indonesian tech guy writes differently from a corporate blog. Match the person, not a generic "good writer" template.

**What form is this writing?** The format dictates everything about structure, length, and tone:
- **Title/Headline**: Punchy, compressed, high-impact. Every word earns its place.
- **Subtitle/Tagline**: Supports the title. Adds context or intrigue without repeating.
- **Single paragraph**: Self-contained thought. Needs a clear entry and exit point.
- **Multi-paragraph prose**: Article, essay, blog post. Needs flow, pacing, transitions that don't feel mechanical.
- **Quote/Pull quote**: Standalone insight. Must hit hard without surrounding context.
- **Caption**: Brief, contextual, often conversational.
- **Social media post**: Platform-specific voice. Twitter is sharp. LinkedIn is professional but human. Instagram is visual-first.
- **Bullet points/Lists**: Only when the content genuinely is a list. Don't default to this.
- **Bio/About text**: Third-person or first-person, depending on platform. Concise but with personality.

Name the form before writing. A paragraph for a landing page hero section reads nothing like a paragraph in a blog post. The same words in a different form feel wrong.

## Core Directive

Write engaging, compelling, natural content that passes AI detection. The test is simple: would a human reader suspect this was written by a machine? If yes, rewrite.

---

## Readability & Complexity

**Flesch Reading Ease Score**: Target 30-40 for educated audiences, 60-70 for general audiences.

**Sentence Dynamics**: Vary sentence length and structure intentionally. Mix short, punchy sentences with longer, descriptive ones. Create rhythm.

**Grammatical Flow**: Structure sentences with close, logical word connections. Strong dependency grammar creates intuitive flow.

---

## Vocabulary & Phrasing

**Lexical Diversity**: Use rich, diverse, occasionally unexpected vocabulary. Avoid clichés and overused terms.

**Adverb Usage**: Be extremely sparse. Use stro
Read the full source on GitHub (opens external page)
Context

Related work