Explore skills
Showing 26101–26130 of 32736 skills
BC Legislation Administrator and Legal Statutory Analyst. Locate, verify, download, print, organize, and analyze British Columbia statutes, regulations, and rules ONLY from the official BC Laws portal (bclaws.gov.bc.ca). Never print legislation from CanLII or other third-party sites. Currency verification, historical vs current versions, court-ready extracts, BOA tabs, statutory analysis. Triggers: BC Laws, print statute, legislative extract, Book of Authorities legislation, verify RTA section, official legislation, JRPA, currency of the Act, point-in-time legislation.
ThomasMoreAI/legal-skills-open
Stars: 136Claude CodeCodexThe Civil Code of Québec (CCQ, in force 1 January 1994, replacing the 1866 Civil Code of Lower Canada) — Quebec's civil-law jus commune and the foundation of its private law. A navigation-and-orientation reference verified against the official consolidated text on LégisQuébec (retrieved 2026-07). Covers: what the Code is and the Preliminary Provision that makes it the general law of Québec, operating in harmony with the Charter of human rights and freedoms and serving as the foundation of all other laws; why Quebec is a CIVIL-LAW jurisdiction and how that differs from the common law of the other provinces (codified general principles reasoned deductively rather than binding precedent/stare decisis, no equity/trusts-by-tradition, different vocabulary); the map of all ten Books with article ranges — One Persons (1-364), Two The Family (365-612, incl. family patrimony), Three Successions (613-898), Four Property (898.1-1370, opening with 'animals are not things'), Five Obligations (1371-2643, the largest — contract formation, civil liability, and the nominate contracts incl. sale, lease at 1851-1978, employment, mandate, insurance), Six Prior Claims and Hypothecs (2644-2802), Seven Evidence (2803-2874.1), Eight Prescription (2875-2933, incl. the 3-year personal action and 10-year judgment rules), Nine Publication of Rights (2934-3075.1, the land register and RDPRM), Ten Private International Law (3076-3168); the Book/Title/Chapter/Section/Division hierarchy and why division scope matters; how to read an article's legislative history (1991, c. 64 enactment, amendments, and decimal numbers signalling later insertions); the equally-authoritative French and English versions; public order vs suppletive rules; and common cross-Book chains for real problems. Use to find where a Quebec legal topic lives in the Code, decode an article citation, understand the civil-law approach, or orient before researching on LégisQuébec/CanLII.
ThomasMoreAI/legal-skills-open
Stars: 136Claude CodeCodexThe Criminal Code of Canada (R.S.C. 1985, c. C-46) as a navigable map — how the statute is organized and how to find things in it. Built by parsing the official consolidated text (laws-lois.justice.gc.ca, current to 2026-05-26), with Part ranges extracted programmatically from the body and cross-checked against the TOC. Covers: the full Part structure I–XXVIII with section ranges (the substantive Parts I–XIII vs the procedural/sentencing Parts XIV–XXVIII), and why decimal Parts and sections are insertions so section numbers cannot be arithmetic (320.4 comes after 320.104); the CLASSIFICATION system that drives everything — indictable vs summary vs hybrid, where 'hybrid' appears zero times in the Code and is expressed structurally as 'indictable … or … punishable on summary conviction' (345 occurrences), the s. 787 default summary penalty ($5,000 / two years less a day, the penitentiary-vs-jail line), and the s. 786(2) 12-month limitation that applies only to summary proceedings, can be waived by agreement, and has no indictable counterpart; general principles (s. 2 definitions, the s. 8(3) preservation of common-law defences against s. 9's bar on common-law offences, parties s. 21, counselling s. 22, accessory s. 23, attempts s. 24 where factual impossibility is no defence and the preparation line is a question of law); defences (self-defence s. 34 and its nine factors, defence of property s. 35, duress s. 17 whose 'immediate'/'present' words were struck in Ruzic but still print, necessity as pure common law, provocation s. 232 as a partial defence narrowed in 2015, mental disorder s. 16 and NCRMD, extreme intoxication s. 33.1 rewritten after Brown); where offences live (assault 265 and why sexual assault 271 has no separate definition, theft 322/334, break and enter 348, fraud 380, mischief 430 incl. computer data); procedure (the s. 493.1 release principle, s. 515 bail and its three grounds, the s. 535 preliminary inquiry narrowed to 14+ years on request, the s.
ThomasMoreAI/legal-skills-open
Stars: 136Claude CodeCodexGuides compliance with Canada's Personal Information Protection and Electronic Documents Act (PIPEDA, S.C. 2000, c. 5). Covers the 10 fair information principles in Schedule 1, consent requirements, cross-border transfer obligations, breach notification under Division 1.1, and OPC enforcement. Keywords: PIPEDA, Canada privacy, fair information principles, OPC, breach notification, cross-border transfer, consent.
ThomasMoreAI/legal-skills-open
Stars: 136Claude CodeCodexBuild and navigate workplace accommodation requests (disability, religious, medical)
ThomasMoreAI/legal-skills-open
Stars: 136Claude CodeCodexAssess whether workplace conditions constitute constructive dismissal
ThomasMoreAI/legal-skills-open
Stars: 136Claude CodeCodexAssess potential discrimination patterns and document protected class treatment disparities
ThomasMoreAI/legal-skills-open
Stars: 136Claude CodeCodexPrepare for workplace HR or third-party investigations
ThomasMoreAI/legal-skills-open
Stars: 136Claude CodeCodexAnalyze severance packages and termination agreements for fairness and negotiation opportunities
ThomasMoreAI/legal-skills-open
Stars: 136Claude CodeCodexBuild organized documentation of workplace incidents and issues
ThomasMoreAI/legal-skills-open
Stars: 136Claude CodeCodexUse this whenever you need to know what is actually in a database, warehouse, or DuckDB file before you trust it: inventory, column profiles, PII detection, grain and data-quality problems, verified joins, ER diagrams, ad-hoc SQL probes, segmentation, and the semantic layer a repo declares (dbt, Ossie, SLayer, or Cube). Trigger it on an unmet precondition, not on phrasing: if you are about to write or fix SQL against tables whose columns, types, grain, or join keys you have not verified in this session, use this FIRST. That includes dbt work (building a model, fixing one, debugging wrong numbers) whenever the ticket names source tables without spelling out their schema. It applies mid-task too: on reaching a table you have not inspected, stop and use this rather than guess column names. Also for "what's in my duckdb", "is this data any good", "how do these tables relate". Read-only; writes only the .dex/ cache. It does not author the model: transform does, and maintain reconciles a project that has drifted.
exmergo/dex
Stars: 136Claude CodeCodexUse this to find out whether an existing dbt project or semantic layer (dbt, Ossie, SLayer or Cube) is correct against its warehouse, and if not, why. `maintain verify` checks the project as it stands; against a .dex/ snapshot, `maintain check` finds schema, volume, grain, and semantic drift and `maintain reconcile` proposes the fix. Reach for it whenever an existing project is suspected wrong, whether or not anything is known to have changed: "this model is wrong, work out why", "the numbers look too high", "some rows are missing", "this column is empty", "duplicates in my fact table", "the project is broken", "diagnose why this test fails", "a test fails and nobody changed the model", "which models have no tests", "how good is our test coverage", "did anything drift", "the metric definition changed". Read-only; fixes come back as reviewable diffs and never overwrite hand-written work. Writing the fix, or repairing a model you just edited, is transform's; a data question with no project is explore's.
exmergo/dex
Stars: 136Claude CodeCodexUse this to author and change a dbt project or a semantic layer: bootstrap a project (`transform init`), write or refactor models from staging to marts, add tests and docs, and define semantic models, entities, dimensions, and metrics in MetricFlow, Apache Ossie or SLayer YAML. Reach for it instead of editing model files by hand whenever a change spans more than one file or must stay consistent with the project: it validates the edit against the real schema, returns a reviewable diff with a plan id, and catches what otherwise fails at `dbt run`, such as wrong columns or broken refs. Bug-fix tickets count: "this model returns wrong numbers, fix it" is a transform task. Also for "build a staging model for this table", "define a revenue metric", "add a dimension to this entity". Warehouse builds are dev-target only, gated, and cost-surfaced first. If you have not verified the source tables' columns or grain, use explore first. For a project that drifted from the warehouse, use maintain.
exmergo/dex
Stars: 136Claude CodeCodexUse this whenever you need to know what is actually in a database, warehouse, or DuckDB file before you trust it: inventory, column profiles, PII detection, grain and data-quality problems, verified joins, ER diagrams, ad-hoc SQL probes, segmentation, and the semantic layer a repo declares (dbt, Ossie, SLayer, or Cube). Trigger it on an unmet precondition, not on phrasing: if you are about to write or fix SQL against tables whose columns, types, grain, or join keys you have not verified in this session, use this FIRST. That includes dbt work (building a model, fixing one, debugging wrong numbers) whenever the ticket names source tables without spelling out their schema. It applies mid-task too: on reaching a table you have not inspected, stop and use this rather than guess column names. Also for "what's in my duckdb", "is this data any good", "how do these tables relate". Read-only; writes only the .dex/ cache. It does not author the model: transform does, and maintain reconciles a project that has drifted.
exmergo/dex
Stars: 136Claude CodeCodexUse this to find out whether an existing dbt project or semantic layer (dbt, Ossie, SLayer or Cube) is correct against its warehouse, and if not, why. `maintain verify` checks the project as it stands; against a .dex/ snapshot, `maintain check` finds schema, volume, grain, and semantic drift and `maintain reconcile` proposes the fix. Reach for it whenever an existing project is suspected wrong, whether or not anything is known to have changed: "this model is wrong, work out why", "the numbers look too high", "some rows are missing", "this column is empty", "duplicates in my fact table", "the project is broken", "diagnose why this test fails", "a test fails and nobody changed the model", "which models have no tests", "how good is our test coverage", "did anything drift", "the metric definition changed". Read-only; fixes come back as reviewable diffs and never overwrite hand-written work. Writing the fix, or repairing a model you just edited, is transform's; a data question with no project is explore's.
exmergo/dex
Stars: 136Claude CodeCodexUse this to author and change a dbt project or a semantic layer: bootstrap a project (`transform init`), write or refactor models from staging to marts, add tests and docs, and define semantic models, entities, dimensions, and metrics in MetricFlow, Apache Ossie or SLayer YAML. Reach for it instead of editing model files by hand whenever a change spans more than one file or must stay consistent with the project: it validates the edit against the real schema, returns a reviewable diff with a plan id, and catches what otherwise fails at `dbt run`, such as wrong columns or broken refs. Bug-fix tickets count: "this model returns wrong numbers, fix it" is a transform task. Also for "build a staging model for this table", "define a revenue metric", "add a dimension to this entity". Warehouse builds are dev-target only, gated, and cost-surfaced first. If you have not verified the source tables' columns or grain, use explore first. For a project that drifted from the warehouse, use maintain.
exmergo/dex
Stars: 136Claude CodeCodexOpen Analytics' design language, extracted from the shipped product: an ink-derived neutral system, squircle surface anatomy, one small spring vocabulary, pixel-matched skeletons, and a plain-spoken copy voice, with type-checked component recipes. Use this whenever you build or restyle a dashboard, SaaS app, analytics UI, settings screen, onboarding flow, or marketing/landing page that should feel calm, dense and native, and whenever the user mentions Open Analytics' look, 'clean SaaS design', cards, dropdowns, tab bars, empty states, skeletons, or UI animation quality, even if they never say the words 'design system'.
OpenLabs-so/oa-design
Stars: 135Claude CodeCodexOperate ArvanCloud (arvancloud.ir) through its REST APIs, including CDN and DNS records, domains, cache purge, WAF and rate limits, Cloud Server (IaaS v3, v1 and the undocumented v2 backups), Object Storage, Edge Computing, Cloud Container, VOD, Live and Video Ads, plus Let's Encrypt DNS-01 certificates via acme.sh dns_arvan. Use when the user wants to list, create, change or delete anything on ArvanCloud, take an account inventory, find out which account a key belongs to, check quota or usage, or debug an ArvanCloud API error. Also trigger on hosts like napi.arvancloud.ir, ecc.{region}.arvanapis.ir, storage.arvanapis.ir, dejban.arvancloud.ir, an "Apikey" Authorization header, the dns_arvan plugin, or one of the user's ArvanCloud-hosted domains.
erfnzdeh/arvancloud-agent-skill
Stars: 135Claude CodeCodex麦麦省钱助手——基于麦当劳中国官方 MCP Server 的省钱点餐技能。当用户提到麦当劳、麦乐送、麦麦、点麦当劳、想省钱/薅羊毛/领券/优惠、查优惠怎么用、积分兑换、麦麦商城、积分抽奖、麦当劳活动,或询问"怎么点麦当劳最划算"时使用本技能。核心能力:在下单前自动完成"领券→选券→比价→积分抵扣评估",用 35 个官方工具帮用户以最低价格吃到同样的麦当劳。
yuxinlaile/McD-saver
Stars: 134Claude CodeCodexAutonomous GDPR compliance auditor that scans a codebase to identify PII collection, storage, and sharing, then produces an article-by-article gap analysis, a pre-filled Data Processing Agreement (DPA), and a ROPA (Record of Processing Activities) starter kit — all exported as downloadable files (.docx recommended). Use this skill whenever the user mentions GDPR, data privacy audit, DPA, ROPA, EU compliance, PII scan, data protection, ICO, CNIL, or asks whether their codebase or product is compliant with data protection law. Trigger even for casual phrasings like "are we GDPR compliant?", "I need to check our data privacy", or "help me get audit-ready." The skill runs autonomously — it reads the codebase, researches third-party processors, and produces final deliverables without the user needing to provide structured input.
goSprinto/compliance-skills
Stars: 134Claude CodeCodexProactive PII add-on — augments the main response with PII guidance. Auto-trigger on any form, schema, migration, model, API route, GraphQL resolver, auth flow, or data design discussion. Also fires on: middleware, webhooks, workers, seed/fixture/factory files, delete/export/purge/anonymize functions, cron jobs, HTTP clients, controllers, services, resolvers. Trigger phrases: "build a form", "collect X data", "what fields should I include", "how should I design the schema", "POC / lead / contact / user / customer information", "store / save / persist X", "sign up / login / auth / registration", "share thoughts on how to build". Trigger on field names: email, phone, name, dob, ssn, card, cvv, password, token, secret, api_key, health, biometric, ip_address, salary, session, device_id, notes, metadata (on user-facing models).
goSprinto/compliance-skills
Stars: 134Claude CodeCodexara-mkr/Wonder-Pill
Stars: 134Claude CodeCodexara-mkr/Wonder-Pill
Stars: 134Claude CodeCodexWork from the same local memory as every other coding agent on this machine. Recall prior decisions, preferences, instructions, and project conventions that Claude Code, Codex, Cursor, and other agents wrote here, with cited sources, fully local. Also searches a separate local technical-documentation index.
docmancer/docmancer
Stars: 133Claude CodeCodexSet up machine-wide memory and open the local project workbench.
docmancer/docmancer
Stars: 133Claude CodeCodexRecall source-attributed local memory before work.
docmancer/docmancer
Stars: 133Claude CodeCodexInspect Docmancer tree, index, capture, and security health.
docmancer/docmancer
Stars: 133Claude CodeCodexDeliberately write or revise one complete curated memory file.
docmancer/docmancer
Stars: 133Claude CodeCodexRecall and write source-attributed local memory.
docmancer/docmancer
Stars: 133Claude CodeCodexWrite deliberate source-attributed local memory.
docmancer/docmancer
Stars: 133Claude CodeCodex