Hum Rhetoric

What it does

When your agent uses it

• The user needs to make a speech more persuasive
• Analyze why a piece of communication is effective
• Write a compelling proposal
• Evaluate rhetorical strategies — even if they say make this more convincing

Example prompts

• “make this more convincing”
• “why is this speech so powerful”
• “how do I persuade the board”
• “/hum-rhetoric”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

1. 1Identify the rhetorical situation: Speaker, audience, purpose, context
2. 2Map the appeals: Where does the text use Ethos, Pathos, Logos?
3. 3Identify devices: Which rhetorical techniques amplify the message?
4. 4Assess effectiveness: Does the appeal balance match the audience? Are the appeals authentic?
5. 5Note weaknesses: Where is the rhetoric thin, manipulative, or mismatched?

What it can do on your machine

Read from SKILL.md and the folder at commit 4e7f4f8. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Hum Rhetoric loads about 1.4k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 107 tokens; SKILL.md has 496 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~107

When it runs · the whole SKILL.md, loaded when a task matches

~1.4k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~4.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from asgard-ai-platform/skills at commit 4e7f4f8, republished under its MIT licence (© asgard-ai-platform). 496 words, ~1,371 tokens.

name

hum-rhetoric

description

Apply classical rhetoric — Ethos, Pathos, Logos — to analyze persuasive communication and craft effective arguments. Use this skill when the user needs to make a speech more persuasive, analyze why a piece of communication is effective, write a compelling proposal, or evaluate rhetorical strategies — even if they say 'make this more convincing', 'why is this speech so powerful', or 'how do I persuade the board'.

metadata.category

WP-19 文學院/人文

metadata.tags

humanities, rhetoric, persuasion, communication

IRON LAW: All Three Appeals, Calibrated to Audience

Logos alone convinces analysts but bores executives. Pathos alone moves
hearts but lacks substance. Ethos alone relies on reputation that may
not exist.

Every persuasive communication must use all three, weighted by audience:
- Technical audience: Lead with Logos, support with Ethos
- Executive audience: Lead with Pathos (vision), support with Logos (data)
- Public audience: Lead with Ethos (trust), amplify with Pathos

# Rhetorical Analysis: {Text/Speech}

## Rhetorical Situation
- Speaker: ...
- Audience: ...
- Purpose: ...
- Context: ...

## Appeal Analysis
| Section | Appeal | Technique | Effectiveness |
|---------|--------|-----------|--------------|
| {quote/section} | Ethos/Pathos/Logos | {specific technique} | H/M/L |

## Overall Balance
- Ethos: {strong/weak} — {evidence}
- Pathos: {strong/weak} — {evidence}
- Logos: {strong/weak} — {evidence}

## Verdict
{Overall effectiveness and recommendations for improvement}

© asgard-ai-platform, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in hum-rhetoric of asgard-ai-platform/skills.

• SKILL.md
• examples/sample_scenario.md
• references/speech-structures.md

Open the folder on GitHubat commit 4e7f4f8