Agent skill

Proposition Audit Anthony Searle

by lawve-ai in lawve-ai/awesome-legal-skills

Post-hoc verification and trust audit of AI-generated factual and interpretive claims.

Apache-2.0Auto-check passedResearch & Science

Install Proposition Audit Anthony Searle

skills CLI
$ npx skills add lawve-ai/awesome-legal-skills --skill proposition-audit-anthony-searle -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install lawve-ai/awesome-legal-skills proposition-audit-anthony-searle --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/proposition-audit-anthony-searle .claude/skills/proposition-audit-anthony-searle && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
proposition-audit-anthony-searle
GitHub stars
847
Token cost
~4.6k tokens
SKILL.md length
2,356 words
Files
4
Skills in repo
154
Repo updated
First seen
Licence
Apache-2.0

At a glance

Post-hoc verification and trust audit of AI-generated factual and interpretive claims.

  • Works in 5 steps: Agree the Threshold → Extract and Classify Claims → Search for Sources → …
  • Research & Science work in your project
  • SKILL.md covers Profile, Purpose, The Verification Process and Limitations and assumptions, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Proposition Audit Anthony Searle is an agent skill from lawve-ai/awesome-legal-skills. Post-hoc verification and trust audit of AI-generated factual and interpretive claims. Classifies claims by type and salience, routes them to domain-appropriate sources, scores trustworthiness on a tiered scale with an Interpolated verdict for plausible-but-unsupported detail, and assesses rhetorical fairness on interpretive claims. Designed for clinical-negligence and healthcare-law practice in England and Wales, with general applicability beyond.

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `README.md`).

It sits in Research & Science. The repository describes itself as: A curated list of awesome Agent Skills for automating legal work. The licence is Apache-2.0.

When your agent uses it

  • Research & Science work in your project

Example prompts

  • “/proposition-audit-anthony-searle”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Agree the Threshold
  2. Extract and Classify Claims
  3. Search for Sources
  4. Score Each Claim
  5. Produce the Audit Report

What it can do on your machine

Read from SKILL.md and the folder at commit 045f738. 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.

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

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    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

Proposition Audit Anthony Searle loads about 4.6k tokens when it runs. Until then it costs about 121 tokens; SKILL.md has 2,356 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~121
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k

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

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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 lawve-ai/awesome-legal-skills at commit 045f738, republished under its Apache-2.0 licence (© lawve-ai). 2,356 words, ~4,562 tokens.

Download SKILL.mdSave it as .claude/skills/proposition-audit-anthony-searle/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
proposition-audit-anthony-searle
description
Post-hoc verification and trust audit of AI-generated factual and interpretive claims. Classifies claims by type and salience, routes them to domain-appropriate sources, scores trustworthiness on a tiered scale with an Interpolated verdict for plausible-but-unsupported detail, and assesses rhetorical fairness on interpretive claims. Designed for clinical-negligence and healthcare-law practice in England and Wales, with general applicability beyond.
metadata.author
Anthony Searle
metadata.license
apache-2.0
metadata.version
2026-05-31

Proposition Audit — AI Output Trust Verification

Profile

  • Jurisdiction: England and Wales (the maintained domain-routing profile; other jurisdictions illustrated under Step 2).
  • Practice area: Clinical negligence and healthcare law (the maintained example domain; the methodology generalises to any field where AI-drafted factual content needs structured verification).
  • Intended user: A practitioner verifying AI-generated factual or interpretive content before professional reliance — publication, court use, formal external use, or internal reliance.

Purpose

AI-generated research, statistics, citations, and factual claims require structured verification before professional use. This skill provides a systematic post-hoc audit — classifying each claim by type and salience, searching domain-appropriate sources, scoring trustworthiness transparently, and flagging what needs attention.

This complements rather than replaces rigour during generation. It is an independent verification layer applied to completed output.

The Verification Process

Step 1: Agree the Threshold

