myjkkn-coe-dev-rules

Integrate MyJKKN API with COE local database for data synchronization.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/Jicate-Solutions/MyJKKN-Library --skill myjkkn-coe-dev-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: myjkkn-coe-dev-rules
Source: https://github.com/Jicate-Solutions/MyJKKN-Library/tree/main/.claude/skills/myjkkn-coe-dev-rules
Command: npx skills add https://github.com/Jicate-Solutions/MyJKKN-Library --skill myjkkn-coe-dev-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complexities of integrating MyJKKN API with the COE local database, ensuring efficient institution filtering, role-based access control, and accurate field mappings between systems.

Core Features & Use Cases

  • MyJKKN API Integration: Facilitates seamless data fetching, institution-based filtering, and handling super_admin vs normal user access.
  • Field Mappings: Provides comprehensive field mappings between MyJKKN and COE local database for accurate data synchronization.
  • Use Case: Ideal for developers implementing MyJKKN data fetching, institution-based filtering, or dealing with field name differences across systems.

Quick Start

Use the myjkkn-coe-dev-rules skill to fetch and filter MyJKKN data based on the current institution.

Frequently Asked Questions about myjkkn-coe-dev-rules

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

FAQPage Schema
How do I integrate the MyJKKN API for data synchronization with a local database?

MyJKKN API integration for data synchronization connects the API with the COE local database, managing institution filtering, role-based access control, and field mappings to ensure accurate data alignment across systems.

How does role-based access control work when fetching MyJKKN data?

Role-based access control differentiates between super_admin and normal user access when fetching MyJKKN data, ensuring that users only retrieve and synchronize institution-level records permitted by their assigned roles.

What is the best way to handle field mappings between MyJKKN and a local database?

Handling field mappings between MyJKKN and the COE local database requires applying comprehensive mapping rules that translate field name differences across systems to guarantee accurate CRUD operations and data validation.

How do I filter MyJKKN API data based on the current institution?

Filtering MyJKKN API data based on the current institution involves applying institution-based filtering parameters during data fetching to synchronize only relevant records with the COE local database.

Does MyJKKN API integration support CRUD operations and data validation?

MyJKKN API integration supports CRUD operations and data validation within development workflows by streamlining data fetching, institution-based filtering, and field mappings between MyJKKN and the COE local database.

Why are my field mappings failing during MyJKKN data synchronization?

Field mappings during MyJKKN data synchronization fail when field name differences between MyJKKN and the COE local database are not accurately translated, causing data validation errors and misaligned CRUD operations.