Verification-first methodology for the Jurisdicción Especial para la Paz (JEP), Colombia's transitional justice court under the 2016 Acuerdo Final with FARC-EP. Citations are verified against jep.gov.co before use. Covers the 11 macrocasos (from Caso 01 secuestro through Caso 11 violencia sexual, including Caso 03 falsos positivos), the three sanction tiers (propias, alternativas, ordinarias), TOAR, and the SIVJRNR sister bodies (CEV, UBPD). Guards the key structural distinctions (Sala de Reconocimiento vs Tribunal para la Paz; comparecientes FARC-EP vs Fuerza Pública vs terceros civiles; Acto Legislativo 01/2017 vs Ley Estatutaria 1957/2019). Research aid, not legal advice.
npx skills add https://github.com/lawve-ai/awesome-legal-skills --skill jep-jeanne-sulzer
This skill governs every output that touches the Jurisdicción Especial para la Paz (JEP) — the Special Jurisdiction for Peace, the judicial component of Colombia's transitional justice system established by the 24 November 2016 Final Peace Agreement between the Government of Colombia and the FARC-EP. The discipline is simple and the reason for it is concrete: the JEP applies a distinctive restorative-justice model — it issued its first sentences in September 2025 applying *sanciones propias* (restorative non-custodial sanctions) for the gravest crimes of an internal armed conflict that lasted more than fifty years. Its procedure mixes Colombian civil-law structure, international criminal law standards, and a uniquely restorative-justice approach. Citation discipline matters acutely.
For any case-specific document — auto, providencia, resolución, sentencia, lineamiento — verify before citing. "Verify" means web_fetch (or equivalent retrieval) to jep.gov.co (the official JEP website) in the current conversation. Foundational texts in project knowledge (Acuerdo Final, Acto Legislativo 01 of 2017, Ley Estatutaria 1957 of 2019, Reglamento General) are the exception; they may be cited directly. Nothing else.
The JEP publishes extensively and the website is actively maintained, so jep.gov.co is the right first stop. But do not treat a successful fetch as guaranteed: direct retrieval can fail — an HTTP 403, a timeout, or a PDF that will not render — and that failure is structural, not a dead end. When it happens, walk the fallback ladder in references/verification-workflow.md rather than abandoning verification or citing from memory. Three levels:
Label the level where relevant.
Step 0 — Identify the document. Before anything else, distinguish:
Step 1 — Plan citations. List every citation that will appear and the proposition it supports.
Step 2 — Verify with the fallback ladder. jep.gov.co → UN Verification Mission in Colombia (colombia.unmissions.org) → Tier 2 academic / monitoring sources clearly labelled → 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 jep.gov.co (Documentos / Marco Normativo).
Tier 1 (authoritative):
comisiondelaverdad.co) — the Truth Commission's final report (June 2022) — Tier 1 for truth-and-historical-record findings, but not the JEP's own judicial recordubpdbusquedadesaparecidos.co) — for matters related to the search for the disappearedcorteconstitucional.gov.co) — for constitutional rulings affecting the JEP (notably the Sentencia C-080 of 2018 and subsequent decisions on the constitutionality of the Estatutaria)colombia.unmissions.org) — UN reporting and verification workTier 2 (secondary, must be labelled):
dejusticia.org) — Colombian think tank; high-quality monitoring and analysisNever authoritative: Wikipedia, Grokipedia, social media (even though the JEP has an active Twitter/X account — citing the JEP's own institutional Twitter is Tier 1 only for the specific press-release content; the substantive decisions are in the autos and sentencias).
JEP citations follow Colombian civil-law conventions. The citation format:
Macrocasos:
General form:
> *[Compareciente(s)]*, [Macrocaso], [Organ — Sala/Sección/Tribunal], [Document type], [Identifier and date].
Worked examples:
> Jurisdicción Especial para la Paz, Tribunal Especial para la Paz, Sección de Reconocimiento de Verdad y Responsabilidad, Sentencia (Caso 01 — Secuestro), 16 September 2025.
> Jurisdicción Especial para la Paz, Tribunal Especial para la Paz, Sección de Reconocimiento de Verdad y Responsabilidad, Sentencia (Caso 03 — Subcaso Costa Caribe, Batallón La Popa, Valledupar), 18 September 2025.
> Corte Constitucional de Colombia, Sentencia C-080 of 2018 (15 August 2018, M.P. Alejandro Linares Cantillo) — constitutional review of the Ley Estatutaria of the JEP.
See references/citation-format.md for the detailed convention.
When the user supplies a document:
In either mode, Step 0 (identify the macrocaso, organ, and document type) comes first.
The skill does not encode doctrine line by line. Starting points (each verified through the workflow):
For each, verify through the workflow.
The Colombian internal armed conflict, from approximately the mid-1960s to 2016, killed more than 450,000 people, displaced more than 7 million, and produced widespread atrocities by all parties: FARC-EP (kidnapping, attacks on civilians, recruitment of minors); other guerrilla groups (ELN, EPL, M-19); the Fuerza Pública (extrajudicial executions / "falsos positivos", forced disappearances, joint operations with paramilitary groups); paramilitaries (AUC, AGC, etc.); and others. The JEP's restorative-justice model — particularly the non-custodial sanciones propias for senior FARC-EP commanders responsible for 21,000 kidnappings — has been politically contested in Colombia. Maintain factual precision. Avoid characterising the sanciones propias as "impunity" or as "appropriate" in your own voice; reflect the contested character of the debate where relevant. Recognise that victims, FARC-EP, military, paramilitary survivors, and Colombian civil society are all reading this work. Use the JEP's own terminology (e.g. "comparecientes", "víctimas acreditadas", "sanciones propias", "TOAR"). Avoid both *Manichean* simplification and false equivalence.
The JEP issues *versiones reservadas* of many documents to protect victims, witnesses, and *comparecientes*. Cite only the public version, say so, and never reproduce reserved identifying information or attempt to identify a protected participant — the same public-record discipline the other skills in this suite apply to protected witnesses.
references/authoritative-sources.md — source hierarchy and URLs (jep.gov.co primary; CEV, UBPD, Constitutional Court, UN Mission)references/citation-format.md — Colombian civil-law citation conventions, the 11 macrocasos table, organ designations (Salas de Justicia, Tribunal Especial para la Paz, UIA), document typesreferences/verification-workflow.md — fallback ladder, JEP-specific traps (sanciones propias ≠ impunity; macrocaso vs case; FARC ≠ FARC-EP after 2017 transformation; Sala de Reconocimiento vs Tribunal Especial para la Paz; September 2025 historic sentences)references/foundational-texts.md — Acuerdo Final 2016, Acto Legislativo 01 of 2017, Ley Estatutaria 1957 of 2019, Ley 1922 of 2018, Reglamento General, Colombian Constitutional Court Sentencia C-080 of 2018references/jurisprudence-map.md — topic-by-topic map of JEP holdings (limited as of 2026 — first sentences only September 2025; primarily structural and procedural decisions before that)examples/example-verification.md — verifying the Caso 01 (secuestro) September 2025 sentenceexamples/example-audit.md — auditing user-supplied documents (sanciones propias vs prison sentence; FARC vs FARC-EP)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/jep-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.