Before beginning verification, ask what minimum standard applies to this use case. Offer these defaults if the user has no preference:

  • Publication or formal external use (skeleton arguments, blog posts, published advice, court documents, regulatory submissions, external correspondence on file): 90%+ (empirical), Accurate (legal), Fair (rhetorical). Remove or independently verify anything below threshold.
  • Internal working documents (drafts circulated for review, internal research notes, working files): 70%+. Flag claims below threshold but they may be retained with caveats.
  • Exploratory research (early-stage research to identify avenues for further investigation): 50%+. The purpose is to identify which claims merit further investigation, not to produce a final verified output.
Step 2: Extract and Classify Claims

Extract each distinct factual or interpretive claim from the output. Break composite sentences into their constituent sub-claims — each gets verified independently, because a sentence can be half-right and half-wrong. Where a single sentence contains claims of different types (a citation plus an empirical figure, for example), split it; each sub-claim is classified and scored independently.

Classify each claim by type:

  • Empirical fact — a verifiable statement about the world (a statistic, a date, a named event). Verify by source corroboration.
  • Citation or reference — a claimed source, case, study, or authority. Verify by locating the primary source and confirming it says what is attributed to it.
  • Legal or regulatory proposition — a statement about the law, regulation, or procedural rules. Verify by locating the primary legislative or judicial source and assessing whether the proposition accurately reflects it. Source-counting alone is insufficient here because legal accuracy depends on interpretive precision, not volume of agreement.
  • Interpretive or analytical claim — a conclusion drawn from evidence ("this suggests X", "the trend indicates Y"). These cannot be verified by corroboration. Instead, assess whether the underlying evidence exists, whether the reasoning is sound, whether credible counter-interpretations exist, and whether the opposing position is presented fairly (see rhetorical fairness in Step 4). Flag rather than score.

Then assign each claim a salience level:

  • Load-bearing — the surrounding argument turns on this claim. The argument fails or substantially weakens if the claim is wrong.
  • Supporting — strengthens the argument but is not strictly necessary to it.
  • Illustrative — used by way of example, colour, or background. The argument is unaffected by removal.

Salience determines proportionate remediation in Step 5. Load-bearing claims warrant Tier-1 corroboration; illustrative claims warrant a quick pass. Apply uniform scrutiny only if every claim is genuinely load-bearing, which is rare.

Step 3: Search for Sources

Search for independent corroboration using sources appropriate to the claim type. Do not verify from training data alone — every claim needs an active web search, because the whole point of this skill is to check what the model "knows" against external reality.

Source tiers:

  • Tier 1 (Definitive):
    • Clinical: Cochrane reviews, NICE guidelines, SIGN guidelines, royal college guidance (RCOG, RCS, RCP, RCPCH), peer-reviewed journals in the relevant specialty.
    • Legal: Primary legislation (legislation.gov.uk), reported judicial decisions (caselaw.nationalarchives.gov.uk, BAILII), Civil Procedure Rules and Practice Directions, the relevant procedural rules of the forum.
    • Statistical: Office for National Statistics, official government data, primary research datasets.
    • General empirical: Peer-reviewed journals, regulatory bodies' official outputs.
  • Tier 2 (Authoritative): Established news organisations (original reporting, not syndicated), university research centres, recognised professional and industry bodies, Law Commission reports, Hansard, MDU/MPS guidance.
  • Tier 3 (Supporting): Reputable industry reports, recognised expert commentary, specialist trade publications, established practitioner blogs.

Domain-specific search routing:

Generic web search performs poorly for technical claims — it surfaces secondary reporting rather than primary sources. Route accordingly:

  • Clinical or medical claims → PubMed, Cochrane Library, NICE, SIGN, and relevant specialty guidelines before general web search.
  • Legal claims (England and Wales) → legislation.gov.uk, caselaw.nationalarchives.gov.uk, BAILII, and the relevant procedural rules before general web search.
  • Legal claims (other jurisdictions, illustrative) → CourtListener and Westlaw for US, EUR-Lex for EU, the relevant primary-source service for other jurisdictions. The UK routing above is the maintained profile; others are illustrative and should be confirmed against the jurisdiction's actual primary-source register.
  • Statistical claims → locate the primary dataset or study, not secondary reporting of it.
  • Quantum or arithmetic claims (multiplier × multiplicand, periodical-payments calculations, life-expectancy adjustments, schedule-of-loss workings) → recompute deterministically against the inputs the source provided. Do not search; arithmetic is verifiable by recomputation, and web search performs poorly on numeric reasoning.
Step 4: Score Each Claim

Score empirical facts and citations on a 0–100% scale. Weight source quality above quantity — one definitive source is worth more than several weak ones, because a Cochrane review settling a clinical question is more reliable than three news articles paraphrasing each other. Two special verdicts (Unverifiable, Interpolated) sit outside the numerical scale and take precedence in their respective failure modes.

ScoreLabelMeaning
90–100VerifiedConfirmed by at least one Tier 1 source, or two Tier 2 sources with no contradictions.
70–89Likely accurateSupported by Tier 2 sources, or one Tier 1 source with minor caveats (figures close but not exact).
50–69Partially supportedSome corroboration exists but with qualifications, outdated sources, or imprecise alignment with the claim as stated.
30–49Weakly supportedOnly Tier 3 corroboration, or a single non-definitive source.
10–29Poorly supportedSources found but none credible or relevant.
0–9ContradictedCredible sources directly contradict the claim.
—UnverifiableSearch tools unable to surface adequate sources to assess this claim. Not a score — a transparency flag. Does not imply the claim is false.
—InterpolatedSpecial verdict (typical underlying score 30–59). The cited source exists and partially supports the claim, but plausible details have been added that the source does not contain. Distinct from "Partially supported" because the issue is invented detail, not imprecision. The most dangerous AI failure in legal writing because it produces fluent, source-shaped sentences that the cited authority does not actually support. Use this label in preference to "Partially supported" or "Weakly supported" whenever the failure mode is interpolation, and note the interpolated content explicitly in the caveat.

Important distinctions:

  • "Not found" is not "contradicted." If web search cannot surface adequate sources, mark the claim Unverifiable rather than scoring it low. The distinction matters because a low score implies evidence was found and was weak, while Unverifiable means the audit itself has a gap. The user can then decide whether to seek verification through other means.
  • For citation claims, score whether the source exists and says what is attributed to it. Partial accuracy (correct case name, wrong paragraph reference) sits at 50–69 with the discrepancy noted; invented sub-claims attached to a real citation sit at Interpolated.
  • Where a claim is close to accurate but imprecise (a rounded statistic, a slightly misstated date), note the discrepancy rather than simply passing or failing it.

Legal and regulatory propositions receive a qualitative assessment instead of a numerical score:

  • Accurate — Reflects the primary source precisely.
  • Broadly accurate — Reflects the substance but with minor imprecision a careful reader would notice.
  • Incomplete or misleading — Omits material qualification or context that changes the proposition's effect.
  • Inaccurate — Misstates the primary source.

State the primary source consulted and any interpretive nuance. Numerical scoring is inappropriate here because legal accuracy is about interpretive precision, not corroboration volume.

Interpretive or analytical claims are not scored. Flag four dimensions:

  • Evidence base — does the underlying evidence the claim relies on exist?
  • Logical soundness — does the inference from evidence to conclusion hold?
  • Counter-interpretations — do material counter-arguments or counter-interpretations exist that the claim does not engage with?
  • Rhetorical fairness — how is the opposing position presented? Use one of:
    • Fair — the opposing position is represented as its strongest version.
    • Slanted — selection bias in presentation; only weaker parts of the opposing view are surfaced.
    • Strawman — a weakened or distorted version of the opposing view is attacked.
    • Uncharitable — the opposing view is presented in a form its proponents would not recognise.

