Token导航 LogoToken导航TokenDH.com
效率需要联网clawhub未标认证来源可访问clear审计通过

don-corleone-writing-style唐·柯里昂的写作风格

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

4,560

周安装

190

GitHub Stars

公开资料未说明

下载量

1,520
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:don-corleone-writing-style(唐·柯里昂的写作风格)
来源仓库:https://github.com/anugotta/don-corleone-writing-style
安装命令:
openclaw skills install don-corleone-writing-style
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install don-corleone-writing-style

简介

don-corleone-writing-style 以正式果断的风格重写文本内容。

  • 适合在 OpenClaw 中强调尊重忠诚和权威互惠的表达。
  • 可用于起草合同条款或官方声明文稿。
  • 安装前应明确语气强度和适用场合。don-corleone-writing-style 属于效率类 Skill,可作为该场景下的辅助能力补充。
  • 适用于法律文书和品牌对外沟通材料撰写。

SKILL.md

name
don-corleone-writing-style
description
Rewrite or draft text in a Don Corleone (Godfather)-inspired patriarchal dealmaker writing style: formal, measured, loyal-favors oriented, and decisive. Use when the user asks to sound like a "wise boss," "patriarch," "don," "set terms," "grant or deny a favor," or "negotiate with authority" in a way that stays professional.
metadata
{"openclaw":{"homepage":"https://en.wikipedia.org/wiki/The_Godfather"}}

Don Corleone (Godfather)-inspired writing style

Goal

Turn the user's text into a voice that sounds like a respected patriarch:

  • Calm authority (measured cadence, no frantic tone)
  • Respect and obligation (loyalty/favors as a framing device)
  • Decisive terms (clear requirements, deadlines, or next step)
  • Controlled pressure (firm boundaries, implied consequences without threats)

Online-informed style traits

Apply these traits consistently:

  • Soft-spoken command: short, deliberate lines that still control the room.
  • Formal respect markers: use "respect", "family", "loyalty", "trust", "honor" naturally and sparingly.
  • Favors as social contract: frame help as reciprocal obligation, not charity.
  • Measured restraint: avoid rage language; prefer poise, patience, and inevitability.
  • Traditional hierarchy cues: prioritize duty, order, and clear roles.

Non-negotiables (guardrails)

  • Do not copy dialogue or quotes from *The Godfather*.
  • No explicit violence. If pressure is requested, convert it into firm consequences (process, timelines, escalation).
  • No harassment, hate, or criminal instructions. Keep it professional.

Anti-AI-tells guardrails (from Wikipedia)

When rewriting/drafting, avoid patterns common in AI text (see Wikipedia:Signs of AI writing) such as:

  • Promotional puffery (prefer specific terms and requirements).
  • Vague attribution (avoid "experts say", "it is believed" unless the user provided sources).
  • Outline-like wrap-ups (avoid "in conclusion" / "overall" restating the thesis).
  • Template-y negation patterns like "Not X, but Y" or repetitive "not ... but ..." structures.
  • Excessive em-dashes and curly quote characters; prefer plain punctuation.
  • AI vocabulary stacking and "Additionally/Furthermore/Moreover/Notably" chains.

Workflow (use every time)

  1. Clarify the objective: grant a favor, refuse a request, negotiate terms, or set expectations.
  2. Pick the stance:

- Grant: "I will do this. Here is the condition." - Refuse: "No. Here is the real constraint." - Negotiate: "Here are the terms. Choose the path." - Correct: "Explaining is not fixing. Do this instead."

  1. Keep it tight:

- 1 to 3 short paragraphs, or about 6 to 12 lines total. - Use short sentences. Cut filler.

  1. Add obligation framing:

- Name what is owed (time, effort, cooperation, honesty). - Name what you require to proceed (deadline, approval path, deliverable). - Where suitable, frame it as a favor with reciprocal duty.

  1. Add one authority device:

- A clear rhetorical question, or - A clean pivot line ("Then you handle the rest."), or - A short rule-of-the-house statement ("We do it in writing.").

  1. Land the ending:

- A single next step with a deadline or decision request.

Language rules

Do

  • Use formal, direct language: "I need", "You will", "Send", "Decide".
  • Use boundaries: "That does not work", "I am not available for this".
  • Use terms: "by Friday", "in writing", "single owner", "one approval path".
  • Use respectful tone even when denying.

Avoid

  • Hedging: "maybe", "kind of", "I think", "just", "hopefully".
  • Rambling context dumps. Frame the request instead.
  • Over-the-top swagger. One strong line is enough.

Output formats

1) Rewrite (same meaning, new voice)

Return:

  1. Don Corleone-style rewrite (just the rewritten text)
  2. One-line rationale (max 1 sentence) describing the main change (tone, structure, terms)

2) Draft from scratch (user gives scenario)

Return:

  1. Draft
  2. Optional variants (only if requested): "more formal" / "more firm"

Templates

Favor grant (with conditions)

  • "I will take care of it."
  • "But I need X by Y."
  • "If that happens, we proceed."

Refusal (respectful, firm)

  • "No."
  • "The constraint is X."
  • "If you want this, propose A by B."

Negotiation / terms (deal language)

  • "Here is what I can do."
  • Terms as 2 to 4 short bullets.
  • "Decide by <time>."

Correction / accountability (no drama)

  • "Explaining is not fixing."
  • "Send the plan. Then execute by <time>."

Examples

See examples.md for ready-to-copy rewrites and original drafts.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

97.68%
按下载量换算1,485

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills