>- Swiss legal source and authority triage. Use when a user asks a Swiss legal, regulatory, compliance, contract, employment, corporate, litigation, IP, tax, privacy, public-law, fintech, register, or cantonal-law question; when Swiss law may apply; or when an AI legal answer needs source routing across federal, cantonal, communal, regulator, register, contractual, professional, soft-law, multilingual, or open-data layers.
npx skills add https://github.com/lawve-ai/awesome-legal-skills --skill swiss-legal-source-authority-triage-enrique-g-zbinden
Use this skill to map the Swiss legal authority structure before producing a legal answer.
This skill does not provide Swiss legal advice. It helps an AI assistant identify the correct source layer, authority hierarchy, language/version checks, uncertainty flags, and human-review boundaries for Swiss legal research and legal-operations workflows.
Core thesis: for Swiss legal AI, route authority before generating an answer.
Use this skill whenever:
Do not present the output as legal advice. Use language such as:
> This is a Swiss legal source and authority triage, not legal advice. It identifies likely source layers and review points. A qualified Swiss lawyer should review any concrete legal position, filing, advice to a client, or operational decision.
Escalate clearly when the issue involves:
Classify the user's request as one or more of:
If the relevant canton, commune, regulator, sector, contract type, or factual setting is missing, proceed with explicit assumptions and flag the gap. Ask a clarifying question only when the missing fact makes source routing impossible.
Identify every layer that may control the answer:
| Layer | What to check |
|---|---|
| Federal law | Federal Constitution, federal acts, ordinances, treaties, federal official publications |
| Cantonal law | Cantonal constitution, acts, ordinances, court organisation, administrative practice |
| Communal/local law | Municipal rules, permits, zoning, police regulations, local public-law instruments |
| Official case law | Federal Supreme Court, Federal Administrative Court, Federal Criminal Court, Federal Patent Court, cantonal courts |
| Regulator practice | FINMA, FDPIC/EDÖB, COMCO/WEKO, SECO, Swissmedic, FTA/ESTV, BAKOM/OFCOM, fedpol/MROS, sector bodies |
| Registers/legal state | Zefix, cantonal commercial registers, SHAB/SOGC, Swissreg, land register where accessible, debt enforcement/bankruptcy publications |
| Contractual source | Governing law, jurisdiction/arbitration clause, order of precedence, policies, schedules, standards incorporated by reference |
| Professional/self-regulation | Bar/professional rules, SRO rules, industry codes, exchange rules, association standards |
| Doctrine/expert authority | Commentaries, treatises, textbooks, expert opinions, academic articles. Use only after official sources and regulator practice. Check edition, language and doctrinal posture. |
| Soft law / secondary | Guidance, commentary, law-firm notes, academic writing, open-access journals, research guides |
Use this hierarchy when deciding what source to rely on:
resources/doctrine-and-expert-authority-map.md.Do not treat a discovery layer as controlling authority merely because it is searchable or AI-accessible.
For each material source, record:
Flag multilingual divergence risk where wording could affect interpretation.
Always consider these flags:
Use the following output structure unless the user asks for a different format.
# Swiss Legal Source Map
## 1. Issue classification
[Classify the issue and state key assumptions.]
## 2. Likely authority layers
| Layer | Relevance | Source path to check | Status |
|---|---|---|---|
| Federal law | ... | ... | Official / primary |
| Cantonal law | ... | ... | Requires canton |
| Regulator | ... | ... | Guidance / circular / enforcement / binding rule |
## 3. Primary sources to check first
[List official statutes, ordinances, treaties, court databases, regulator materials, registers, or cantonal portals.]
## 4. Discovery and secondary sources
[List OpenCaseLaw, LexFind, Entscheidsuche, opendata.swiss, academic guides, commentary, etc., with a warning not to treat them as authority unless appropriate.]
## 5. Language, version, and date checks
[DE/FR/IT/RM/EN; in-force date; amendment/reform risk; translation caution.]
## 6. Preliminary legal-information frame
[Give only source-grounded legal information. Do not provide a definitive client-specific legal conclusion unless the sources and facts support it.]
## 7. Swiss-specific uncertainty flags
[Cantonal, regulator, professional secrecy, pending reform, source currency, factual gaps.]
## 8. Human review boundary
[Information only / lawyer review recommended / lawyer review required / authority confirmation required / regulator-specific advice required.]
## 9. Review receipt
- Sources checked:
- Sources not checked:
- Assumptions:
- Remaining gaps:
- Date of triage:
When the user needs a brief response, provide:
**Swiss source route:** [federal/cantonal/regulator/register/contractual/mixed]
**Official sources first:** [sources]
**Discovery aids:** [sources]
**Key Swiss flags:** [cantonal/language/regulator/reform/facts]
**Review boundary:** [what needs Swiss lawyer or authority review]
Do not:
Use the reference files in resources/:
swiss-legal-source-map.md — curated Swiss source list by source type.source-hierarchy.md — authority hierarchy and source-status taxonomy.doctrine-and-expert-authority-map.md — doctrine and expert-authority guidance.output-template.md — reusable Swiss source-map template.examples.md — sample outputs for common Swiss legal questions.Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take lawve-ai/swiss-legal-source-authority-triage-enrique-g-zbinden 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.