For case-comment, analytical writing, and skeleton arguments, rhetorical fairness is often the substantive failure mode — the AI may be factually accurate but argumentatively unfair to the losing side. The fairness assessment matters at least as much as the factual scoring for this category.

Show full SKILL.md (910 more words)Show less
Step 5: Produce the Audit Report

Present the report as structured inline text by default. Produce an HTML artifact only if explicitly requested or if the output contains more than 15 individually verified claims.

Include:

  1. Summary — total claims verified, breakdown by type and salience, overall confidence assessment as a narrative (not a single averaged number — averages obscure the difference between "mostly solid with one bad load-bearing claim" and "uniformly mediocre across illustrative claims").
  2. Claim-by-claim results — each claim quoted verbatim from the original output, its classification (type + salience), score or qualitative assessment, sources consulted (with URLs where available), and any caveats.
  3. Source disagreements — where authoritative sources consulted disagreed on the same point (NICE vs RCOG on a clinical question; majority and dissenting reasoning in a leading case; ONS vs research-paper figures on the same metric), present the disagreement explicitly rather than averaging the sources. Guideline and authority conflict is often the substantive point in a clinical-negligence dispute and should be surfaced as a finding.
  4. Action items — claims below the applicable threshold, calibrated to salience:
    • Load-bearing claims below threshold — remediate before reliance; the argument cannot proceed on an unverified load-bearing claim.
    • Supporting claims below threshold — remediate where practicable; may be retained with explicit caveats if remediation is disproportionate.
    • Illustrative claims below threshold — remove without rebuilding the argument; an illustrative claim that cannot be verified is not worth the audit risk.

Limitations and assumptions

