content-model
SolidWhen and how text goes through the GPT/Gemini door (.claude/scripts/text_model.py) instead of being written by the engineering model — README and docs prose, i18n and help strings, changelog wording, site copy, and any audit or verdict about such text; also the second-family challenge of a research note. Use "rewrite this sentence", "review the wording", "simplify the docs", "second opinion".
Install
Quality Score: 85/100
Skill Content
Details
- Author
- assaio
- Repository
- assaio/assaio
- Created
- 2 months ago
- Last Updated
- today
- Language
- Go
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
external-model-consult
Consult a second, non-Claude model through a bundled wrapper for four things: (1) natural, native-sounding KOREAN phrasing via Google Gemini — copy, UI microcopy, marketing text; (2) a MULTI-PERSONA / second-opinion review of a design, plan or spec; (3) CONCISE, well-STRUCTURED writing via OpenAI Codex — tightening prose, restructuring a doc; and (4) IMAGE GENERATION as real image files on disk (not labeled diagrams — use Mermaid). Fire it when Korean reads translated, or when you would otherwise hand-write polished Korean yourself. Triggers on "어색해", "자연스럽게 다듬어줘", "gemini 한테 물어봐", "nano banana", "제3자 관점", "codex한테 물어봐", "간결하게 정리해줘", "이미지 만들어줘", and in English "ask gemini", "ask codex", "generate an image". Returns candidates to choose from; never auto-applies. Do NOT use for deterministic transforms (rename, reformat, sort), labeled diagrams, internal logs or identifiers, anything needing repo secrets, a native subagent panel (`multi-persona-review`), or when the user explicitly wants YOUR answer.
second-opinion
Cross-model audit via Gemini (review / challenge / consult modes). Defends against same-model self-bias. Used before high-impact decisions (publish gate, /init final review).
humanize
Remove AI-writing tells from any prose, normalize punctuation to plain ASCII (em dash -> hyphen, curly quotes -> straight, ellipsis char -> "..."), and raise headings to Title Case. Use when the user says "humanize this", "make it sound human", "de-AI this", "this reads like ChatGPT", "remove AI patterns", or when editing/reviewing any prose (doc, README, PR description, commit message, email, post) that shows AI tells. The general-purpose de-AI pass for any prose, in any format, unless a more specific writing workflow already owns the piece. Skips agent-instruction files (CLAUDE.md, AGENTS.md, context.md, llms.txt, cursor rules) unless the user aims it at one - their terse fragment style is the working format, not a tell.