agentleFS
Sign inStart free
CSlawyer1985CSlawyer1985/claude-for-legal-ZH/.agents/skills/chinese-legal-regulatory/SKILL.md

chinese-legal-regulatory

Skill863 starsChanged 34 days agoApache-2.0View on GitHub

Use when the user needs Chinese legal work in the 监管合规 domain: 法规动态监控、监管简报、政策差异比对、合规差距、征求意见稿、监管政策重写、行政监管. This is a Codex adapter for claude-for-legal-ZH/regulatory-legal; it routes natural-language requests to the original domain CLAUDE.md and skills/*/SKILL.md workflows.

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read regulatory-legal/CLAUDE.md before substantive work.

    line 19
  2. Distinctive:

    Follow that skill's workflow, translating Claude Code slash-command wording into Codex actions and natural conversation.

    line 21
  3. Distinctive:

    If multiple original skills apply, execute them in the order implied by the workflow and merge the result.

    line 22
  4. Distinctive:

    Do not run Claude-specific plugin commands.

    line 23
  5. Distinctive:

    If a populated Claude profile exists, read it as the user's existing practice profile.

    line 29
  6. Very specific:

    If the selected skill requires setup and the profile still contains [PLACEHOLDER], run the domain's cold-start-interview workflow in …

    line 31
  7. Very specific:

    When an original instruction says to run /regulatory-legal:some-command, interpret that as: load skills/some-command/SKILL.md and perform …

    line 33
  8. Distinctive:

    Treat all output as lawyer-review draft work, not legal advice replacing professional judgment.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

监管合规 Codex Adapter

This skill lets Codex use the original claude-for-legal-ZH/regulatory-legal content without requiring Claude Code slash commands.

Source Files

  • Domain root: regulatory-legal
  • Domain profile template and shared rules: regulatory-legal/CLAUDE.md
  • Original skills directory: regulatory-legal/skills
  • Original plugin description: 监管追踪实务：监测监管法规动态，对比新规与政策库的差异，跟踪征求意见期和合规差距，编制团队周一晨会监管简报。

How To Use

  1. Read regulatory-legal/CLAUDE.md before substantive work.
  2. Select the closest original skill from the list below, then read its SKILL.md.
  3. Follow that skill's workflow, translating Claude Code slash-command wording into Codex actions and natural conversation.
  4. If multiple original skills apply, execute them in the order implied by the workflow and merge the result.
  5. Do not run Claude-specific plugin commands. Ignore Claude hooks. Use Codex tools for local files, web verification, document rendering, and user-visible output.

Configuration Compatibility

The original project stores setup profiles under ~/.claude/plugins/config/.... For Codex, use this order:

  1. If a populated Claude profile exists, read it as the user's existing practice profile.
  2. Otherwise use or create ~/.codex/legal-zh/regulatory-legal/CLAUDE.md for Codex-specific setup.
  3. If the selected skill requires setup and the profile still contains [PLACEHOLDER], run the domain's cold-start-interview workflow in conversation before producing customized legal work.

When an original instruction says to run /regulatory-legal:some-command, interpret that as: load skills/some-command/SKILL.md and perform the workflow in Codex.

Available Original Skills

cold-start-interview, comments, customize, gap-surfacer, gaps, matter-workspace, policy-diff, policy-redraft, reg-feed-watcher

Legal Output Rules

  • Treat all output as lawyer-review draft work, not legal advice replacing professional judgment.
  • Mark uncertain legal citations or case references as requiring verification unless verified from a reliable source in this session.
  • For current law, regulatory updates, case retrieval, filing requirements, deadlines, or other time-sensitive legal facts, verify with current sources before relying on them.
  • Preserve the original workflow's escalation, approval, confidentiality, and source-labeling requirements.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free