Map relationships between verification rules for impact analysis and conflict detection.
npx skills add https://github.com/memect/kc --skill rule-graph
Please help me install this Agent Skill. Skill: rule-graph Source: https://github.com/memect/kc/tree/main/template/skills/zh/rule-graph Command: npx skills add https://github.com/memect/kc --skill rule-graph
Build and maintain a graph of relationships between verification rules — shared entities, logical dependencies, and conflicts. Use when analyzing the impact of a regulation change, when optimizing extraction to avoid duplicate work, when checking rule catalog completeness, or rolling up document-level results into a summary. Critical constraint — the graph is an overlay for analysis, NOT a prerequisite for execution. Every rule must remain independently runnable.
Determine a target rule catalog and run the rule-graph analysis to produce an adjacency list of rule relationships.
High-intent search queries and answers about installing and using this skill.
Mapping relationships between compliance rules for impact analysis is done by building a graph overlay that captures shared entities, logical dependencies, and conflicts. This structure enables dependency tracking and completeness checks across evolving regulations.
A rule graph is an adjacency list of metadata mapping dependencies and shared entities across a rule catalog. It helps regulatory compliance by highlighting conflicts, identifying shared corner cases, and tracing impacted rules when regulations change.
Yes, you can use a rule graph to detect conflicting verification rules in a risk catalog by highlighting contrasting rule guidance. This conflict detection surfaces decisions for resolution and identifies shared corner cases affecting multiple rules.
No, a rule graph requires no execution dependencies to run individual verification rules. The graph remains a decoupled overlay for analysis, ensuring every rule maintains explicit independence and remains independently runnable.
The best way to analyze the impact of a regulation change on existing rules is to run a rule graph analysis to trace impacted rules and logical dependencies. This produces an adjacency list to plan testing and optimize extraction.
You should not use graph-based metadata for rule dependency tracking when you need to execute rules at runtime or require execution prerequisites. The graph is strictly an overlay for analysis and must remain decoupled from runtime execution.
Timmy6942025Apply KYC/AML rules grids to onboarding records for risk assessment.
aryaniyapsConvert heterogeneous file collections into interactive HTML knowledge graphs with community detection.
Timmy6942025Extract structured KYC fields from investor onboarding documents into JSON records.
ShadylukinWrite Neumann database queries across relational, graph, vector, and unified engines.
