agentleFS
SafetyMPSafetyMP/HR-ERP/.cursor/skills/hr-product-mcp-governance/SKILL.md

hr-product-mcp-governance

Skill1 starsChanged 6 months agoApache-2.0View on GitHub

Product-runtime HR copilot MCP: catalog, transport, tenant isolation, HITL, hybrid protect-mcp shadow→enforce. Use for lib/copilot, MCP tool additions, red-team scenarios. Not Cursor IDE MCP plugins.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read hr-copilot-mcp.md and agent-mcp-threat-model.md.

    line 32
  2. Distinctive:

    Update threat-model review checklist when adding tools.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

HR product MCP governance

Collaboration plane: Specialized skill — phase 6 only after human tradeoffs recorded. Distinct from Harness HITL (@hr-human-collaboration).

Use this skill when

  • Editing lib/copilot/ (catalog, transport, governance config)
  • Adding or changing tools in COPILOT_TOOL_CATALOG
  • Wiring MCP stdio/websocket transport (Phase 3)
  • Red-team or audit scenarios for cross-tenant tool calls

Do not use this skill when

  • Configuring Cursor workspace MCP plugins (Prisma, Figma, etc.) — use @protect-mcp-governance on the IDE plane
  • MLOps inference routing only (docs/ml/, services/ml-serving/) — use @hr-regulated-domain mlops L3
  • T1/T2 work with no copilot or threat-model surface

Instructions

  1. Read hr-copilot-mcp.md and agent-mcp-threat-model.md.
  2. Catalog: Zod inputSchema.parse before handlers; RBAC permission from descriptor; no direct Prisma in handlers — reuse lib/* with AuthContext.
  3. Identity: tenant_id / subject_id only from JWT/session — never from model arguments.
  4. Side effects: High-stakes mutations via lib/governance/ proposals + HITL — not raw tool execution.
  5. Hybrid boundary: Cedar + shadow mode per transport-rollout.md; enforce only after shadow validation.
  6. Tests: Extend tests/unit/copilot/mcp-tools.test.ts — unique names, read permissions, validation, unknown tool denial.
  7. Update threat-model review checklist when adding tools.

Resources

  • references/tier-mapping.md
  • references/transport-rollout.md
  • hr-regulated-domain product-mcp L3
  • Global @protect-mcp-governance for Cedar/receipts at transport

Limitations

  • Engineering controls only — not legal advice
  • Transport may remain scaffold until Phase 3 exit criteria in implementation-sequence.md

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.