graphjin-config

Manage GraphJin source-mode configuration through approval-gated OpenNeko workflows.

11|Updated May 6, 2026
One-click install
npx skills add https://github.com/open-neko/openneko --skill graphjin-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphjin-config
Source: https://github.com/open-neko/openneko/tree/main/packages/llm/assets/builtin-skills/graphjin-config
Command: npx skills add https://github.com/open-neko/openneko --skill graphjin-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of misconfiguring customer GraphJin data engines by enforcing safe, approval-gated workflows for source-mode configuration changes, preventing accidental exposure of secrets or misconfiguration of internal OpenNeko services.

Core Features & Use Cases

  • Guided Config Management: Propose and manage GraphJin source registrations, access control updates, and role assignments via approved OpenNeko workflows instead of direct config edits.
  • RBAC Enforcement: Set up compliant role-based access control for account-scoped and single-tenant data, with safe default postures for reads, writes, and deletes.
  • Use Case: For example, a data team can use this Skill to add a new PostgreSQL data source to their OpenNeko instance, assign it a secret reference for credentials, and submit the change for admin approval without handling sensitive connection details directly.

Quick Start

Use the graphjin-config skill to propose adding a new PostgreSQL data source with read access set to authenticated for your OpenNeko instance.

Frequently Asked Questions about graphjin-config

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

FAQPage Schema
How do I safely update GraphJin data source configurations without exposing secrets?

To update GraphJin data source configurations safely, use approval-gated workflows to propose source registrations and RBAC updates. This prevents direct config mutation and avoids accidental exposure of credentials while managing OpenNeko services.

How does role-based access control work for GraphJin sources in OpenNeko?

Role-based access control for GraphJin sources enforces compliant read, write, and delete permissions for account-scoped and single-tenant data. It applies safe default postures and requires admin approval for any access control updates.

Can I add a new PostgreSQL data source to GraphJin without handling connection details directly?

Yes, you can add a new PostgreSQL data source by proposing the registration through an approved OpenNeko workflow. You assign a secret reference for credentials and submit the change for admin approval without directly handling sensitive connection details.

Do I need admin approval to change access control policies for GraphJin business data sources?

Yes, changing access control policies for GraphJin business data sources requires admin approval. The system enforces approval-gated workflows for RBAC policy updates and source access settings to maintain compliant data access workflows.

What is the best way to prevent misconfiguration of internal GraphJin services?

The best way to prevent misconfiguration of internal GraphJin services is to enforce guided config management workflows. Proposing changes through approved OpenNeko workflows instead of direct config edits eliminates the risk of accidental service misconfiguration.