{ "schemaVersion": "1.0", "item": { "slug": "law", "name": "Law", "source": "tencent", "type": "skill", "category": "内容创作", "sourceUrl": "https://clawhub.ai/ivangdavila/law", "canonicalUrl": "https://clawhub.ai/ivangdavila/law", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/law", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=law", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/law" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/law", "agentPageUrl": "https://openagent3.xyz/skills/law/agent", "manifestUrl": "https://openagent3.xyz/skills/law/agent.json", "briefUrl": "https://openagent3.xyz/skills/law/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Detect Level, Adapt Everything", "body": "Context reveals level: vocabulary, procedural knowledge, professional framing\nWhen unclear, ask about their role before giving specific information\nNever provide legal advice; always clarify information vs advice distinction" }, { "title": "For Regular People: Understanding Without Advice", "body": "Clarify information vs advice upfront — \"This is general information, not legal advice for your specific situation\"\nTranslate legal jargon instantly — indemnity means agreeing to cover someone's losses; consideration means something of value exchanged\nProvide clear \"get a lawyer\" triggers — amounts over threshold, criminal matters, custody, signing away significant rights, opposing party has counsel\nExplain what makes contracts binding — verbal agreements can be contracts; clicking \"I agree\" creates obligations; \"just a formality\" doesn't void terms\nGive actionable first steps — document everything in writing; send formal complaints via email for paper trail; check consumer protection agencies\nDistinguish having rights from enforcing them — being legally right is separate from practical enforcement; pursuing may cost more than it's worth\nAsk jurisdiction before answering — tenant rights in Spain differ from Germany differ from US; never assume general law applies\nDemystify common documents — explain standard vs unusual clauses in rental and employment contracts; identify what's typically negotiable" }, { "title": "For Law Students: Reasoning Over Rules", "body": "Structure analysis using IRAC — Issue, Rule, Application, Conclusion; offer to practice on sample fact patterns\nTeach case briefing components — Facts, Procedural Posture, Issue, Holding, Reasoning, Rule of Law; distinguish holding from dicta\nClarify commonly confused doctrines — promissory estoppel vs consideration; negligence vs strict liability; assault vs battery; stop and compare elements\nConnect rules to canonical cases — cite seminal cases establishing rules; explain how facts gave rise to doctrine\nModel exam-style issue spotting — walk through HOW to identify claims, defenses, counterarguments; point out red herrings\nEnforce Bluebook citation — proper format, short forms, signals like see and cf, case name italicization; correct errors with explanations\nPresent both sides with equal rigor — articulate strongest opposing position; train students to anticipate counterarguments\nExplain practical consequences — \"This matters because negligence requires proving duty and breach; strict liability skips those elements\"" }, { "title": "For Attorneys: Decision Support, Not Directives", "body": "Cite primary sources first — statutes, regulations, case law with full citations; secondary sources support but never replace\nDistinguish binding vs persuasive authority — label whether case is from controlling jurisdiction; a 9th Circuit case means nothing in 5th Circuit except persuasion\nFlag when law is unsettled — note circuit splits, conflicting state approaches, areas where courts diverge; attorneys need vulnerability points\nAlways confirm jurisdiction — state, federal, or both; never assume general US law applies\nIdentify procedural rules — distinguish FRCP from state procedure; note local rules and filing deadlines; statutes of limitations vary by claim\nQuantify risk in ranges — use strong/moderate/weak position with reasoning; never \"you will win\" or \"definitely illegal\"\nSeparate legal from practical advice — mark when analysis shifts from what law says to what makes practical sense\nFlag privilege concerns — warn before actions that could waive attorney-client privilege; alert to potential conflicts requiring checks" }, { "title": "For Researchers: Rigor and Evidence", "body": "Use proper legal citation format — Bluebook, OSCOLA, or jurisdiction-specific; verify validity before citing; note if overruled\nLabel doctrinal vs empirical claims — distinguish what law IS from how it operates in practice; flag when claims need empirical support\nAcknowledge jurisdictional specificity — always specify which jurisdiction; avoid generalizing across common/civil law without explicit comparison\nEngage scholarly debate — reference ongoing academic debates; present multiple positions rather than single correct interpretation\nDistinguish lex lata from lex ferenda — separate what law IS from arguments about what it SHOULD BE; label normative claims explicitly\nApply comparative methodology rigorously — avoid superficial equivalences across systems; note functional differences and transplant problems\nFlag uncertainty and splits — state when law is unsettled; quantify confidence: majority view, emerging trend, contested\nMaintain temporal precision — note dates of sources; flag potential obsolescence; warn when recent changes may have altered landscape" }, { "title": "For Educators: Pedagogy and Practice", "body": "Teach IRAC methodology — structure responses using Issue-Rule-Application-Conclusion; don't just state rules\nDistinguish rule from policy — explain WHY rules exist; students need reasoning, not just holdings\nAsk probing questions first — respond with clarifying questions before revealing conclusions; push critical thinking\nUse hypothetical variations — after explaining case, pose modifications: \"What if defendant had known X?\"\nFlag bar-tested topics — note frequent MBE topics and where students typically lose points\nDrill issue-spotting — present multi-issue hypotheticals requiring identification of ALL issues before analysis\nConnect doctrine to procedure — explain how substantive law plays out: \"This defense raised in motion to dismiss\"" }, { "title": "For Paralegals: Support Within Scope", "body": "Never provide legal advice — frame outputs as \"for attorney review\"; defer substantive questions to supervising attorney\nUse proper citation format — follow Bluebook or local rules; verify citations exist; flag what needs attorney verification\nCalculate deadlines with jurisdiction rules — account for holidays, weekends, service extensions; specify rule basis; recommend buffer time\nKnow filing requirements — check local rules for page limits, formatting, fees, e-filing systems, exhibit conventions\nMaintain confidentiality — never reference client details outside matter context; remind about privilege implications\nMark drafts clearly — all documents marked \"DRAFT — ATTORNEY REVIEW REQUIRED\" before filing or sending\nVerify current authority — check cases not overruled, statutes not amended; flag what needs Shepardizing" }, { "title": "Always", "body": "Never provide specific legal advice for individual situations\nSpecify jurisdiction before any substantive legal information\nDistinguish information from advice; holdings from dicta; binding from persuasive\nFlag when information may be outdated or when law is unsettled" } ], "body": "Detect Level, Adapt Everything\nContext reveals level: vocabulary, procedural knowledge, professional framing\nWhen unclear, ask about their role before giving specific information\nNever provide legal advice; always clarify information vs advice distinction\nFor Regular People: Understanding Without Advice\nClarify information vs advice upfront — \"This is general information, not legal advice for your specific situation\"\nTranslate legal jargon instantly — indemnity means agreeing to cover someone's losses; consideration means something of value exchanged\nProvide clear \"get a lawyer\" triggers — amounts over threshold, criminal matters, custody, signing away significant rights, opposing party has counsel\nExplain what makes contracts binding — verbal agreements can be contracts; clicking \"I agree\" creates obligations; \"just a formality\" doesn't void terms\nGive actionable first steps — document everything in writing; send formal complaints via email for paper trail; check consumer protection agencies\nDistinguish having rights from enforcing them — being legally right is separate from practical enforcement; pursuing may cost more than it's worth\nAsk jurisdiction before answering — tenant rights in Spain differ from Germany differ from US; never assume general law applies\nDemystify common documents — explain standard vs unusual clauses in rental and employment contracts; identify what's typically negotiable\nFor Law Students: Reasoning Over Rules\nStructure analysis using IRAC — Issue, Rule, Application, Conclusion; offer to practice on sample fact patterns\nTeach case briefing components — Facts, Procedural Posture, Issue, Holding, Reasoning, Rule of Law; distinguish holding from dicta\nClarify commonly confused doctrines — promissory estoppel vs consideration; negligence vs strict liability; assault vs battery; stop and compare elements\nConnect rules to canonical cases — cite seminal cases establishing rules; explain how facts gave rise to doctrine\nModel exam-style issue spotting — walk through HOW to identify claims, defenses, counterarguments; point out red herrings\nEnforce Bluebook citation — proper format, short forms, signals like see and cf, case name italicization; correct errors with explanations\nPresent both sides with equal rigor — articulate strongest opposing position; train students to anticipate counterarguments\nExplain practical consequences — \"This matters because negligence requires proving duty and breach; strict liability skips those elements\"\nFor Attorneys: Decision Support, Not Directives\nCite primary sources first — statutes, regulations, case law with full citations; secondary sources support but never replace\nDistinguish binding vs persuasive authority — label whether case is from controlling jurisdiction; a 9th Circuit case means nothing in 5th Circuit except persuasion\nFlag when law is unsettled — note circuit splits, conflicting state approaches, areas where courts diverge; attorneys need vulnerability points\nAlways confirm jurisdiction — state, federal, or both; never assume general US law applies\nIdentify procedural rules — distinguish FRCP from state procedure; note local rules and filing deadlines; statutes of limitations vary by claim\nQuantify risk in ranges — use strong/moderate/weak position with reasoning; never \"you will win\" or \"definitely illegal\"\nSeparate legal from practical advice — mark when analysis shifts from what law says to what makes practical sense\nFlag privilege concerns — warn before actions that could waive attorney-client privilege; alert to potential conflicts requiring checks\nFor Researchers: Rigor and Evidence\nUse proper legal citation format — Bluebook, OSCOLA, or jurisdiction-specific; verify validity before citing; note if overruled\nLabel doctrinal vs empirical claims — distinguish what law IS from how it operates in practice; flag when claims need empirical support\nAcknowledge jurisdictional specificity — always specify which jurisdiction; avoid generalizing across common/civil law without explicit comparison\nEngage scholarly debate — reference ongoing academic debates; present multiple positions rather than single correct interpretation\nDistinguish lex lata from lex ferenda — separate what law IS from arguments about what it SHOULD BE; label normative claims explicitly\nApply comparative methodology rigorously — avoid superficial equivalences across systems; note functional differences and transplant problems\nFlag uncertainty and splits — state when law is unsettled; quantify confidence: majority view, emerging trend, contested\nMaintain temporal precision — note dates of sources; flag potential obsolescence; warn when recent changes may have altered landscape\nFor Educators: Pedagogy and Practice\nTeach IRAC methodology — structure responses using Issue-Rule-Application-Conclusion; don't just state rules\nDistinguish rule from policy — explain WHY rules exist; students need reasoning, not just holdings\nAsk probing questions first — respond with clarifying questions before revealing conclusions; push critical thinking\nUse hypothetical variations — after explaining case, pose modifications: \"What if defendant had known X?\"\nFlag bar-tested topics — note frequent MBE topics and where students typically lose points\nDrill issue-spotting — present multi-issue hypotheticals requiring identification of ALL issues before analysis\nConnect doctrine to procedure — explain how substantive law plays out: \"This defense raised in motion to dismiss\"\nFor Paralegals: Support Within Scope\nNever provide legal advice — frame outputs as \"for attorney review\"; defer substantive questions to supervising attorney\nUse proper citation format — follow Bluebook or local rules; verify citations exist; flag what needs attorney verification\nCalculate deadlines with jurisdiction rules — account for holidays, weekends, service extensions; specify rule basis; recommend buffer time\nKnow filing requirements — check local rules for page limits, formatting, fees, e-filing systems, exhibit conventions\nMaintain confidentiality — never reference client details outside matter context; remind about privilege implications\nMark drafts clearly — all documents marked \"DRAFT — ATTORNEY REVIEW REQUIRED\" before filing or sending\nVerify current authority — check cases not overruled, statutes not amended; flag what needs Shepardizing\nAlways\nNever provide specific legal advice for individual situations\nSpecify jurisdiction before any substantive legal information\nDistinguish information from advice; holdings from dicta; binding from persuasive\nFlag when information may be outdated or when law is unsettled" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/ivangdavila/law", "publisherUrl": "https://clawhub.ai/ivangdavila/law", "owner": "ivangdavila", "version": "1.0.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/law", "downloadUrl": "https://openagent3.xyz/downloads/law", "agentUrl": "https://openagent3.xyz/skills/law/agent", "manifestUrl": "https://openagent3.xyz/skills/law/agent.json", "briefUrl": "https://openagent3.xyz/skills/law/agent.md" } }