「law」の検索結果

Use when adding or editing any script under `scripts/` — `--quiet`, `_lib/script_output`, silent Taskfile wiring, Iron-Law carve-outs; fires on 'add a check script for X'.

日本語の概要は準備中です。原文の説明を表示しています。

Use when triaging an inbound NDA fast — GREEN/YELLOW/RED so only the hard ones reach a lawyer. Triggers on 'check this NDA', 'can we sign this NDA', 'is this NDA standard'.

日本語の概要は準備中です。原文の説明を表示しています。

When triaging the quick legal-question channel + intake; classifies and ROUTES, never reviews. Triggers on 'is this a legal problem', 'do we need a lawyer for this', 'quick legal question'.

日本語の概要は準備中です。原文の説明を表示しています。

文献接力（ScholarRelay）：人机协作法学／中文学术论文写作工作流。解决的核心问题是——机构订阅文献库（知网等）需经校园 webvpn 的 IP 授权才能下载，Agent 无法自行走通这条链路，而让非专业用户自建浏览器自动化又门槛过高；本工作流把链路切在授权边界上：人做检索/导出题录/下载 PDF，AI 做解析/分级/精读/写作/校验/排版。并把流程固化为十阶段协议（立项定锚→题录获取→解析分级→精读笔记→分章写作→修订体检→编号校验→投稿排版→模拟审稿→选刊投递），用脚本强制保证正文引用编号与文末参考文献一一对应、不从零编造文献页码、用版本健康度监控防止补丁式迭代把论文改烂、用机械扫描清除 AI 写作痕迹与标点问题。 Trigger when user asks for 文献接力, scholarrelay, 论文合作流程, 人机协作写论文, 文献分级, 文献精读笔记, 写作启动包, 参考文献编号校验, 编号错位, 投稿排版, 模拟审稿, 征文投稿, 知网题录解析, 期刊体例 Word, 论文修订, 车轱辘话, 越改越烂, 版本对比, 文字冗余, 摘要写作, 关键词, 去AI腔, AI写作痕迹, 选刊, 投稿策略, 投稿检查清单, 法学引注手册, CSSCI期刊.

日本語の概要は準備中です。原文の説明を表示しています。

Run a Mixture of Experts (MoE) audit on any topic, plan, codebase, evidence archive, or process. Dynamically spawns specialized subagents with different critical lenses to cross-reference findings and detect flaws, overlap, retention issues, or drift. Use when designing architectures, analyzing complex code, verifying multi-step plans, classifying evidence artifacts, or looking for duplicated intent in a repo.

日本語の概要は準備中です。原文の説明を表示しています。

中国药品权威数据库查询 — NMPA(国家药监局) + CDE(药品审评中心) + DrugBank(英文名/ATC) + PubChem(化学结构) 多源融合,提供(通用名 ↔ 商品名 ↔ 英文名 ↔ 适应症 ↔ NMPA 批文号 ↔ 上市日期)精确映射。Make sure to use this skill whenever the user mentions 药品名 / 通用名 / 商品名 / NMPA / 国药准字 / 药监局 / CDE / drug brand name / generic name / drug registry / pharmaceutical lookup / drug verification / 药物核验 / 商品名对应 / drug cross-check / drug authority lookup. 在任何 medical / market-sizing / clinical / disease-research 报告生成阶段,**所有药品提及必须先调 lookup_drug() 验证**,严禁 LLM 凭训练记忆拼凑通用名↔商品名↔英文名对应关系。LLM 训练截止后药企会更换商品名、新药持续上市,记忆完全不可信。Iron Law:lookup 返回 None → 调用方必须 raise UnverifiedDrugError,不允许 fallback 到记忆。免费公开数据源,跨平台:Claude Code / Codex / Gemini CLI 三端均可 auto-trigger,实现仅依赖 httpx + beautifulsoup4 标准生态,不绑定任何厂商 SDK。

日本語の概要は準備中です。原文の説明を表示しています。

Helm chart development agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw — chart scaffolding, values design, template patterns, dependency management, security hardening, and chart testing. Use when: user wants to create or improve Helm charts, design values.yaml files, implement template helpers, audit chart security (RBAC, network policies, pod security), manage subcharts, or run helm lint/test.

日本語の概要は準備中です。原文の説明を表示しています。

Pre-breach impact analysis: inventories sensitive data (PII, PHI, PCI-DSS, credentials), traces data flows, scores exposure vectors, and produces a regulatory blast radius report with fine ranges sourced verbatim from GDPR Art. 83, CCPA § 1798.155(a), and HIPAA 45 CFR § 160.404. Cost benchmarks from IBM Cost of a Data Breach Report (annually updated). All citations in references/SOURCES.md for verification. Use when asked: "assess breach impact", "what data could be exposed", "calculate blast radius", "data exposure analysis", "how bad would a breach be", "quantify data risk", "sensitive data inventory", "data flow security audit", "pre-breach assessment", "worst-case breach scenario", "breach readiness", "data risk report", "/data-breach-blast-radius". For any stack handling user data, health records, or financial information. Output labels law-sourced figures (exact) vs heuristic estimates (planning only). Does not replace legal counsel.

