Agent skill

Regulatory Research Fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs

Install Regulatory Research Fallback

skills CLI

$ npx skills add HKUDS/OpenSpace --skill regulatory-research-fallback -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install HKUDS/OpenSpace regulatory-research-fallback --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/benchmarks/gdpval/skills/regulatory-research-fallback .claude/skills/regulatory-research-fallback && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "regulatory-research-fallback" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-research-fallback into .claude/skills/regulatory-research-fallback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-research-fallback", 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

$skill-installer install https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-research-fallback

Type 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.

skills CLI

$ npx skills add HKUDS/OpenSpace --skill regulatory-research-fallback -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install HKUDS/OpenSpace regulatory-research-fallback --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/benchmarks/gdpval/skills/regulatory-research-fallback .agents/skills/regulatory-research-fallback && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "regulatory-research-fallback" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-research-fallback into .agents/skills/regulatory-research-fallback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-research-fallback", 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.

skills CLI

$ npx skills add HKUDS/OpenSpace --skill regulatory-research-fallback -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install HKUDS/OpenSpace regulatory-research-fallback --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/benchmarks/gdpval/skills/regulatory-research-fallback .cursor/skills/regulatory-research-fallback && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "regulatory-research-fallback" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-research-fallback into .cursor/skills/regulatory-research-fallback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-research-fallback", 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

$ gemini skills install https://github.com/HKUDS/OpenSpace.git --path benchmarks/gdpval/skills/regulatory-research-fallback

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add HKUDS/OpenSpace --skill regulatory-research-fallback -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install HKUDS/OpenSpace regulatory-research-fallback --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/benchmarks/gdpval/skills/regulatory-research-fallback .gemini/skills/regulatory-research-fallback && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "regulatory-research-fallback" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-research-fallback into .gemini/skills/regulatory-research-fallback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-research-fallback", 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.

GitHub CLI

$ gh skill install HKUDS/OpenSpace regulatory-research-fallback

Installs 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).

skills CLI

$ npx skills add HKUDS/OpenSpace --skill regulatory-research-fallback -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .github/skills && cp -r skills-src/benchmarks/gdpval/skills/regulatory-research-fallback .github/skills/regulatory-research-fallback && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "regulatory-research-fallback" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-research-fallback into .github/skills/regulatory-research-fallback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-research-fallback", 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.

skills CLI

$ npx skills add HKUDS/OpenSpace --skill regulatory-research-fallback -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install HKUDS/OpenSpace regulatory-research-fallback --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/benchmarks/gdpval/skills/regulatory-research-fallback .opencode/skills/regulatory-research-fallback && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "regulatory-research-fallback" agent skill from https://github.com/HKUDS/OpenSpace/tree/main/benchmarks/gdpval/skills/regulatory-research-fallback into .opencode/skills/regulatory-research-fallback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-research-fallback", 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-research-fallback
GitHub stars: 7.8k
Token cost: ~1k tokens
SKILL.md length: 233 words
Files: 2
Skills in repo: 199
Repo updated: Aug 12, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Fallback workflow for regulatory research when web extraction tools fail on government PDFs

Works in 5 steps: Attempt Primary Source Extraction → Activate Fallback - Shell Agent Research → Apply Domain Knowledge → …
Tasks that involve Regulatory compliance
SKILL.md covers When to Use This Skill, Step-by-Step Procedure, Key Principles and Example Output Structure, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Regulatory Research Fallback is an agent skill from HKUDS/OpenSpace. Fallback workflow for regulatory research when web extraction tools fail on government PDFs

Its SKILL.md is about 1k 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-research-fallback”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Attempt Primary Source Extraction
Activate Fallback - Shell Agent Research
Apply Domain Knowledge
Create Documentation with Confidence Levels
Flag Verification Needs

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 (its code samples are markdown).
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 Research Fallback loads about 1k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 233 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~30
When it runs · the whole SKILL.md, loaded when a task matches: ~1k

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). 233 words, ~1,048 tokens.

Download SKILL.mdSave it as .claude/skills/regulatory-research-fallback/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: regulatory-research-fallback
description: Fallback workflow for regulatory research when web extraction tools fail on government PDFs

