Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Proposition Checking

ASecurity

Use when users say "does this authority support the point", "check propositions", "fact-check this argument", "verify record support", or need cited cases, statutes, exhibits, transcripts, emails, or pleadings checked against legal or factual propositions.

15 stars
0 votes
0 copies
2 views
Added 6/7/2026
ai-agentsgogitapi

Works with

apimcp

Security Analysis

A100/100

Scanned 6/7/2026

$npx -y skills add ThomasMoreAI/legal-skills-open --skill proposition-checking --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Proposition Checking?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Proposition Checking
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-proposition-checking/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-proposition-checking)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: proposition-checking
title: proposition-checking
description: Use when users say "does this authority support the point", "check propositions", "fact-check this argument", "verify record support", or need cited cases, statutes, exhibits, transcripts, emails, or pleadings checked against legal or factual propositions.
author: LegalQuants
author_url: https://github.com/LegalQuants/lq-skills/tree/main/skills/proposition-checking
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: litigation
language: en
tags: [briefs, citations, factual-record, proposition-checking, hallucination-detection]
---

# proposition-checking

## When to Use

- A brief, skeleton argument, motion, memo, advice note, or witness statement makes propositions tied to citations.
- The user wants to know whether cited cases, statutes, exhibits, or witness evidence actually support the statement made.
- A citation exists, but the concern is misuse rather than fabrication.
- The user asks whether a quotation, paraphrase, or record reference is accurate.

This skill checks support. It does not predict who wins and does not replace legal judgment.

## Audience and Work Shape

Audience: litigators, legal researchers, trainees, and paralegals checking draft arguments or evidence summaries for lawyer review.

Work shape: pattern-matched source checking with accretive judgment. The skill maps propositions to sources and grades support; it does not make the legal argument for the user.

## Legal Failure Modes

- Legal support, not legal advice: support classification is a verification aid, not a merits opinion.
- Privilege/confidentiality: drafts, exhibits, transcripts, and advice notes may be privileged or confidential; use approved environments and mark source limitations.
- Accountability: the responsible lawyer decides whether to keep, narrow, replace, or abandon the proposition.

## Access Modes

This skill works in three modes:

1. **Live source mode** - use browser, web search, MCP, API, or other configured access to retrieve authorities, statutes, rules, or public records.
2. **User-supplied source mode** - use uploaded or pasted judgments, statutes, exhibits, pleadings, transcripts, correspondence, witness statements, or record bundles.
3. **No-source mode** - extract propositions and citations, then prepare a verification queue. Do not classify support as `supported`, `unsupported`, or `contradicted`.

If the source cannot be retrieved or supplied, mark the proposition `unverified-source-unavailable`. Do not assess source support from model memory.

## How It Works

### 1. Separate propositions from citations

For each paragraph, extract:

- The proposition being asserted.
- Whether it is legal, factual, procedural, evidential, or mixed.
- The citation or record reference offered in support.
- Any direct quotation.

Do not treat a string citation as support until the proposition it supposedly supports is identified.

### 2. Retrieve or read the source

Use supplied source text first:

- Case text, statute, regulation, pleading, exhibit, transcript, witness statement, expert report, or correspondence.
- Public sources or research tools only if available and approved.

If the source cannot be retrieved, classify the proposition as `unverified`, not unsupported.

For every source used, record the source type, URL or document identifier, access date, and pinpoint. Do not assess support from model memory.

## Confidence Bands

- High: source text is available, pinpointed, and directly supports or contradicts the proposition.
- Medium: source text is available but the proposition depends on interpretation, context, admissibility, or legal characterization.
- Low: source unavailable, quote incomplete, conflicting sources, or `needs_review` / `unverified_source_unavailable`.

### 3. Compare proposition to source

Classify each proposition:

- `supported` - source directly supports the proposition.
- `partially-supported` - source supports part of it, but the draft overstates or omits a condition.
- `unsupported` - source does not support the proposition.
- `contradicted` - source cuts the other way.
- `quote-inaccurate` - direct quotation is materially wrong.
- `unverified` - source unavailable or insufficient.

For legal propositions, distinguish:

- Existence of authority.
- Accuracy of the holding.
- Applicability to the jurisdiction, court level, facts, and procedural posture.

For factual propositions, distinguish:

- The source says the fact.
- Whether admissibility, competence, hearsay, privilege, or procedural use appears to require lawyer review under the governing rules.
- The fact is disputed elsewhere in the supplied record.

### 4. Report with traceability

Output:

| Field | Meaning |
|---|---|
| `paragraph` | source paragraph or location |
| `proposition` | claim being checked |
| `citation` | authority or record cite |
| `status` | support classification |
| `source_location` | page, paragraph, Bates, section, exhibit, or other pinpoint |
| `source_excerpt` | exact supporting or contradicting text |
| `problem` | overstatement, mismatch, missing source, etc. |
| `suggested_fix` | narrow, replace cite, add source, or remove |

Use short excerpts. The goal is fast lawyer verification, not a replacement brief.

### 5. Identify dependency risk

After checking individual propositions, summarize:

- Arguments that depend on unsupported propositions.
- Citations repeatedly misused for the same point.
- Facts contradicted by the record.
- Authorities that exist but are cited for the wrong doctrine.
- Unverified sources that need manual research.

## Escalation

Stop and route to the responsible lawyer when a key proposition is contradicted, an authority appears fabricated, a quote is materially inaccurate, admissibility/privilege controls the answer, or the user asks for merits advice rather than source support.

## Example

```text
Check whether each cited authority in this draft actually supports the proposition it is cited for. Separate citation existence problems from misuse problems.
```

For a compact output pattern, see `examples/output.md`.
For proposition types, support states, and argument dependency mapping, see `references/proposition-checking-model.md`.

## Limitations

- A source may support a proposition legally only after jurisdiction-specific research.
- The skill cannot assess undisclosed record material.
- `unverified` is not a merits conclusion.
- Admissibility and evidential competence concerns should be flagged for lawyer review unless the user supplies the governing rule and enough context to apply it.
- Privileged or sealed materials require an approved processing environment.

Attribution

ThomasMoreAIThomasMoreAI
View sourceSee grades on GitHubMore from ThomasMoreAI →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →