Agent skill

Swiss Legal Source Authority Triage Enrique G Zbinden

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

Swiss legal source and authority triage. An agent skill from lawve-ai/awesome-legal-skills.

MITAuto-check passedLegal & Compliance

Install Swiss Legal Source Authority Triage Enrique G Zbinden

skills CLI
$ npx skills add lawve-ai/awesome-legal-skills --skill swiss-legal-source-authority-triage-enrique-g-zbinden -a claude-code

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

GitHub CLI
$ gh skill install lawve-ai/awesome-legal-skills swiss-legal-source-authority-triage-enrique-g-zbinden --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/swiss-legal-source-and-authority-triage-enrique-g-zbinden .claude/skills/swiss-legal-source-authority-triage-enrique-g-zbinden && 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
swiss-legal-source-authority-triage-enrique-g-zbinden
GitHub stars
847
Token cost
~3.3k tokens
SKILL.md length
1,319 words
Files
8
Skills in repo
154
Repo updated
First seen
Licence
MIT

At a glance

Swiss legal source and authority triage. An agent skill from lawve-ai/awesome-legal-skills.

  • Works in 6 steps: Classify the issue → Map the authority layer → Apply the Swiss source hierarchy → …
  • A user asks a Swiss legal
  • SKILL.md covers Purpose, When to use this skill, Safety and role limits and Core principles, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Swiss Legal Source Authority Triage Enrique G Zbinden is an agent skill from lawve-ai/awesome-legal-skills. 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.

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files (for example `README.md`, `resources/doctrine-and-expert-authority-map.md` and `resources/examples.md`).

It sits in Legal & Compliance, covering Legal research, Regulatory compliance and Banking and insurance. The repository describes itself as: A curated list of awesome Agent Skills for automating legal work. The licence is MIT.

When your agent uses it

  • A user asks a Swiss legal
  • Cantonal-law question
  • Swiss law may apply
  • An AI legal answer needs source routing across federal

Example prompts

  • “/swiss-legal-source-authority-triage-enrique-g-zbinden”

Workflow steps

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

  1. Classify the issue
  2. Map the authority layer
  3. Apply the Swiss source hierarchy
  4. Verify language, version, and temporal status
  5. Identify Swiss-specific uncertainty flags
  6. Produce the answer in a safe frame

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 (its code samples are markdown).

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

  • Network

    No URLs in SKILL.md.

    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

Swiss Legal Source Authority Triage Enrique G Zbinden loads about 3.3k tokens when it runs. Until then it costs about 119 tokens; SKILL.md has 1,319 words of instructions outside code blocks.

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

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 MIT licence (© lawve-ai). 1,319 words, ~3,315 tokens.

Download SKILL.mdSave it as .claude/skills/swiss-legal-source-authority-triage-enrique-g-zbinden/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
swiss-legal-source-authority-triage-enrique-g-zbinden
description
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.
metadata.author
Enrique G. Zbinden
metadata.license
mit
metadata.version
2026-05-16

Purpose

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.

When to use this skill

Use this skill whenever:

  • The user asks a question involving Swiss law, Switzerland, a Swiss party, Swiss assets, Swiss employment, Swiss contracts, Swiss courts, Swiss regulators, Swiss companies, Swiss data protection, Swiss financial regulation, Swiss IP, Swiss tax, Swiss criminal/public law, or Swiss cantonal/municipal law.
  • The user asks whether a legal issue is federal, cantonal, communal, regulatory, contractual, professional, or mixed.
  • The user asks for Swiss legal research sources, legal-source validation, or a legal source map.
  • A contract, policy, memo, or compliance workflow claims to be governed by Swiss law.
  • The answer could be affected by official-language versions, cantonal variation, regulator practice, pending reform, or register/legal-state evidence.

Safety and role limits

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:

  • Litigation strategy, limitation periods, procedural deadlines, criminal exposure, regulatory authorisation, sanctions, employment termination, immigration, tax, financial-market authorisation, medical/health regulation, or court filings.
  • Client-specific facts that materially affect the legal outcome.
  • Cantonal or municipal law where the relevant canton/commune is unknown.
  • Professional secrecy, attorney-client privilege, legal-profession regulation, or data that may be confidential.
  • Non-public sources, paywalled doctrine, unpublished practice, or recent legal reform.

Core principles

  1. Authority before answer: first identify which Swiss source layer controls.
  2. Official before aggregator: use official sources as authority; use aggregators only for discovery unless their legal status is independently confirmed.
  3. Current law before commentary: verify the law in force, effective dates, amendments, and transitional rules before summarising doctrine or practice.
  4. Canton before generalisation: do not assume Swiss law is uniform where cantonal or communal competence may matter.
  5. Language before confidence: German, French, and Italian official versions may matter. English translations are usually informational unless an official status is established.
  6. Regulator practice is not always binding law: classify guidance, circulars, enforcement reports, FAQs, and self-regulation separately from statutes and ordinances.
  7. Doctrine is persuasive, not binding: use doctrinal sources (commentaries, treatises, textbooks, expert opinions) only after official law, case law and regulatory practice have been checked. Treat doctrine as persuasive authority. Prefer works over names, check editions and languages, and note doctrinal disagreements.
  8. Review boundary before conclusion: state where human legal judgment enters.

Triage workflow

Step 1: Classify the issue

Classify the user's request as one or more of:

  • Private law / contract / tort / property
  • Corporate / commercial register / authority to sign
  • Employment / social security / immigration-adjacent
  • Data protection / privacy / information security
  • Financial-market / AML / fintech / insurance
  • Competition / consumer / unfair competition
  • IP / technology / licensing
  • Tax / customs / trade / sanctions
  • Public law / administrative law / public procurement
  • Criminal / regulatory enforcement
  • Civil, criminal, administrative, or arbitration procedure
  • Cantonal / communal / professional-regulatory matter
  • Mixed or uncertain

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.

Step 2: Map the authority layer

Identify every layer that may control the answer:

LayerWhat to check
Federal lawFederal Constitution, federal acts, ordinances, treaties, federal official publications
Cantonal lawCantonal constitution, acts, ordinances, court organisation, administrative practice
Communal/local lawMunicipal rules, permits, zoning, police regulations, local public-law instruments
Official case lawFederal Supreme Court, Federal Administrative Court, Federal Criminal Court, Federal Patent Court, cantonal courts
Regulator practiceFINMA, FDPIC/EDÖB, COMCO/WEKO, SECO, Swissmedic, FTA/ESTV, BAKOM/OFCOM, fedpol/MROS, sector bodies
Registers/legal stateZefix, cantonal commercial registers, SHAB/SOGC, Swissreg, land register where accessible, debt enforcement/bankruptcy publications
Contractual sourceGoverning law, jurisdiction/arbitration clause, order of precedence, policies, schedules, standards incorporated by reference
Professional/self-regulationBar/professional rules, SRO rules, industry codes, exchange rules, association standards
Doctrine/expert authorityCommentaries, treatises, textbooks, expert opinions, academic articles. Use only after official sources and regulator practice. Check edition, language and doctrinal posture.
Soft law / secondaryGuidance, commentary, law-firm notes, academic writing, open-access journals, research guides
Show full SKILL.md (583 more words)Show less
Step 3: Apply the Swiss source hierarchy

Use this hierarchy when deciding what source to rely on:

  1. Official primary law: Fedlex; Official Compilation; Classified/Systematic Compilation; treaties; official cantonal and communal law portals.
  2. Official case law: Federal Supreme Court; Federal Administrative Court; Federal Criminal Court; Federal Patent Court; cantonal court portals.
  3. Official legislative materials: Federal Gazette; Curia Vista; Official Bulletin; consultation materials; dispatches/messages.
  4. Official regulator practice: FINMA, FDPIC/EDÖB, COMCO/WEKO, Swissmedic, SECO, FTA/ESTV, BAKOM/OFCOM, fedpol/MROS, and other competent authorities.
  5. Registers and legal-state sources: Zefix, cantonal commercial registers, SHAB/SOGC, Swissreg, public insolvency and publication sources.
  6. Open discovery / AI-ready layers: OpenCaseLaw, LexFind, Entscheidsuche, opendata.swiss datasets, Fedlex-JOLux, open APIs and bulk datasets.
  7. Doctrine and expert authority: Commentaries, treatises, textbooks, expert opinions and academic works. Doctrine is persuasive only. Use after official sources. See resources/doctrine-and-expert-authority-map.md.
  8. Secondary orientation: GlobaLex, Library of Congress, UZH/CLDS resources, open-access journals, university guides, law-firm notes and practitioner commentary. Useful for broad context and discovery but not authoritative.
  9. Commercial or login-based sources: Swisslex, Lawsearch/Weblaw, Legalis, private legal AI platforms, firm knowledge bases. Treat as useful but not public authority.

Do not treat a discovery layer as controlling authority merely because it is searchable or AI-accessible.

Step 4: Verify language, version, and temporal status

For each material source, record:

  • Official language version checked: DE / FR / IT / RM / EN.
  • Whether the English version is official, informational, or uncertain.
  • Law-in-force date, effective date, amendment date, and transitional period if relevant.
  • Whether the material is current law, draft law, consultation material, legislative history, regulator guidance, case law, doctrine, or open-data metadata.
  • Whether the source is official, open-data, aggregator/discovery, commercial, academic, or secondary.

Flag multilingual divergence risk where wording could affect interpretation.

Step 5: Identify Swiss-specific uncertainty flags

Always consider these flags:

  • Cantonal competence: answer may vary by canton.
  • Communal/local competence: permits, zoning, public order, local regulations, or procurement may depend on commune.
  • Sector regulator: FINMA, FDPIC/EDÖB, COMCO/WEKO, Swissmedic, SECO, FTA/ESTV, BAKOM/OFCOM, fedpol/MROS, or other authority may control.
  • Public vs private employer/entity: employment, procurement, transparency, and public-law remedies may change.
  • Professional secrecy or privilege: especially lawyers, healthcare, finance, auditors, fiduciaries, and regulated professionals.
  • Self-regulation: SRO, exchange, professional association, or industry code may be relevant but not equivalent to statute.
  • Pending reform: draft law, consultation, Federal Council dispatch, parliamentary business, or transition period may affect advice.
  • Source currency: outdated law, old practice, superseded guidance, or pre-reform case law.
  • Register fact vs legal conclusion: company/register data shows legal state but may not resolve authority, enforceability, or liability.
  • Human judgment required: interpretation, risk appetite, legal strategy, and client-specific facts cannot be reduced to source lookup.
Step 6: Produce the answer in a safe frame

Use the following output structure unless the user asks for a different format.

markdown
# 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:

Compact mode

When the user needs a brief response, provide:

markdown
**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]

Prohibited shortcuts

Do not:

  • Start with a confident legal conclusion before mapping authority.
  • Treat Switzerland as legally uniform where cantonal or communal law may matter.
  • Treat English translations as controlling without checking status.
  • Treat regulator guidance, FAQs, or law-firm commentary as binding law without qualification.
  • Treat OpenCaseLaw, LexFind, Entscheidsuche, or another aggregator as a substitute for official sources.
  • Ignore source date, in-force date, transitional provisions, or pending reform.
  • Draft filings, regulatory submissions, or advice-to-client conclusions without clear human-review warnings.

Navigation

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.

© lawve-ai, MIT. 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 7 other files in skills/swiss-legal-source-and-authority-triage-enrique-g-zbinden of lawve-ai/awesome-legal-skills.

  • SKILL.md
  • LICENSE.txt
  • README.md
  • resources/doctrine-and-expert-authority-map.md
  • resources/examples.md
  • resources/output-template.md
  • resources/source-hierarchy.md
  • resources/swiss-legal-source-map.md

Open the folder on GitHubat commit 045f738

Compare with similar skills

Swiss Legal Source Authority Triage Enrique G Zbinden 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.

Swiss Legal Source Authority Triage Enrique G Zbinden compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Swiss Legal Source Authority Triage Enrique G Zbinden this skilllawve-ai/awesome-legal-skills847—~3.3kAutomated safety check: PassMIT
Legal Article RetrievalTHUYRan/Legal-Skills-Chinese874—~20kAutomated safety check: PassNone
Legal Compliancetravisjneuman/.claude100—~3.4kAutomated safety check: PassMIT
Find Law Firmjeremylongshore/tons-of-skills-marketplace2.8k—~3.6kAutomated safety check: NotesMIT
Contract Legal Researchinfometa/workbuddyskills348—~2.1kAutomated safety check: PassNone
Legal CogaAAaqwq/AGI-Super-Team1051 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • Legal Article Retrieval

    THUYRan/Legal-Skills-Chinese

    Generate standardized legal research reports for case retrieval, statutory research, similar-case analysis, and related legal research scenarios.

    874 GitHub stars~20k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed
  • Legal Compliance

    travisjneuman/.claude

    Legal and compliance expertise for corporate governance, contract analysis, regulatory compliance (SOX, GDPR, HIPAA), risk assessment, intellectual property, and litigation management.

    100 GitHub stars~3.4k tokensUpdated yesterday
    Legal & ComplianceAuto-check passed
  • Find Law Firm

    jeremylongshore/tons-of-skills-marketplace

    A skill your agent uses whenever the user wants to find, shortlist, vet, or enrich US B2B law firms — corporate, IP/patent, M&A and securities, employment, commercial litigation…

    2.8k GitHub stars~3.6k tokensUpdated yesterday
    Legal & ComplianceAuto-check: notes
  • Contract Legal Research

    infometa/workbuddyskills

    Retrieve the legal basis and due-diligence facts that contract work depends on — supporting statutes and their effectiveness status, regulatory requirements, mandatory provisions for the contract…

    348 GitHub stars~2.1k tokensUpdated yesterday
    Legal & ComplianceAuto-check passed
  • Legal Cog

    aAAaqwq/AGI-Super-Team

    Legal demands two things: frontier-level reasoning and precision document generation.

    105 GitHub starsUsed in 1 repo~1.9k tokens
    Legal & ComplianceAuto-check passed
  • Mortgage Compliance

    davepoon/buildwithclaude

    Enforces mortgage regulatory compliance — TRID, RESPA, TILA, ECOA/Fair Lending, state licensing, required disclosures, and data privacy rules for all borrower interactions.

    3.6k GitHub stars~448 tokensUpdated 2 days ago
    Business, Finance & HRAuto-check passed

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 8 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 8 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 8 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 8 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 8 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 8 days ago
    Auto-check passed

Questions about Swiss Legal Source Authority Triage Enrique G Zbinden

What does Swiss Legal Source Authority Triage Enrique G Zbinden do?

Swiss legal source and authority triage. An agent skill from lawve-ai/awesome-legal-skills. Swiss Legal Source Authority Triage Enrique G Zbinden is an agent skill from lawve-ai/awesome-legal-skills. Swiss legal source and authority triage.

When should I use Swiss Legal Source Authority Triage Enrique G Zbinden?

Swiss Legal Source Authority Triage Enrique G Zbinden fits situations like: A user asks a Swiss legal; cantonal-law question; swiss law may apply; an AI legal answer needs source routing across federal.

How do I install Swiss Legal Source Authority Triage Enrique G Zbinden in Claude Code?

Run `npx skills add lawve-ai/awesome-legal-skills --skill swiss-legal-source-authority-triage-enrique-g-zbinden -a claude-code`. Or copy the skill folder (skills/swiss-legal-source-and-authority-triage-enrique-g-zbinden in lawve-ai/awesome-legal-skills) into .claude/skills/swiss-legal-source-authority-triage-enrique-g-zbinden in your project. Claude Code loads it when a task matches its description.

How do I install Swiss Legal Source Authority Triage Enrique G Zbinden in Codex?

Run `npx skills add lawve-ai/awesome-legal-skills --skill swiss-legal-source-authority-triage-enrique-g-zbinden -a codex`. Or copy the skill folder (skills/swiss-legal-source-and-authority-triage-enrique-g-zbinden in lawve-ai/awesome-legal-skills) into .agents/skills/swiss-legal-source-authority-triage-enrique-g-zbinden in your project. Codex loads it when a task matches its description.

Can I use Swiss Legal Source Authority Triage Enrique G Zbinden 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 swiss-legal-source-authority-triage-enrique-g-zbinden -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/swiss-legal-source-authority-triage-enrique-g-zbinden, .gemini/skills/swiss-legal-source-authority-triage-enrique-g-zbinden, .github/skills/swiss-legal-source-authority-triage-enrique-g-zbinden and .opencode/skills/swiss-legal-source-authority-triage-enrique-g-zbinden in your project.

What does Swiss Legal Source Authority Triage Enrique G Zbinden need to run?

SKILL.md names no scripts, command-line tools or credentials: Swiss Legal Source Authority Triage Enrique G Zbinden is instructions for the agent only.

Does Swiss Legal Source Authority Triage Enrique G Zbinden access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Swiss Legal Source Authority Triage Enrique G Zbinden 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 Swiss Legal Source Authority Triage Enrique G Zbinden use?

Swiss Legal Source Authority Triage Enrique G Zbinden is published under the MIT 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 Swiss Legal Source Authority Triage Enrique G Zbinden use?

About 3.3k tokens (SKILL.md is roughly 13k 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 Swiss Legal Source Authority Triage Enrique G Zbinden?

Skills that share tags, products or a category with Swiss Legal Source Authority Triage Enrique G Zbinden: Legal Article Retrieval (THUYRan/Legal-Skills-Chinese, 874 stars), Legal Compliance (travisjneuman/.claude, 100 stars), Find Law Firm (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Contract Legal Research (infometa/workbuddyskills, 348 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Swiss Legal Source Authority Triage Enrique G Zbinden?

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.