Regulatory Research Fallback Workflow

This skill provides a systematic approach to gathering regulatory/compliance information when primary web extraction tools fail on government or regulatory website URLs.

When to Use This Skill

read_webpage returns "unknown error" on .gov or regulatory PDF URLs
search_web fails to retrieve current regulatory information
You need to create compliance checklists or regulatory documentation
Primary sources are inaccessible but the task must be completed

Step-by-Step Procedure

Step 1: Attempt Primary Source Extraction

First, try standard web extraction tools:

1. Use read_webpage on the regulatory URL
2. Use search_web for supplementary regulatory information
3. Document which tools failed and with what errors

Step 2: Activate Fallback - Shell Agent Research

When primary tools fail, delegate to shell_agent for secondary research:

Task: "Research [TOPIC] compliance requirements using available system tools. 
Gather information from alternative sources including:
- State/federal regulatory summaries
- Industry compliance guides
- Professional association resources
Focus on actionable checklist items for [SPECIFIC REQUIREMENT]"

Example shell_agent task for pharmacy compliance:

"Research pharmacy compliance requirements for [state]. Gather information 
about licensing, storage, dispensing, and documentation requirements from 
available sources. Create structured notes on mandatory compliance areas."

Step 3: Apply Domain Knowledge

When sources remain inaccessible, use established domain knowledge:

For pharmacy compliance, standard areas include:
- Licensing and registration requirements
- Controlled substance handling
- Prescription record-keeping
- Storage and security protocols
- Patient counseling requirements
- Continuing education obligations

Step 4: Create Documentation with Confidence Levels

Structure output with clear sourcing transparency:

markdown

## [Requirement Area]

**Status**: Based on standard regulatory framework (primary sources inaccessible)

**Key Requirements**:
- [Item 1] - Standard industry requirement
- [Item 2] - Common regulatory expectation
- [Item 3] - Best practice guideline

**Note**: Verify with [specific agency] for jurisdiction-specific requirements

Step 5: Flag Verification Needs

Always include disclaimers when using fallback approach:

⚠️ **Verification Required**: This checklist was created using secondary 
sources due to primary regulatory website inaccessibility. Please verify 
all requirements with the official [Agency Name] before implementation.

Key Principles

Persevere through failures - Tool errors don't mean task failure
Layer your research - Try multiple approaches before concluding information is unavailable
Be transparent - Clearly mark when information comes from secondary sources
Provide value anyway - A best-effort checklist is better than no guidance
Flag verification needs - Help users understand what needs official confirmation

Example Output Structure

markdown

# [Compliance Area] Checklist

## Source Transparency
This document was created using secondary research methods due to 
inaccessibility of primary regulatory sources. All items should be 
verified with official authorities.

## Core Requirements
[Checklist items based on standard regulatory framework]

## Verification Steps
[List of specific items requiring official confirmation]

## Recommended Next Actions
1. Contact [Agency] for current requirements
2. Review [Official Publication] when accessible
3. Consult with [Professional Association] for updates

Applicable Domains

This workflow applies to:

Pharmacy/healthcare compliance
Financial regulatory requirements
Environmental compliance
Building codes and permits
Employment law requirements
Any jurisdiction-specific regulatory research

name: regulatory-research-fallback category: workflow version: 1.0

Files

SKILL.md and 1 other file in benchmarks/gdpval/skills/regulatory-research-fallback of HKUDS/OpenSpace.

SKILL.md
.skill_id

Open the folder on GitHubat commit 3827781

Compare with similar skills

Regulatory Research Fallback 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.

Regulatory Research Fallback compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Regulatory Research Fallback this skillHKUDS/OpenSpace	7.8k	—	~1k	Automated safety check: Pass	MIT	1 mo ago
HIPAA Pre-Deployment Compliance Checkmaziyarpanahi/openmed	5.5k	—	~2k	Automated safety check: Pass	Apache-2.0	today
PaperjurySpark-To-Paper-Skills/paperjury-codex	223	—	~4.4k	Automated safety check: Pass	MIT	2 mo ago
Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance	946	1 repos	~2.3k	Automated safety check: Pass	MIT	today
Spec To Code Compliancevigolium/piolium	140	4 repos	~2.7k	Automated safety check: Pass	MIT	20 days ago
ISO Standards Readiness EvidenceK-Dense-AI/scientific-agent-skills	48k	1 repos	~4.6k	Automated safety check: Notes	MIT	5 days ago

Similar skills

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.
5.5k GitHub stars~2k tokensUpdated today
Legal & ComplianceAuto-check passed
Paperjury
Spark-To-Paper-Skills/paperjury-codex
Pre-submission CS-conference LaTeX paper editing and adversarial review.
223 GitHub stars~4.4k tokensUpdated 2 mo ago
Documents & OfficeAuto-check passed
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
946 GitHub starsUsed in 1 repo~2.3k tokens
Legal & ComplianceAuto-check passed
Spec To Code Compliance
vigolium/piolium
Verifies code implements exactly what documentation specifies for blockchain audits.
140 GitHub starsUsed in 4 repos~2.7k tokens
Documents & OfficeAuto-check passed
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.
48k GitHub starsUsed in 1 repo~4.6k tokens
Legal & ComplianceAuto-check: notes
Iso42001
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert ISO 42001 AI Management System (AIMS) compliance advisor.
946 GitHub starsUsed in 1 repo~3.7k tokens
Legal & ComplianceAuto-check passed

Questions about Regulatory Research Fallback

What does Regulatory Research Fallback do?

Fallback workflow for regulatory research when web extraction tools fail on government PDFs. Regulatory Research Fallback is an agent skill from HKUDS/OpenSpace.

When should I use Regulatory Research Fallback?

Regulatory Research Fallback fits situations like: tasks that involve Regulatory compliance.

How do I install Regulatory Research Fallback in Claude Code?

Run `npx skills add HKUDS/OpenSpace --skill regulatory-research-fallback -a claude-code`. Or copy the skill folder (benchmarks/gdpval/skills/regulatory-research-fallback in HKUDS/OpenSpace) into .claude/skills/regulatory-research-fallback in your project. Claude Code loads it when a task matches its description.

How do I install Regulatory Research Fallback in Codex?

Run `npx skills add HKUDS/OpenSpace --skill regulatory-research-fallback -a codex`. Or copy the skill folder (benchmarks/gdpval/skills/regulatory-research-fallback in HKUDS/OpenSpace) into .agents/skills/regulatory-research-fallback in your project. Codex loads it when a task matches its description.

Can I use Regulatory Research Fallback 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-research-fallback -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-research-fallback, .gemini/skills/regulatory-research-fallback, .github/skills/regulatory-research-fallback and .opencode/skills/regulatory-research-fallback in your project.

What does Regulatory Research Fallback need to run?

SKILL.md names no scripts, command-line tools or credentials: Regulatory Research Fallback is instructions for the agent only.

Does Regulatory Research Fallback 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 Research Fallback 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 Research Fallback use?

Regulatory Research Fallback 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 Research Fallback use?

About 1k tokens (SKILL.md is roughly 4.2k 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 Research Fallback?

Skills that share tags, products or a category with Regulatory Research Fallback: HIPAA Pre-Deployment Compliance Check (maziyarpanahi/openmed, 5.5k stars), Paperjury (Spark-To-Paper-Skills/paperjury-codex, 223 stars), Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars) and Spec To Code Compliance (vigolium/piolium, 140 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Regulatory Research Fallback?

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.

Install Regulatory Research Fallback

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Regulatory Research Fallback Workflow

When to Use This Skill

Step-by-Step Procedure

Step 1: Attempt Primary Source Extraction

Step 2: Activate Fallback - Shell Agent Research

Step 3: Apply Domain Knowledge

Step 4: Create Documentation with Confidence Levels

Step 5: Flag Verification Needs

Key Principles

Example Output Structure

Applicable Domains

name: regulatory-research-fallback category: workflow version: 1.0

Files

Compare with similar skills

Similar skills

More from HKUDS/OpenSpace

Related

Questions about Regulatory Research Fallback