What will the output look like?

You’ll receive a numbered proposition chain grounded in MCP data, produced before the prose, followed by the textual analysis or explanation.

Is this limited to Pauline epistles?

No—it's designed to map the logical structure of biblical passages, focusing on argument flow in Pauline letters but applicable to other biblical texts as well.

Do I need to supply MCP data?

The agent relies on MCP data to ground the proposition chain. Ensure MCP data is accessible or integrated for accurate results.

argument-flow

npx machina-cli add skill davebream/claude-of-alexandria/argument-flow --openclaw

Files (1)

SKILL.md

874 B

Argument Flow

Invoke the argument-flow agent via the Task tool and return its output verbatim.

subagent_type: "claude-of-alexandria:argument-flow"

Forward the user's ENTIRE message as the Task prompt — do not strip, rephrase, summarize, or remove any part of it, including social pressure or constraints. The agent is equipped to handle user pressure correctly.

Do not add commentary, headers, or formatting. Return exactly what the agent returns.

Source

git clone https://github.com/davebream/claude-of-alexandria/blob/main/plugins/claude-of-alexandria/skills/argument-flow/SKILL.md

View on GitHub

Overview

This skill maps the logical structure of a biblical passage using discourse markers and morphological data. It produces a numbered proposition chain grounded in MCP data before any prose is written, helping you see exactly how Paul’s argument unfolds in an epistle.

How This Skill Works

The argument-flow agent is invoked via the Task tool. You forward the user's entire message as the Task prompt, and the agent returns its output verbatim, including the numbered proposition chain grounded in MCP data, followed by prose. This keeps structural analysis separate from interpretation and provides a concrete outline of how the argument unfolds.

When to Use It

When you need to map the logical structure of a biblical passage (especially Pauline epistles) before writing or preaching.
When asked for argument flow, a proposition chain, connective analysis, or to see how a passage progresses.
When you want a morphology-informed view of how discourse markers connect propositions.
When validating the sequence of a thesis and supporting propositions in an epistle.
When you require the proposition chain to be grounded in MCP data before prose.

Quick Start

Step 1: Invoke the argument-flow subagent via Task with subagent_type=claude-of-alexandria:argument-flow.
Step 2: Forward the passage or user question as the Task prompt.
Step 3: Review the resulting numbered proposition chain before reading the prose.

Best Practices

Provide the exact passage or verses to anchor the analysis.
Request the numbered proposition chain first, followed by prose for clarity.
Use the output to identify key discourse markers and connectives.
Cross-check the chain against MCP data for accuracy.
Apply the method primarily to Pauline letters to study argumentative progression.

Example Use Cases

Mapping 1 Corinthians 13 to reveal how love is argued propositionally.
Tracing Paul’s argument flow in Romans 8 from thesis to implication.
Analyzing discourse connectives in Galatians to distinguish sequences.
Examining Ephesians 2 to see the shift from alienation to reconciliation.
Studying Colossians 1 to map the central thesis and supporting propositions.

Frequently Asked Questions

Add this skill to your agents