This skill produces a structured audit; it does not produce certainty. Specific limitations:

  • Paywalled sources. Where the primary source is behind a paywall (Westlaw, LexisNexis, certain medical journals), the skill flags the citation and consults the abstract where available, but the body is not retrieved. The verdict is reported with a "paywalled — abstract only" caveat. Obtain full-text verification through institutional access before relying on a paywalled-only assessment of a load-bearing claim.
  • Web search dependence. This skill is useless without active web search. If the host platform's web-search tool is unavailable or rate-limited, the skill cannot perform the verification step and must report each empirical and citation claim as Unverifiable with the cause. Do not run this skill without confirming web search is available.
  • What this skill does NOT do. Three things complementary skills do better and should be reached for where the failure mode dominates:
    • Internal consistency checks across multiple LLM critics and a cross-family disagreement signal at generation time: see Verity (Johnny Ryan / ICCL Enforce), designed to run during generation as an MCP the primary model calls.
    • Citation-fidelity scoring of attached citations — does the cited source support the proposition attributed to it, even when the source is provided? See mhalle's claim-audit, designed for post-hoc audit of citation provenance.
    • Reasoning-trace verification of step-by-step inferences: outside the scope of any structured-audit skill. Requires manual review.
  • Complementary use. Where the failure mode dominates, reach for the complementary skills above directly. The three are good together: in-generation hallucination minimisation (Verity), post-hoc citation-fidelity scoring (mhalle's claim-audit), and post-hoc claim-type-classified verification with domain-routed search and rhetorical-fairness assessment (this skill).

Principles

  1. Every empirical and citation claim is treated as unverified pending an active search against a domain-appropriate source. The model's prior knowledge is not the audit source — only retrievable, current material is.
  2. Source quality outweighs source quantity. One definitive source is sufficient for a high score.
  3. Use the Unverifiable flag — not a low score — when search cannot surface adequate sources. A low score implies evidence was found and was weak; Unverifiable means the audit itself has a gap, and the user can then decide whether to seek verification through other means.
  4. Legal propositions require interpretive assessment against primary sources, not source-counting.
  5. Salience determines proportionate remediation. Spend audit budget where the argument turns, not uniformly across every claim.
  6. The audit informs the practitioner; it does not adjudicate. The verdict columns describe how strongly the evidence supports each proposition. The professional decision sits with the user.
  7. Do not silently pass over claims that are difficult to verify. If verification is impractical for a particular claim, say so explicitly and explain why.

Example

Source text:

"In Smith v Jones [2024] EWHC 999 (KB), the High Court held that the standard of care for a junior doctor is the same as that for a consultant, following Bolam v Friern Hospital Management Committee [1957] 1 WLR 582."

Audit at publication threshold:

  • Sub-claim 1. "Smith v Jones [2024] EWHC 999 (KB)" — citation; load-bearing; Contradicted (0–9). caselaw.nationalarchives.gov.uk and BAILII return no judgment under this neutral citation. The case is fabricated.
  • Sub-claim 2. "The standard of care for a junior doctor is the same as that for a consultant" — legal proposition; load-bearing; Inaccurate. The settled position is that a junior doctor is held to the standard appropriate to the post they occupy, not to the standard of a consultant. The authority is the Court of Appeal in Wilsher v Essex AHA [1987] QB 730 (per Mustill LJ), not Bolam.
  • Sub-claim 3. "following Bolam v Friern Hospital Management Committee [1957] 1 WLR 582" — citation; load-bearing; Inaccurate. Bolam exists and is the general professional-negligence test (the responsible-body-of-medical-opinion test) but does not address the junior-doctor calibration. The proposition is properly attributed to Wilsher.

Action items: at publication threshold every sub-claim fails. Rewrite the paragraph — substitute Wilsher v Essex AHA [1987] QB 730 as the authority for the junior-doctor standard, remove the fabricated Smith v Jones citation, and recast the proposition to reflect the actual test (standard of the post occupied) rather than the consultant-equivalence framing.

© lawve-ai, Apache-2.0. 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 3 other files in skills/proposition-audit-anthony-searle of lawve-ai/awesome-legal-skills.

  • SKILL.md
  • LICENSE
  • NOTICE
  • README.md

Open the folder on GitHubat commit 045f738

Compare with similar skills

Proposition Audit Anthony Searle next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Proposition Audit Anthony Searle compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Proposition Audit Anthony Searle this skilllawve-ai/awesome-legal-skills847—~4.6kAutomated safety check: PassApache-2.0
Hypothesis Generationspacering-net/codeg3.9k14 repos~3.6kAutomated safety check: NotesMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Nature Paper CardYuan1z0825/nature-skills47k2 repos~2.1kAutomated safety check: PassApache-2.0
Content Research Writerweapp-tailwindcss/weapp-tailwindcss1.9k25 repos~3.5kAutomated safety check: PassMIT
Last30daysmvanhorn/last30days-skill64k—~7.9kAutomated safety check: NotesMIT

Similar skills

  • Hypothesis Generation

    spacering-net/codeg

    Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.

    3.9k GitHub starsUsed in 14 repos~3.6k tokens
    Research & ScienceAuto-check: notes
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Nature Paper Card

    Yuan1z0825/nature-skills

    Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.

    47k GitHub starsUsed in 2 repos~2.1k tokens
    Research & ScienceAuto-check passed
  • Content Research Writer

    weapp-tailwindcss/weapp-tailwindcss

    Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.

    1.9k GitHub starsUsed in 25 repos~3.5k tokens
    Research & ScienceAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated yesterday
    Research & ScienceAuto-check: notes
  • Peer Review

    spacering-net/codeg

    Structured manuscript/grant review with checklist-based evaluation.

    3.9k GitHub starsUsed in 17 repos~5.9k tokens
    Research & ScienceAuto-check: notes

More from lawve-ai/awesome-legal-skills

All 154 skills in this repo
  • Customs Trade Law Onur Kafkas

    lawve-ai/awesome-legal-skills

    U.S. An agent skill from lawve-ai/awesome-legal-skills.

    847 GitHub stars~4.1k tokensUpdated 9 days ago
    Auto-check passed
  • Eu Data Act Oliver Schmidt Prietz

    lawve-ai/awesome-legal-skills

    Practitioner skill for advising on EU Regulation 2023/2854 (Data Act).

    847 GitHub stars~3.9k tokensUpdated 9 days ago
    Auto-check passed
  • Litigation Deadline Calendar

    lawve-ai/awesome-legal-skills

    Calendar litigation and arbitration deadlines from a scheduling order.

    847 GitHub stars~4.3k tokensUpdated 9 days ago
    Auto-check passed
  • Outlook Emails Lawvable

    lawve-ai/awesome-legal-skills

    Read, search, and download emails and attachments from Microsoft Outlook via OAuth2.

    847 GitHub stars~672 tokensUpdated 9 days ago
    Auto-check passed
  • Ambiguity Report

    lawve-ai/awesome-legal-skills

    Turn an interpretive-ambiguity audit of a legal text — contract, statute, regulation, or judicial opinion — into a polished deliverable.

    847 GitHub stars~4.6k tokensUpdated 9 days ago
    Auto-check passed
  • Az Eu Website Privacy Audit

    lawve-ai/awesome-legal-skills

    Audits a website for compliance with Azerbaijan's Law on Personal Data No.

    847 GitHub stars~3.8k tokensUpdated 9 days ago
    Auto-check passed

Questions about Proposition Audit Anthony Searle

What does Proposition Audit Anthony Searle do?

Post-hoc verification and trust audit of AI-generated factual and interpretive claims. Proposition Audit Anthony Searle is an agent skill from lawve-ai/awesome-legal-skills. Post-hoc verification and trust audit of AI-generated factual and interpretive claims.

When should I use Proposition Audit Anthony Searle?

Proposition Audit Anthony Searle fits situations like: research & Science work in your project.

How do I install Proposition Audit Anthony Searle in Claude Code?

Run `npx skills add lawve-ai/awesome-legal-skills --skill proposition-audit-anthony-searle -a claude-code`. Or copy the skill folder (skills/proposition-audit-anthony-searle in lawve-ai/awesome-legal-skills) into .claude/skills/proposition-audit-anthony-searle in your project. Claude Code loads it when a task matches its description.

How do I install Proposition Audit Anthony Searle in Codex?

Run `npx skills add lawve-ai/awesome-legal-skills --skill proposition-audit-anthony-searle -a codex`. Or copy the skill folder (skills/proposition-audit-anthony-searle in lawve-ai/awesome-legal-skills) into .agents/skills/proposition-audit-anthony-searle in your project. Codex loads it when a task matches its description.

Can I use Proposition Audit Anthony Searle in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lawve-ai/awesome-legal-skills --skill proposition-audit-anthony-searle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/proposition-audit-anthony-searle, .gemini/skills/proposition-audit-anthony-searle, .github/skills/proposition-audit-anthony-searle and .opencode/skills/proposition-audit-anthony-searle in your project.

What does Proposition Audit Anthony Searle need to run?

SKILL.md names no scripts, command-line tools or credentials: Proposition Audit Anthony Searle is instructions for the agent only.

Does Proposition Audit Anthony Searle access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Proposition Audit Anthony Searle safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Proposition Audit Anthony Searle use?

Proposition Audit Anthony Searle is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Proposition Audit Anthony Searle use?

About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Proposition Audit Anthony Searle?

Skills that share tags, products or a category with Proposition Audit Anthony Searle: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Proposition Audit Anthony Searle?

lawve-ai (a GitHub organization) maintains it in lawve-ai/awesome-legal-skills, which has 847 GitHub stars. The repository holds 154 skills in this directory. The repository was last updated on October 2, 2026.

Source: lawve-ai/awesome-legal-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.