Rhetorical Analysis Skill

A Claude skill for rhetorical and epistemological analysis of articles, speeches, and argumentative texts.

Features

• Toulmin Model Analysis: Decompose arguments into claim, grounds, warrant, backing, qualifier, and rebuttal
• CRAAP Test: Evaluate source reliability (Currency, Relevance, Authority, Accuracy, Purpose)
• Fallacy Detection: Identify logical fallacies from a comprehensive catalog
• XLSX Report Generation: Export structured analysis to Excel format

Example Data

This repository includes example analysis files that are either synthetic (created for
demonstration) or public domain content:

These examples demonstrate the analysis format without any copyright concerns. To analyze
your own articles, see the JSON Schema documentation.

Note: The benchmark/ directory (if present) may contain analyses of copyrighted
content and is excluded from the distributed package and git tracking.

Download

Pre-packaged .skill archives are available for download from GitHub Releases.

Installation Steps

1. Navigate to the Releases page
2. Download the latest .skill file (e.g., rhetorical-analysis-0.1.0.skill)
3. Use the .skill file with your Claude-compatible application

GitHub automatically provides checksums for all release assets if you need to verify integrity.

Development Installation

uv sync --all-extras

Usage

Generate Analysis Report

uv run python scripts/generate_analysis.py input.json output.[xlsx|json|md] --format [xlsx|json|md]

Examples:

uv run python scripts/generate_analysis.py analysis.json rapport_analyse.xlsx --format xlsx
uv run python scripts/generate_analysis.py analysis.json analysis_output.json --format json
uv run python scripts/generate_analysis.py analysis.json rapport.md --format md

Package the Skill

The package_skill.py script validates and packages the skill for distribution.

# Create distributable .skill archive
uv run python scripts/package_skill.py

# Preview files without creating archive
uv run python scripts/package_skill.py --dry-run

# Output to specific directory
uv run python scripts/package_skill.py --output dist/

Validation

The script validates SKILL.md before packaging:

• Requires YAML frontmatter with name and description fields
• Enforces maximum 500 lines

Excluded Files

The following patterns are excluded from the archive by default:

Output

The archive is named {skill-name}-{version}.skill, e.g., rhetorical-analysis-0.1.0.skill.

Development

Run Tests

uv run pytest tests/ -v

Project Structure

.
├── SKILL.md              # Skill entry point (read by Claude)
├── scripts/              # Python scripts
│   ├── generate_analysis.py
│   └── package_skill.py
├── references/           # Reference documentation
│   ├── fallacies-catalog.md
│   └── existing-frameworks-and-tools.md
├── assets/               # Example files and templates
│   ├── example_analysis.json    # Synthetic example (CC0)
│   ├── example_ddhc_1789.json   # Public domain example
│   └── SCHEMA.md                # JSON format documentation
├── benchmark/            # Benchmark data (not distributed)
└── tests/                # Unit tests

Creating a Release (Maintainers)

Releases are automated via GitHub Actions when version tags are pushed.

Release Process

1. Update version in pyproject.toml to match the release version (e.g., 0.1.0)
2. Commit changes and push to main branch
3. Create and push tag with the version number:

bash git tag v0.1.0 git push origin v0.1.0

1. GitHub Actions automatically:
2. Runs the packaging script (scripts/package_skill.py)
3. Creates a GitHub Release with the tag name
4. Uploads the .skill archive as release asset

Tagging Conventions

• Standard releases: v<major>.<minor>.<patch> (e.g., v1.0.0, v0.2.1)
• Pre-releases: Include suffix -alpha, -beta, or -rc (e.g., v0.1.0-alpha, v1.0.0-rc1)
• Pre-releases are automatically marked as such on GitHub

Version Consistency

Ensure the Git tag version matches the version field in pyproject.toml:

• Tag v0.1.0 should correspond to version = "0.1.0" in pyproject.toml
• The .skill archive name is derived from pyproject.toml
• Mismatches will be visible to users but won't fail the workflow

Troubleshooting

Workflow fails during packaging:

• Check the workflow logs in the Actions tab
• Verify SKILL.md passes validation (max 500 lines, valid YAML frontmatter)
• Test locally: uv run python scripts/package_skill.py --dry-run

Need to fix a release:

1. Delete the tag locally and remotely:

bash git tag -d v0.1.0 git push origin :refs/tags/v0.1.0

1. Delete the GitHub Release in the web interface
2. Fix the issue, then create the tag again

License

MIT