一键导入
synthetic-baa-author
Activate during synthetic data generation slices. Teaches how to author plausible, materially-differing BAA terms across 6 provider customers.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Activate during synthetic data generation slices. Teaches how to author plausible, materially-differing BAA terms across 6 provider customers.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
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.
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.
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.
Activate when designing any new case stage, child case, or grandchild case. Defines the six case-shape patterns Maestro Case must demonstrate.
| name | synthetic-baa-author |
| description | Activate during synthetic data generation slices. Teaches how to author plausible, materially-differing BAA terms across 6 provider customers. |
Generate six sets of plausible, materially-different Business Associate Agreement terms so that Reversal 3 (six legal answers to one subpoena) is credible.
| Provider | Archetype | BAA Notification | Breach Threshold | Subcontractor Flow-Down |
|---|---|---|---|---|
| Northstar | 7-hospital regional, SE US | 72 hours | >500 records | Full flow-down required |
| Alpha | Urban academic, Mid-Atlantic | 24 hours | Any confirmed access | Strict flow-down + audit rights |
| Beta | Rural community, Midwest | Reasonable time (~30 days) | >1000 records | Basic flow-down |
| Gamma | Multi-state for-profit chain | 48 hours | Any unauthorized use | Full flow-down + indemnification cap |
| Delta | Specialty surgical network | 72 hours | >100 records | Standard flow-down |
| Epsilon | Children's hospital system | 24 hours | Any access to minor data | Enhanced flow-down + state AG notification |
Each BAA must differ on at least 3 of these 6 dimensions:
Each synthetic BAA should produce a JSON structure with: