Verification-first methodology for the Special Tribunal for Lebanon. Citations are verified against the STL legacy archive and legal-tools.org. Covers the Ayyash et al. case, the two contempt cases (STL-14-05 New TV/Al-Khayat and STL-14-06 Akhbar Beirut/Al-Amin), and the 2011 terrorism decision. Research aid, not legal advice. Part of the open-source \"Skills for International Justice\" library — methodology: github.com/jeannesulzer/international-criminal-tribunals-skills
npx skills add https://github.com/lawve-ai/awesome-legal-skills --skill stl-lebanon-jeanne-sulzer
This skill governs every output that touches the Special Tribunal for Lebanon. The discipline is simple and the reason for it is concrete: the STL is the only international tribunal in modern history to have adjudicated a single political assassination as terrorism under a hybrid framework applying Lebanese domestic law within an international procedural architecture. Its case numbers are exact, its in absentia trial framework is unusual, and its 2011 Interlocutory Decision on the Applicable Law is one of the most-cited (and most-contested) post-9/11 jurisprudential developments in international criminal law. A fabricated citation here misrepresents holdings that are still being debated.
For any case-specific document — judgment, decision, indictment, filing, OTP submission, victim participation order — verify before citing. "Verify" means web_fetch (or equivalent retrieval) to stl-tsl.org (the legacy site, archived since closure on 31 December 2023) or legal-tools.org in the current conversation. Foundational texts in project knowledge (UN-Lebanon Agreement, Statute of the STL annexed to Resolution 1757, Rules of Procedure and Evidence) are the exception; they may be cited directly. Nothing else.
In practice, retrieval to stl-tsl.org usually works — the site is preserved as a legacy archive but is no longer actively maintained, so some materials are more reliably reached on legal-tools.org. Three levels:
Label the level where relevant. The 2011 Interlocutory Decision and the Ayyash Trial Judgment are constantly paraphrased; if quoting, verify the exact wording against the official text.
Step 0 — Identify the document. Before anything else, distinguish:
The case identifier matters. STL-11-01 is the principal case; STL-18-10 is a related-attacks case that was opened later. Confusing them corrupts everything downstream.
Step 1 — Plan citations. List every citation that will appear in the output. For each, note the proposition it supports and the source to verify against.
Step 2 — Verify with the fallback ladder. For each case-specific citation, work the ladder in references/verification-workflow.md: stl-tsl.org → legal-tools.org → ICC Legal Tools (which mirrors STL documents) → secondary source clearly labelled → ask the user. Capture case number, document number, chamber, date, paragraph.
Step 3 — Draft using verified material. Use the citation format in references/citation-format.md. Where verification is partial, say so.
Step 4 — Self-audit. Each citation must trace to project knowledge or to a successful retrieval in this conversation, with verification level appropriate to the claim.
If not in project knowledge, retrieve from stl-tsl.org/en/documents/statute-of-the-tribunal before citing. See references/foundational-texts.md.
Tier 1 (authoritative):
Tier 2 (secondary, must be labelled):
legal.un.org/avl/) — for the Statute introductory note and Resolution 1757 commentaryNever authoritative: Wikipedia, Grokipedia, social media, AI-generated summaries, blogs (unless from a serious scholar).
See references/authoritative-sources.md.
STL citations are precise. Two pieces matter for every case-specific citation:
STL-[YY]-[NN] (year of indictment confirmation + sequential number). Examples:STL-11-01 — Ayyash et al. (main case)STL-13-04 — Merhi (joined with main case in 2014)STL-18-10 — Ayyash et al. (connected attacks of El-Murr, Hawi, Hamadeh)STL-14-05 — New TV S.A.L. and Al-Khayat (contempt)STL-14-06 — Akhbar Beirut S.A.L. and Al-Amin (contempt)STL-[YY]-[NN]/[Phase]/[Chamber] followed by a filing number. Phase suffixes:I — Pre-Trial / InterlocutoryPT — Pre-Trial ChamberT — Trial ChamberS — SentencingA — Appeals ChamberA-1 — Appeal of the first judgmentR[number]bis — Rule-based proceedings (e.g. R176 bis for the 2011 Applicable Law decision)Document references work like ICC: filing number assigned in chronological order by the Court Records Office. Example: STL-11-01/T/TC/F3840 (filing 3840 in case STL-11-01 before the Trial Chamber, with TC indicating Trial Chamber sealing).
Decisions cite by case number, document type, chamber, title, date, paragraph.
Worked examples:
See references/citation-format.md for the full guide, case-name conventions, and the table of frequently cited authorities.
The Appeals Chamber's Interlocutory Decision on the Applicable Law of 16 February 2011 (STL-11-01/I/AC/R176bis) is among the most discussed STL decisions, and the most often miscited. Its key findings:
Always indicate the contested character of the customary-international-law finding when relevant. The decision is a Tier 1 source for STL jurisprudence; it is not a universally accepted statement of customary international law.
When the user supplies a document:
In either mode, Step 0 (identify the document) comes first.
The skill does not encode doctrine line by line. Starting points:
For each, verify the specific decision through the workflow before citing. See references/jurisprudence-map.md.
The STL adjudicated the 14 February 2005 attack on Hariri — a political assassination embedded in the Lebanese sectarian political system, the Syrian withdrawal from Lebanon, and the Hezbollah question. The Tribunal's findings continue to be politically contested in Lebanon, and the convicted defendant remains at large. Maintain factual precision, identify holdings carefully, and remember that the *Ayyash* Trial Judgment expressly noted that the evidence did not implicate Hezbollah's leadership — a sensitive and important finding. Avoid sensationalism. Use the public, non-confidential versions of documents.
references/authoritative-sources.md — source hierarchy and URL patterns specific to the STLreferences/citation-format.md — case-number anatomy, phase suffixes, party-designation conventions, and the table of frequently cited authorities (Ayyash, Merhi, the 2011 Interlocutory Decision, contempt cases)references/verification-workflow.md — step-by-step procedure, fallback ladder, the in-absentia / Defence Office disciplinereferences/foundational-texts.md — the UN-Lebanon Agreement, Resolution 1757, the Statute, and the Rules of Procedure and Evidence; how to work with themreferences/jurisprudence-map.md — topic-by-topic map of the STL's principal holdingsexamples/example-verification.md — verifying one STL citation end-to-end (the 2011 Interlocutory Decision)examples/example-audit.md — auditing user-supplied documents (Ayyash Trial Judgment and the 2011 Interlocutory Decision typical errors)Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.
Efficient database search tool for bioRxiv preprint server. Use this skill when searching for life sciences preprints by keywords, authors, date ranges, or categories, retrieving paper metadata, downloading PDFs, or conducting literature reviews.
Query and analyze scholarly literature using the OpenAlex database. This skill should be used when searching for academic papers, analyzing research trends, finding works by authors or institutions, tracking citations, discovering open access publications, or conducting bibliometric analysis across 240M+ scholarly works. Use for literature searches, research output analysis, citation analysis, and academic database queries.
Access USPTO APIs for patent/trademark searches, examination history (PEDS), assignments, citations, office actions, TSDR, for IP analysis and prior art searches.
Multiagent AI system for scientific research assistance that automates research workflows from data analysis to publication. This skill should be used when generating research ideas from datasets, developing research methodologies, executing computational experiments, performing literature searches, or generating publication-ready papers in LaTeX format. Supports end-to-end research pipelines with customizable agent orchestration.
Automated LLM-driven hypothesis generation and testing on tabular datasets. Use when you want to systematically explore hypotheses about patterns in empirical data (e.g., deception detection, content analysis). Combines literature insights with data-driven hypothesis testing. For manual hypothesis formulation use hypothesis-generation; for creative ideation use scientific-brainstorming.
Take lawve-ai/stl-lebanon-jeanne-sulzer from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.