talk-normal

Solid

Always-on writing rules for concise, normal, bilingual documentation and user-facing text.

AI & Automation 146 stars 3 forks Updated 2 days ago Apache-2.0

Install

View on GitHub

Quality Score: 91/100

Stars 20%
72
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
31
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# talk-normal Use this skill before drafting or editing public docs, UI copy, README text, agent-facing instructions, release notes, and other user-facing prose. The full writing rules live in [prompt.md](prompt.md). The operating summary: - Lead with the answer or concrete point. - Keep useful detail; remove filler, throat-clearing, and corporate polish. - Prefer direct positive claims. - Use bullets only when the content is naturally parallel. - End with the concrete recommendation or next action when one is needed. - Avoid hypothetical follow-up offers. Upstream: https://github.com/hexiecs/talk-normal

Details

Author
olo-dot-io
Repository
olo-dot-io/Uni-CLI
Created
2 months ago
Last Updated
2 days ago
Language
TypeScript
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

write-for-ai

Writes documentation, commit messages, and PR descriptions optimized for the NEXT AI session to understand the project cold. Templates for README, CLAUDE.md / AGENTS.md, conventional commits, and PR bodies. Prioritizes tables and checklists over prose, absolute file paths over vague references, invariants over narrative.

0 Updated today
Sordid-cantor687
Data & Documents Listed

atomic-prose

Voice and tone rules for *enduring narrative documentation* — README.md, docs/guides/, CHANGELOG narrative entries, and any other long-form human-facing markdown that ships in the repo. Clear, direct, technical narrative. No marketing language, no AI-tell phrases, no em dashes, no throat-clearing. Two voices: Claude's TUI replies use atomic output style (terse, fragments); file contents split by surface — narrative docs use this skill, everything else (specs, design docs, CLAUDE.md, signals files) uses terse technical prose. Invoked by /documentation when editing README or guides. Invoked as callee by `atomic-documentation` when surface is human-facing prose. Auto-fires on "draft the README", "write the docs", "improve this prose", "edit the guide".

35 Updated today
damusix
AI & Automation Listed

write-clear-readme

Author, audit, or polish a project README — clarity, structure (Pattern A per-section collapse / Pattern B grouped / Pattern C per-entry), wording concision, anchor integrity. Reads the repo first, proposes diffs, applies on approval.

2 Updated today
coroboros