Skip to main content
ClaudeWave
Skill95 estrellas del repoactualizado 1mo ago

rhetorical-analyst

>-

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/infranodus/skills /tmp/rhetorical-analyst && cp -r /tmp/rhetorical-analyst/skill-rhetorical-analyst ~/.claude/skills/rhetorical-analyst
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Rhetorical Analyst

A skill for rigorous analysis of arguments and debate — mapping rhetorical moves, scoring them across three dimensions, and exposing hidden assumptions including the analyst's own.

---

## Core Principles

### Three dimensions of analysis

Every argument gets evaluated on three distinct axes — never collapse them:

1. **Persuasion** — Does it work emotionally and socially? Does it build trust, tap genuine grievances, shift the terrain effectively?
2. **Rhetoric** — Is the structure sound? Does it use classical devices (concession, pivot, ethos-building) competently?
3. **Logic** — Do the premises actually support the conclusion? Are there fallacies, hidden assumptions, missing steps?

A move can score high on persuasion and low on logic simultaneously. Keep them separate. The most interesting cases are arguments that are rhetorically strong but logically incomplete — or logically sound but rhetorically inert.

### Follow the argument, not your priors

The most common failure in rhetorical analysis is treating one position as the neutral baseline and the other as the claim requiring justification. This is a hidden prior, not an analytical finding.

**Always ask**: whose frame am I implicitly accepting as "reasonable"? If the analysis consistently asks one side to justify itself while letting the other side's assumptions pass unchallenged, that asymmetry is itself a bias to name and correct.

This applies especially when:

- One position is more institutionally mainstream than the other
- One position uses more polished or "measured" language
- The analyst (including Claude) was trained on corpora that favor a particular milieu

### Understanding is not endorsing

One of the most common category errors in debate is collapsing three distinct acts:

- **Understanding** a logic — epistemic, always necessary. You cannot navigate a situation you refuse to see clearly.
- **Endorsing** a logic — normative, always optional. Understanding why something operates does not mean agreeing it should.
- **Responding** to a logic — strategic, where the real work is.

When an analyst or debater says "this logic makes sense even if we don't like it," opponents frequently hear endorsement. That's a category error — and it's a strategically paralyzing one. If you refuse to understand an operating logic because understanding feels like endorsing, you cannot formulate an effective response to it.

**Face reality clearly so you can respond to it effectively.** The principled position is not "refuse to engage with power logic." It is: understand it clearly, don't pretend it isn't operating, and build the most effective principled response from that honest starting point.

This also means: when someone in a debate is accused of endorsing something they were only describing, that accusation is itself a move worth naming. It shifts the terrain from substance to allegiance, and it usually signals that the accuser has no answer to the descriptive claim.

The three-part separation also generates the only productive path out of most political deadlocks: nobody needs to agree with the logic, but understanding it — and then finding a way to resolve it while staying true to your own principles — is the only way forward. Ideological claims that don't engage the operating logic don't change the perpetrator's behavior. They just make the claimant feel righteous while the situation continues.

### Hidden assumptions shape the evidence space — symmetry is the correction

Hidden assumptions in rhetorical analysis don't primarily distort conclusions — they determine what gets treated as evidence at all. Before anyone weighs evidence, a prior set of assumptions has already decided which observations are relevant, which comparisons are valid, and which absences are significant. The analyst experiences this as reading the evidence. They are actually applying a template that was built before they encountered the text.

This has two consequences worth naming:

**In individual cases**, general patterns — "aggressive openers signal insecurity," "concessions signal weakness" — get applied to specific instances where the pattern may not hold. The instance gets filed as confirmation of the template, and the analyst calls this evidence-following. The test: ask what in this specific exchange could have produced a different conclusion. If nothing could have, the analysis wasn't tracking the evidence — it was tracking the assumption.

**In public discourse**, language converts private assumptions into portable concepts — "motivated reasoning," "institutional hypocrisy," "in-group signaling" — that travel and get applied by others who adopt the name without examining the assumption underneath it. Technical vocabulary creates the appearance of neutrality. When an analyst says "this is a tu quoque" they sound like they're reporting a fact about the text. They're applying a categorization scheme with its own history and contestable boundaries. The language of analysis is in the same register as the language of description, which makes the two easy to confuse. What gets exported into public discourse is treated as a finding rather than a frame.

A further consequence: public discourse disciplines what can be stated at all. Hidden assumptions that can't be articulated in the available rhetorical norms simply don't enter — not because they've been examined and rejected, but because there's no slot for them. This is the mechanism behind respectable language insulating bad policy from accountability: it's not only that polish obscures, it's that it sets the terms of what can be stated, making anything outside those terms invisible as a possible position.

**The correction is symmetry.** Apply the same evidential standard to every position in the exchange, including your own. When a technical or evaluative term appears in your analysis, verify it can be grounded in plain language first — if you can't describe the phenomenon plainl
infranodusSkill

>

actionizeSkill

|

cognitive-variabilitySkill

Guide conversations through dynamic shifts between zoom levels (scale) and connecting/exploring (intent) to unlock creative breakthroughs and prevent rigid thinking. Helps enhance and develop biased, focused, diversified, dispersed states. Receives signals from writing assistant's pattern detection to diagnose cognitive states. Identifies structural gaps between idea clusters as spaces for innovation. Tracks temporal dwelling patterns and manages energy across personality modes. Uses playfulness for difficult transitions from chaos to clarity. Reads emotional feedback—inspiration signals continuation, exhaustion/frustration trigger transitions. Prevents obsessive loops through sustainable cycling through topical clusters and latent nodes. Maximum creative potential lives in gaps and dissipative states. Apply for complex analysis, when a user is stuck, breakthroughs, decision paralysis, group facilitation, breaking repetitive patterns, or when grammatical patterns reveal cognitive issues.

critical-perspectiveSkill

Engage in critical thinking by questioning assumptions, exploring alternative perspectives, and uncovering latent topics in conversations. Use when discussions could benefit from deeper exploration, when identifying blind spots, or when broadening understanding through respectful challenge and curiosity-driven inquiry.

embodied-navigationSkill

Transfer embodied movement principles (Vipassana equanimous scanning, Systema adaptive fluidity, contemporary dance tensegrity, EightOS confluence) to navigate work, relationships, projects, strategy, and everyday situations. Uses InfraNodus MCP tools to map situations as networks and apply body-informed intelligence to their structure. Trigger when someone is stuck, in conflict, negotiating, blocked, fixated, overwhelmed, or facing rigidity — or asks for "embodied advice", "fluid approach", "organic strategy", "adaptive strategy", "how would the body handle this". Also trigger on phrases like "I'm stuck", "standoff", "tense situation", "can't move forward". Apply proactively when situations exhibit excessive force, single-point fixation, or neglect of peripheral dynamics.

llm-wikiSkill

>

ontology-generatorSkill

Generate comprehensive ontological knowledge graphs in [[wikilinks]] syntax for InfraNodus visualization. Use when the user requests to create an ontology, extract entities and relationships from text, or generate knowledge graph structures. Handles both topic-based ontology generation and entity extraction from existing text. Output is formatted for direct paste into InfraNodus.com for network visualization and AI-powered gap analysis.

perspective-reversalSkill

>