agentleFS
CSlawyer1985CSlawyer1985/claude-for-legal-ZH/.agents/skills/chinese-legal-reg-monitor/SKILL.md

chinese-legal-reg-monitor

Skill863 starsChanged 34 days agoApache-2.0View on GitHub

Use when the user needs a Chinese legal managed workflow for 监管动态监控工作流: 监管动态监控、法规 feed、监管摘要、重大性过滤、合规周报. This is a Codex adapter for claude-for-legal-ZH/managed-agent-cookbooks/reg-monitor.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read the cookbook README.md and agent.yaml before running the workflow.

    line 20
  2. Distinctive:

    Use local file reads/writes for repositories, trackers, tables, and source documents.

    line 22
  3. Distinctive:

    Use Codex subagents only if the user explicitly asks for parallel agents or the workflow itself is requested as a multi-agent run.

    line 23
  4. Distinctive:

    Use Codex automations only when the user asks to monitor, remind, watch, or repeat the workflow over time.

    line 24
  5. Very specific:

    If the cookbook references subagents, read only the relevant YAML files under subagents/.

    line 25

≈ “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 ports the original managed-agent cookbook into Codex workflow form.

Source Files

  • Cookbook root: managed-agent-cookbooks/reg-monitor
  • Read first: managed-agent-cookbooks/reg-monitor/README.md
  • Agent blueprint: managed-agent-cookbooks/reg-monitor/agent.yaml
  • Steering examples: managed-agent-cookbooks/reg-monitor/steering-examples.json
  • Subagent blueprints: managed-agent-cookbooks/reg-monitor/subagents

How To Use

  1. Read the cookbook README.md and agent.yaml before running the workflow.
  2. Translate Claude managed-agent concepts into Codex execution:
    • Use local file reads/writes for repositories, trackers, tables, and source documents.
    • Use Codex subagents only if the user explicitly asks for parallel agents or the workflow itself is requested as a multi-agent run.
    • Use Codex automations only when the user asks to monitor, remind, watch, or repeat the workflow over time.
  3. If the cookbook references subagents, read only the relevant YAML files under subagents/.
  4. Preserve legal review limits: all outputs are lawyer-review drafts; verify current legal facts and deadlines before reliance.
  5. Produce the cookbook's intended artifact, such as a grid, tracker update, alert, digest, or memo, in the user's requested location or inline if no location is specified.

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.