日本語の概要は準備中です。原文の説明を表示しています。

AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.

日本語の概要は準備中です。原文の説明を表示しています。

SOP for auditing AI-generated code. Trigger when: - Reviewing, refactoring, or cleaning up AI-generated code to prevent regressions or hallucinated APIs. - Prompt contains: /ai-audit, code audit, AI cleanup, common flaws.

日本語の概要は準備中です。原文の説明を表示しています。

Foundational ethics, authority hierarchy, and structural principles for the Predicate agent. Always-on law (composable system-prompt core): Truth>Harmony, Evidence>Authority, Halt>Assumption, Outcomes>Process — four ordered principles that govern every walk. Reference (by-moment): conflict resolution, ethics adjudication, novel situations, precedence walkthrough, entropy diagnostics, principled resistance. Trigger (reference depth): resolving rule conflicts, ethics calls, novel situations. Prompt contains: constitution, principles, precedence, truth over harmony, outcomes over process, evidence over authority, principled resistance.

日本語の概要は準備中です。原文の説明を表示しています。

The LAW a council SEAT is bound by — deliberation protocol, pact obligations, governance, and decision-ledger recording — the discipline half of a seat. Trigger when: - Holding a seat on a bound council (architect, lead-maintainer, process-auditor, or a summoned guest). - Depositing an independent assessment, routing a decision, or recording assent or a finding. - Auditing whether the council honored the pact, the delegation table, or the barring lifecycle. - Prompt contains: /council, council seat, deliberation protocol, pact, delegation table, decision ledger, barring, merge-consent.

日本語の概要は準備中です。原文の説明を表示しています。

Adversarially probe this monorepo for security flaws at the right depth. Steers the red-team subagent — picks quick/standard/deep from the request, spawns it (fanning out for a wide deep sweep), collates findings into a dated report, and files security/sec:* issues for confirmed high/critical findings. Use when asked to "red-team", "try to hack this", "find security holes", "pentest this package/app", or as the brain behind the CI + daily security runs.

日本語の概要は準備中です。原文の説明を表示しています。

The case-law chronicle of this repo's major failures — symptom, root cause, evidence, status, and the rule each battle minted — so nobody re-fights a settled battle or re-proposes a rejected fix. Use when a bug/incident looks familiar ("didn't this happen before?"), when you're about to propose an approach that may have been tried and rejected (e.g. shipping a migration from a package), when someone asks "why does rule X exist" / "why is done-by-lgtm a thing" / "what was incident 988", or when a bug-archaeology run hits the shallow-clone wall and needs the pre-June-2026 history. Trigger phrases: "has this broken before", "why can't packages ship migrations", "why did graduation fail", "why is the green-build lesson a rule", "what did we learn from incident NN". (For a live "build is green but the app is broken" symptom, start at crouton-diagnostics-index. NB keep this description free of any space-then-hash sequence — an unquoted YAML scalar treats space-hash as a comment start and silently truncates.)

日本語の概要は準備中です。原文の説明を表示しています。

Get structured data from catalogued providers instead of scraping pages. Firecrawl Alexandria is a library of official APIs, licensed publishers, and Firecrawl indexes (financial series, company data, government contracts and law, podcasts, listings, research). Use this skill when the user needs records, listings, prices, filings, transcripts, or a dataset, says "is there an API for", "find a data source for", "pull the records", "get the dataset", or when assembling the answer by scraping would take many pages that one provider call returns directly. Discover with search, inspect with find_tools, execute with scrape.

日本語の概要は準備中です。原文の説明を表示しています。

Add Telegram as a channel. Can replace WhatsApp entirely or run alongside it. Also configurable as a control-only channel (triggers actions) or passive channel (receives notifications only).

日本語の概要は準備中です。原文の説明を表示しています。

Format messages for Slack using mrkdwn syntax. Use when responding to Slack channels (folder starts with "slack_" or JID contains slack identifiers).

日本語の概要は準備中です。原文の説明を表示しています。

Switch from Docker to Apple Container for macOS-native container isolation. Use when the user wants Apple Container instead of Docker, or is setting up on macOS and prefers the native runtime. Triggers on "apple container", "convert to apple container", "switch to apple container", or "use apple container".

日本語の概要は準備中です。原文の説明を表示しています。

Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)

日本語の概要は準備中です。原文の説明を表示しています。

Add Ollama MCP server so the container agent can call local models and optionally manage the Ollama model library.

日本語の概要は準備中です。原文の説明を表示しています。

Add WhatsApp emoji reaction support — receive, send, store, and search reactions.

日本語の概要は準備中です。原文の説明を表示しています。

Add WhatsApp as a channel. Can replace other channels entirely or run alongside them. Uses QR code or pairing code for authentication.

日本語の概要は準備中です。原文の説明を表示しています。

Add /compact command for manual context compaction. Solves context rot in long sessions by forwarding the SDK's built-in /compact slash command. Main-group or trusted sender only.

日本語の概要は準備中です。原文の説明を表示しています。

Loads org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification follows team standards. Use before any code generation or modification task when rules are not already loaded. Invoke when user asks to write, edit, refactor, or review code, or when starting implementation planning.

日本語の概要は準備中です。原文の説明を表示しています。