Token导航 LogoToken导航

Agent Skill · 效率

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

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

don-corleone-writing-style 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 11,520。

总安装 4,560周安装 190GitHub Stars 公开资料未说明下载 1,520核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

don-corleone-writing-style 以正式果断的风格重写文本内容。适合在 OpenClaw 中强调尊重忠诚和权威互惠的表达。可用于起草合同条款或官方声明文稿。安装前应明确语气强度和适用场合。don-corleone-writing-style 属于效率类 Skill,可作为该场景下的辅助能力补充。

适用于法律文书和品牌对外沟通材料撰写。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install don-corleone-writing-style;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

don-corleone-writing-style 怎么安装?

在终端执行 openclaw skills install don-corleone-writing-style。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

don-corleone-writing-style 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

don-corleone-writing-style 需要什么权限?

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

don-corleone-writing-style 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

don-corleone-writing-style 用的人多吗?

公开数据是累计安装 4,560 次,近一周安装 190 次,下载 1,520 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

don-corleone-writing-style 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理效率类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
github

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
don-corleone-writing-style

唐·柯里昂的写作风格 · 本页

4,560—需要联网MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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.

平台分布

OpenClaw

97.68%
按下载量换算1,485

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills