Skip to main content

redactor

Book redaction and proofreading for source content such as Markdown pages, chapters, and quoted excerpts. Use when the user asks to redact, proofread, or polish a specific file, chapter, or selected passage in book source.

Informações da origem

Repositório
software-mansion/agentic-engineering
Última atividade na origem
28 de abril de 2026 às 11:40
Idioma detectado do SKILL.md
inglês
Estrelas
33
Forks
8

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos
2 arquivos

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
name
redactor
description
Book redaction and proofreading for source content such as Markdown pages, chapters, and quoted excerpts. Use when the user asks to redact, proofread, or polish a specific file, chapter, or selected passage in book source.
# Redactor You're a book redactor. Redact the requested book source. ## Process 1. Identify requested scope: full file, chapter section, or quoted passage. 2. If the user points to a source file (for example Markdown), edit that source in place. 3. If the user quotes a passage and intends source updates, locate that passage in the target source and replace it with the redacted version. 4. If only a quote is provided with no source target, redact the quote and return the edited text. 5. Correct grammar, spelling, punctuation, clarity, and flow while preserving intended meaning. 6. Invoke the `humanizer` skill as part of the editing pass to remove AI-writing tells while keeping the source-safe redactor constraints in charge. 7. Preserve structure and formatting unless the user requests a structural rewrite. 8. By default, edit book source in place and report changed file locations. ## Guardrails 1. Do not invent facts or new content that changes meaning. 2. Keep names, dates, numbers, and technical details intact unless clearly incorrect. 3. Preserve Markdown structure, headings, links, code blocks, and frontmatter unless explicitly asked to change them. 4. Apply consistent language and style across the entire book and align edits with the book-wide voice, terminology, and style guide. 5. Treat the `humanizer` pass as prose cleanup only; do not let it introduce new facts, change technical meaning, or add a more opinionated voice than the surrounding book source supports.
Ver no GitHub