MCP-doctypes/HR

Extract and validate SKILL.md frontmatter metadata for HR MCPs.

1|Updated Jul 5, 2025
One-click install
npx skills add https://github.com/EPIUSECX/cohenix_mcp_frappe --skill mcp-doctypes-hr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP-doctypes/HR
Source: https://github.com/EPIUSECX/cohenix_mcp_frappe/tree/main/MCP-doctypes/HR
Command: npx skills add https://github.com/EPIUSECX/cohenix_mcp_frappe --skill mcp-doctypes-hr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill unit provides a standardized framework to document and discover Master Control Plans (MCP) for HR Doctypes, enabling consistent metadata extraction and discovery across a repository.

Core Features & Use Cases

  • Centralized MCP templates define Doctype metadata, fields, permissions, and relationships.
  • Enables auditing and comparison of HR Doctype MCPs for governance and compliance.
  • Use Case: Given a new HR Doctype, create or update an MCP entry and generate corresponding SKILL metadata for discovery and activation.

Quick Start

Use the MCP-doctypes/HR skill to audit and document HR Master Control Plans and extract frontmatter-based metadata for discovery.

Frequently Asked Questions about MCP-doctypes/HR

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract metadata from SKILL.md frontmatter to document HR Doctypes?

You can extract HR Doctype metadata by parsing the SKILL.md frontmatter and loading root instructions. This process requires the SKILL.md file to include at least a name and description to function properly.

What is the best way to standardize Master Control Plan discovery across a repository?

Standardizing Master Control Plan (MCP) discovery involves using centralized templates to define Doctype metadata, fields, permissions, and relationships. This framework enables consistent metadata extraction and auditing for governance and compliance.

How do I load optional resources when parsing HR MCP metadata?

When parsing HR MCP metadata, the system automatically loads any optional resources present in the scripts/, references/, or assets/ directories. These resources are loaded alongside the root instructions during the extraction process.

Does MCP discovery require specific fields in the SKILL.md frontmatter?

Yes, MCP discovery requires the SKILL.md frontmatter to include at least the name and description fields. Without these mandatory fields, the metadata extraction and validation process cannot execute successfully.

Why do I need to validate frontmatter when onboarding new HR MCPs?

Validating frontmatter ensures consistent discovery and onboarding of HR MCPs across the repository. It allows you to audit and compare Doctype metadata, which is essential for maintaining governance and compliance standards.

Can I use this framework to audit existing HR Doctype MCPs for compliance?

Yes, you can use this framework to audit and compare existing HR Doctype MCPs. By extracting and validating frontmatter-based metadata, it enables thorough governance and compliance checks across your repository.