一键在 Manus 中运行任何 Skill

regulatory-citer

星标0

分支0

更新时间2026年5月31日 22:48

Activate whenever regulatory text appears in code, prompts, or docs. Guides precise citation of US healthcare regulatory sources.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

mlbrilliance

mlbrilliance/cascadecare-network-command

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Regulatory Citation Guide

Purpose

Ensure all regulatory citations in code, agent prompts, documentation, and UI text are precise and verifiable. Never fabricate case numbers, settlement amounts, or enforcement actions.

When to Activate

Writing agent prompts that reference regulations
Creating synthetic regulatory communications
Building mock regulator responses
Writing documentation that mentions compliance frameworks

Citable Regulatory Sources

HIPAA (Health Insurance Portability and Accountability Act)

Privacy Rule: 45 CFR Part 160 and Subparts A, E of Part 164
Security Rule: 45 CFR Part 160 and Subparts A, C of Part 164
Breach Notification Rule: 45 CFR Part 164 Subpart D (sections 164.400-414)
Business Associate provisions: 45 CFR 164.502(e), 164.504(e)
Enforcement: 45 CFR Part 160 Subparts C, D, E

No Surprises Act / IDR

NSA IDR process: 45 CFR Part 149 (specifically 149.510-149.520)
Federal IDR portal and process rules
State IDR variations where applicable

SEC Disclosure

SEC Item 1.05 (Form 8-K): Material cybersecurity incidents
SEC Regulation S-K Item 106: Cybersecurity risk management

False Claims Act

FCA Civil Cyber-Fraud Initiative (DOJ)
31 U.S.C. sections 3729-3733

State Insurance Codes

State DOI authority: cite as "[State] Insurance Code section [X]" — use fictional state code sections
NAIC Model Laws: cite by model number, not state-specific adoption

Anti-patterns

NEVER fabricate case numbers (e.g., "In re ClearFlow Health, Case No. 24-cv-1234")
NEVER cite specific settlement amounts as if they are real ("$XX million settlement")
NEVER cite real enforcement actions against real companies
NEVER present regulatory analysis as legal advice — always label as "decision-support draft"
When uncertain about a citation, use the general statute reference (e.g., "45 CFR 164.400-414") rather than inventing a specific subsection

同仓库更多 Skills

同仓库

maestro-case-kit

mlbrilliance/cascadecare-network-command

Offline, credential-free knowledge + static validators for UiPath Maestro Case footguns. Explain cryptic error codes (400300, 160009, ...) and lint caseplans, spawn inputs, and Data Fabric specs in CI — no UiPath login. Use when authoring, debugging, or reviewing UiPath Maestro Case / Data Fabric / Action Center work.

2026-06-160

polyskill

mlbrilliance/cascadecare-network-command

Cross-runtime skill optimizer. Use this skill when the user wants to package an Agent Skill so it runs in both Claude Code and OpenAI Codex from a single portable source. Also use when the user wants to import an existing skill (Claude Code or Codex) into the portable format, build/emit for any runtime, install a skill into Claude Code or Codex, or troubleshoot why a skill behaves differently across runtimes.

2026-05-310

polyskill

mlbrilliance/cascadecare-network-command

Use when the user wants to package a skill so it runs in both Claude Code and Codex from one source, import an existing skill into the portable format, install to Claude or Codex, or troubleshoot cross-runtime drift.

2026-05-310

agent-endurance

mlbrilliance/cascadecare-network-command

Structure long-running Claude Code sessions on this Python project so the agent iterates for hours instead of stopping after one pass. Use when the user mentions "long-running session", "multi-hour run", "agent keeps stopping", "agent finishes too early", "headless run", "tmux session", "milestones", "make verify", "fake success", "prevent shortcuts", or asks how to set up hooks, a verification gate, or an operating contract for an autonomous coding agent.

2026-05-310

baa-boundary-reasoning

mlbrilliance/cascadecare-network-command

Activate when the BAA Boundary Reasoner Agent runs or when a regulatory inquiry hits multiple affected provider customers. Teaches how to reason about a single regulatory inquiry against multiple differing BAA terms.

2026-05-310

case-shape-patterns

mlbrilliance/cascadecare-network-command

Activate when designing any new case stage, child case, or grandchild case. Defines the six case-shape patterns Maestro Case must demonstrate.

2026-05-310

Regulatory Citation Guide

Purpose

Ensure all regulatory citations in code, agent prompts, documentation, and UI text are precise and verifiable. Never fabricate case numbers, settlement amounts, or enforcement actions.

When to Activate

Writing agent prompts that reference regulations

Creating synthetic regulatory communications

Building mock regulator responses

Writing documentation that mentions compliance frameworks

Citable Regulatory Sources

HIPAA (Health Insurance Portability and Accountability Act)

Privacy Rule: 45 CFR Part 160 and Subparts A, E of Part 164

Security Rule: 45 CFR Part 160 and Subparts A, C of Part 164

Breach Notification Rule: 45 CFR Part 164 Subpart D (sections 164.400-414)

Business Associate provisions: 45 CFR 164.502(e), 164.504(e)

Enforcement: 45 CFR Part 160 Subparts C, D, E

No Surprises Act / IDR

NSA IDR process: 45 CFR Part 149 (specifically 149.510-149.520)

Federal IDR portal and process rules

State IDR variations where applicable

SEC Disclosure

SEC Item 1.05 (Form 8-K): Material cybersecurity incidents

SEC Regulation S-K Item 106: Cybersecurity risk management

False Claims Act

FCA Civil Cyber-Fraud Initiative (DOJ)

31 U.S.C. sections 3729-3733

State Insurance Codes

State DOI authority: cite as "[State] Insurance Code section [X]" — use fictional state code sections

NAIC Model Laws: cite by model number, not state-specific adoption

Anti-patterns

NEVER fabricate case numbers (e.g., "In re ClearFlow Health, Case No. 24-cv-1234")

NEVER cite specific settlement amounts as if they are real ("$XX million settlement")

NEVER cite real enforcement actions against real companies

NEVER present regulatory analysis as legal advice — always label as "decision-support draft"

When uncertain about a citation, use the general statute reference (e.g., "45 CFR 164.400-414") rather than inventing a specific subsection

name	regulatory-citer
description	Activate whenever regulatory text appears in code, prompts, or docs. Guides precise citation of US healthcare regulatory sources.