Don Corleone Writing Style

Rewrite or draft text in a formal, measured, and decisive patriarchal style emphasizing respect, loyalty, clear terms, and reciprocal favors for authoritativ...

Security Scan

This is an instruction-only writing-style skill whose requirements and instructions are consistent with its stated purpose and do not request extra access or install anything.

Purpose & Capability

The name/description (produce Don Corleone-style text) matches the SKILL.md content. There are no unrelated env vars, binaries, or installs requested that would be out of scope for a text-style transformation skill.

Instruction Scope

The SKILL.md contains explicit, bounded runtime instructions (style traits, workflow, guardrails) for rewriting/drafting text. It does not instruct the agent to read local files, access environment variables, call external endpoints, or transmit data outside the conversational context. It includes clear anti-abuse and no-violence guardrails.

Install Mechanism

No install spec or code files are present; this is instruction-only so nothing will be written to disk or downloaded during install.

Credentials

The skill declares no required environment variables, credentials, or config paths — proportionate for a text-style transformation skill.

Persistence & Privilege

Flags are default (always: false, agent invocation enabled). The skill does not request permanent system presence or modify other skills/configuration.

Assessment

This skill is coherent and low-risk from a security perspective. Before installing, consider: (1) review sample outputs to ensure the tone is appropriate for your context and does not unintentionally imply threats or endorse wrongdoing (the SKILL.md forbids explicit violence, but you should still verify outputs), (2) be aware of potential IP/branding concerns when emulating a well-known fictional character and avoid copying copyrighted dialogue, and (3) test with representative inputs to confirm the guardrails (no harassment, no violent language) are consistently enforced. If you need the agent to never invoke this skill autonomously, disable agent invocation at install time.

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."
3. Keep it tight:
   • 1 to 3 short paragraphs, or about 6 to 12 lines total.
   • Use short sentences. Cut filler.
4. 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.
5. 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.").
6. 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.