Verification-first methodology for Section I (War Crimes) of the Court of Bosnia and Herzegovina. Citations are verified against the Court of BiH, the ICTY/IRMCT archives and OSCE. Distinguishes ICTY-referred (Rule 11 bis) cases from locally-initiated ones; covers Stanković, Janković and the Maktouf lex mitior ruling. 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 special-panels-timor-leste-jeanne-sulzer-2
This skill governs every output that touches the Special Panels for Serious Crimes of the Dili District Court (SPSC), also referred to as the East Timor Tribunal. The discipline is simple and the reason for it is concrete: the SPSC was the first hybrid criminal jurisdiction created internally by the United Nations through a transitional administration, prosecuting serious crimes committed during the Indonesian occupation of East Timor (1975-1999) — and particularly during the post-referendum violence of August-October 1999 in which approximately 1,400 people were killed and hundreds of thousands were displaced. Its jurisprudence is foundational for understanding internationalised justice in post-conflict transition.
For any case-specific document — judgment, decision, indictment, filing — verify before citing. "Verify" means web_fetch (or equivalent retrieval) to Tier 1 sources (JSMP — Judicial System Monitoring Programme; UC Berkeley Human Rights Center digital archive of SPSC records; UN UNTAET archives; legal-tools.org) in the current conversation. Foundational texts in project knowledge (UNTAET Regulations 2000/11, 2000/15, 2000/30) are the exception; they may be cited directly. Nothing else.
The SPSC held approximately 55 trials involving approximately 88 accused, resulting in 84 convictions and 4 acquittals (out of 391 persons indicted across 95 indictments — the vast majority, some 339 accused, remained in Indonesia and never stood trial). Three levels:
Label the level where relevant. SPSC archives are distributed across multiple repositories (the court itself ceased to function in 2006, and no successor institution maintains a unified archive) — this makes verification more challenging than for ongoing institutions.
Step 0 — Identify the document. Before anything else, distinguish:
Step 1 — Plan citations. List every citation and the proposition it supports. Distinguish SPSC trial proceedings from SCU indictment phase from CAVR Community Reconciliation Procedures.
Step 2 — Verify with the fallback ladder. JSMP archive → UC Berkeley Human Rights Center digital archive → UN UNTAET archives → legal-tools.org → academic literature (Caitlin Reiger, Suzannah Linton, Sylvia de Bertodano) → ask the user.
Step 3 — Draft using verified material. Use the citation format in references/citation-format.md.
Step 4 — Self-audit. Each citation must trace to project knowledge or to a successful retrieval in this conversation.
If not in project knowledge, retrieve from legal-tools.org or UN UNTAET archives.
Tier 1 (authoritative, but distributed):
Tier 2 (secondary, must be labelled):
Never authoritative: Wikipedia, Grokipedia, social media, AI-generated summaries.
See references/authoritative-sources.md.
SPSC citations follow a hybrid of Timorese civil-law conventions and international tribunal practice.
General form:
> *Prosecutor v. [Defendant(s)]*, Special Panels for Serious Crimes, Dili District Court, [Document type], Case No. [Number], [Date], [paragraph/page].
Case number format: generally No. XX/YYYY (serial/year), with prefix indicating the SCU indictment ("SCU.IND") or Court Case ("DC.CR"). Multiple numbering conventions were used; verify against the specific document.
Worked examples:
See references/citation-format.md for the full convention.
When the user supplies a document:
In either mode, Step 0 (identify the jurisdiction, the institutional context, and the document type) comes first.
The skill does not encode doctrine line by line. Starting points:
For each, verify the specific decision through the workflow.
The 1999 post-referendum violence in Timor-Leste (August-October 1999) produced approximately 1,400 deaths and over 400,000 displaced persons, in addition to the broader toll of the Indonesian occupation (1975-1999) which the CAVR estimated at approximately 102,800 conflict-related deaths. The SPSC's findings are historically authoritative for the cases it tried.
The structural impunity of senior commanders (Indonesian military leadership) is the defining institutional feature of the Serious Crimes process. Some 391 persons were indicted (across 95 indictments); approximately 88 stood trial. The remainder — some 339, including the most senior — remained in Indonesia. Indonesia did not effectively cooperate with the SPSC despite the April 2000 MOU. This is the central political fact of the SPSC and should be acknowledged in any substantive output.
Sensitive topics include:
Approach with care:
references/authoritative-sources.md — source hierarchy and URLsreferences/citation-format.md — case-name conventions, panel designationsreferences/verification-workflow.md — fallback ladder, SPSC-specific trapsreferences/foundational-texts.md — UNTAET Regulations 1999/1, 2000/11, 2000/15, 2000/16, 2000/30, MOU UNTAET-Indonesia 2000references/jurisprudence-map.md — topic-by-topic map of SPSC holdingsexamples/example-verification.md — verifying one SPSC citation end-to-endexamples/example-audit.md — auditing user-supplied documentsAssists 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/special-panels-timor-leste-jeanne-sulzer-2 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.