HIPAA Pre-Deployment Compliance Check
maziyarpanahi/openmed
Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.
Handle tool failures when researching regulatory/government content by using fallback methods and domain knowledge
Install Regulatory Fallback Research
$ npx skills add HKUDS/OpenSpace --skill regulatory-fallback-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install HKUDS/OpenSpace regulatory-fallback-research --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/benchmarks/gdpval/skills/regulatory-fallback-research .claude/skills/regulatory-fallback-research && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "regulatory-fallback-research" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-fallback-research into .claude/skills/regulatory-fallback-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-fallback-research", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-fallback-researchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add HKUDS/OpenSpace --skill regulatory-fallback-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install HKUDS/OpenSpace regulatory-fallback-research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/benchmarks/gdpval/skills/regulatory-fallback-research .agents/skills/regulatory-fallback-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "regulatory-fallback-research" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-fallback-research into .agents/skills/regulatory-fallback-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-fallback-research", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add HKUDS/OpenSpace --skill regulatory-fallback-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install HKUDS/OpenSpace regulatory-fallback-research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/benchmarks/gdpval/skills/regulatory-fallback-research .cursor/skills/regulatory-fallback-research && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "regulatory-fallback-research" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-fallback-research into .cursor/skills/regulatory-fallback-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-fallback-research", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/HKUDS/OpenSpace.git --path benchmarks/gdpval/skills/regulatory-fallback-research--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add HKUDS/OpenSpace --skill regulatory-fallback-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install HKUDS/OpenSpace regulatory-fallback-research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/benchmarks/gdpval/skills/regulatory-fallback-research .gemini/skills/regulatory-fallback-research && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "regulatory-fallback-research" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-fallback-research into .gemini/skills/regulatory-fallback-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-fallback-research", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install HKUDS/OpenSpace regulatory-fallback-researchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add HKUDS/OpenSpace --skill regulatory-fallback-research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .github/skills && cp -r skills-src/benchmarks/gdpval/skills/regulatory-fallback-research .github/skills/regulatory-fallback-research && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "regulatory-fallback-research" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-fallback-research into .github/skills/regulatory-fallback-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-fallback-research", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add HKUDS/OpenSpace --skill regulatory-fallback-research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install HKUDS/OpenSpace regulatory-fallback-research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/benchmarks/gdpval/skills/regulatory-fallback-research .opencode/skills/regulatory-fallback-research && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "regulatory-fallback-research" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-fallback-research into .opencode/skills/regulatory-fallback-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-fallback-research", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
regulatory-fallback-research- GitHub stars
- 7.8k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 395 words
- Files
- 2
- Skills in repo
- 199
- Repo updated
- First seen
- Licence
- MIT
At a glance
Handle tool failures when researching regulatory/government content by using fallback methods and domain knowledge
- Works in 4 steps: Attempt Primary Source Access → Deploy Shell Agent for Secondary Research → Apply Domain Knowledge → …
- Tasks that involve Regulatory compliance
- SKILL.md covers Overview, When to Use This Skill, Step-by-Step Procedure and Code Examples, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Regulatory Fallback Research is an agent skill from HKUDS/OpenSpace. Handle tool failures when researching regulatory/government content by using fallback methods and domain knowledge
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.
It sits in Legal & Compliance, covering Regulatory compliance. The repository describes itself as: "OpenSpace: The Skill Management Layer for AI Agents" -- https://open-space.cloud/. The licence is MIT.
When your agent uses it
- Tasks that involve Regulatory compliance
Example prompts
- “/regulatory-fallback-research”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 3827781. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Regulatory Fallback Research loads about 1.3k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 395 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from HKUDS/OpenSpace at commit 3827781, republished under its MIT licence (© HKUDS). 395 words, ~1,325 tokens.
Download SKILL.mdSave it as
.claude/skills/regulatory-fallback-research/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- regulatory-fallback-research
- description
- Handle tool failures when researching regulatory/government content by using fallback methods and domain knowledge
Regulatory/Government Content Research with Fallback Strategy
Overview
When researching regulatory, government, or compliance-related content, primary sources (official websites, PDFs, regulatory databases) often become inaccessible due to tool failures, access restrictions, or technical issues. This skill provides a resilient workflow to complete research tasks despite these obstacles.
When to Use This Skill
Use this workflow when:
- You need to research regulatory/government content (FDA, CMS, DEA, state boards, etc.)
- Primary source tools (read_webpage, search_web) return 'unknown error' or fail repeatedly
- You need to produce compliance documentation, checklists, or regulatory summaries
Step-by-Step Procedure
Step 1: Attempt Primary Source Access
First, try to access official sources directly:
1. Use read_webpage on known regulatory URLs
2. Use search_web for specific regulatory queries
3. Attempt read_file on any available PDFs or documentsExpected outcomes:
- Success: Proceed with content extraction
- 'unknown error' or repeated failures: Document the failure and proceed to Step 2
Step 2: Deploy Shell Agent for Secondary Research
When primary tools fail, use shell_agent for alternative information gathering:
shell_agent task: "Research [topic] compliance requirements using alternative sources.
Search for summaries, guides, or cached versions of regulatory information.
Focus on established compliance frameworks and best practices."Strategies for shell_agent:
- Request research from multiple angles (state vs federal, industry guides, etc.)
- Ask for aggregated information from secondary sources
- Request compliance checklist templates from industry resources
Step 3: Apply Domain Knowledge
When both primary and secondary research tools fail:
1. Acknowledge the tool limitations explicitly
2. State you will proceed using established domain knowledge
3. Create content based on well-known regulatory frameworksKey domains to leverage:
- Pharmacy compliance: HIPAA, OBRA-90, controlled substance handling, prescription verification, drug storage, patient counseling
- Healthcare compliance: OSHA, HIPAA privacy/security, Medicare/Medicaid billing, infection control
- General regulatory: Documentation requirements, audit trails, staff training, record retention
Step 4: Produce Deliverables Despite Limitations
Continue to completion:
1. Create required outputs (checklists, summaries, documentation)
2. Note any limitations due to inaccessible sources
3. Recommend verification against current official sources
4. Structure content for easy updating when sources become availableCode Examples
Example: Handling Multiple Tool Failures
# Document failures transparently
"Note: Primary regulatory sources (FDA.gov, state board websites)
returned access errors. Content compiled from established
compliance frameworks and industry standards."
# Proceed with domain knowledge
create_pharmacy_checklist(
categories=["prescription_handling", "controlled_substances",
"patient_counseling", "record_keeping"],
basis="OBRA-90 and standard pharmacy practice guidelines"
)
# Add verification disclaimer
"Recommendation: Verify all requirements against current state
board regulations before implementation."Example: Shell Agent Fallback Query
shell_agent task: "Gather pharmacy compliance requirements from
secondary sources including:
1. Industry association guidelines (NCPDP, ASHP)
2. Academic pharmacy practice resources
3. State board examination study materials
4. Compliance training program outlines
Compile into structured checklist format."Show full SKILL.md (156 more words)Show less
Best Practices
Never abandon the task - Tool failures are common with government sites; persist using available methods
Be transparent - Always document which sources were inaccessible and what basis you used instead
Structure for updates - Create modular content that can be easily revised when sources become available
Prioritize safety-critical items - When uncertain, include conservative compliance measures
Recommend verification - Always advise end-users to verify against current official sources
Common Failure Scenarios
| Failure | Fallback Action |
|---|---|
| read_webpage 'unknown error' | Try search_web, then shell_agent |
| search_web 'unknown error' | Try shell_agent research task |
| shell_agent timeout/failure | Proceed with domain knowledge |
| All tools fail | Use established domain knowledge, document limitations |
Quality Criteria
Your output is successful when:
- All required deliverables are produced
- Tool failures are documented transparently
- Content is based on verifiable regulatory frameworks
- Verification recommendations are included
- Content structure allows easy updates
name: regulatory-fallback-research description: Handle tool failures when researching regulatory/government content by using fallback methods and domain knowledge
© HKUDS, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in benchmarks/gdpval/skills/regulatory-fallback-research of HKUDS/OpenSpace.
- SKILL.md
- .skill_id
Open the folder on GitHubat commit 3827781
Compare with similar skills
Regulatory Fallback Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Regulatory Fallback Research this skillHKUDS/OpenSpace | 7.8k | — | ~1.3k | Automated safety check: Pass | MIT | |
| HIPAA Pre-Deployment Compliance Checkmaziyarpanahi/openmed | 5.5k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| ISO Standards Readiness EvidenceK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~4.6k | Automated safety check: Notes | MIT | |
| Iso42001Sushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Legal Compliance SearchSerein-81/financial_rag | 148 | — | ~1.6k | Automated safety check: Notes | None |
Similar skills
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
ISO Standards Readiness Evidence
K-Dense-AI/scientific-agent-skills
Organizes scope, controlled documents, risk files and traceability into draft evidence for human review against ISO 13485, 14971, 17025 and 15189.
Iso42001
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert ISO 42001 AI Management System (AIMS) compliance advisor.
Legal Compliance Search
Serein-81/financial_rag
Looks up current company registration rules, industry licences and compliance obligations in China through live web search, tailored to the business profile.
Ad Compliance Review
zh-xx/legal-assistant-skills
广告合规审核技能，用于审核广告素材是否符合中国广告法及相关法规。适用场景：(1) 用户提交广告文案、广告素材要求合规审核时；(2) 用户提到"广告审核""广告合规""广告法审查"等关键词时；(3) 用户要求检查广告内容是否存在违法违规风险时；(4) 用户提交房地产、食品、医疗、药品、互联网等行业广告要求专项审核时。审核依据涵盖《广告法》《反不正当竞争法》及行业专项法规。
More from HKUDS/OpenSpace
All 199 skills in this repoAudio Track Production Workflow
HKUDS/OpenSpace
Walks through producing a master audio track plus stems in Python, from checking a reference file and timing sections by BPM to effects, a zip archive and final verification.
Cascade Failure Recovery
HKUDS/OpenSpace
Handle cascading data retrieval tool failures by falling back to embedded knowledge generation
Sandbox Code Execution Fallback
HKUDS/OpenSpace
Gives an agent a workaround when its code-execution sandbox keeps failing: save the Python script to a file and run it through the shell instead.
Code Execution Fallback
HKUDS/OpenSpace
A recovery routine for agents whose sandboxed code runner keeps failing: save the Python script to disk, then run it through the shell and read the output.
Code Execution Fallback and Path Anchoring
HKUDS/OpenSpace
Fallback ladder for failed sandboxed code runs, plus the habit of fixing the working directory first so generated files land in the right place.
Code Execution Fallback E81068
HKUDS/OpenSpace
Fallback workflow for executing Python code when executecodesandbox fails repeatedly
Related
Categories
Questions about Regulatory Fallback Research
What does Regulatory Fallback Research do?
Handle tool failures when researching regulatory/government content by using fallback methods and domain knowledge. Regulatory Fallback Research is an agent skill from HKUDS/OpenSpace.
When should I use Regulatory Fallback Research?
Regulatory Fallback Research fits situations like: tasks that involve Regulatory compliance.
How do I install Regulatory Fallback Research in Claude Code?
Run `npx skills add HKUDS/OpenSpace --skill regulatory-fallback-research -a claude-code`. Or copy the skill folder (benchmarks/gdpval/skills/regulatory-fallback-research in HKUDS/OpenSpace) into .claude/skills/regulatory-fallback-research in your project. Claude Code loads it when a task matches its description.
How do I install Regulatory Fallback Research in Codex?
Run `npx skills add HKUDS/OpenSpace --skill regulatory-fallback-research -a codex`. Or copy the skill folder (benchmarks/gdpval/skills/regulatory-fallback-research in HKUDS/OpenSpace) into .agents/skills/regulatory-fallback-research in your project. Codex loads it when a task matches its description.
Can I use Regulatory Fallback Research in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HKUDS/OpenSpace --skill regulatory-fallback-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/regulatory-fallback-research, .gemini/skills/regulatory-fallback-research, .github/skills/regulatory-fallback-research and .opencode/skills/regulatory-fallback-research in your project.
What does Regulatory Fallback Research need to run?
SKILL.md names no scripts, command-line tools or credentials: Regulatory Fallback Research is instructions for the agent only.
Does Regulatory Fallback Research access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Regulatory Fallback Research safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Regulatory Fallback Research use?
Regulatory Fallback Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Regulatory Fallback Research use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Regulatory Fallback Research?
Skills that share tags, products or a category with Regulatory Fallback Research: HIPAA Pre-Deployment Compliance Check (maziyarpanahi/openmed, 5.5k stars), Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars), ISO Standards Readiness Evidence (K-Dense-AI/scientific-agent-skills, 48k stars) and Iso42001 (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Regulatory Fallback Research?
HKUDS (a GitHub organization) maintains it in HKUDS/OpenSpace, which has 7,754 GitHub stars. The repository holds 199 skills in this directory. The repository was last updated on August 12, 2026.
Source: HKUDS/OpenSpace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.