neolink-gatekeeper-expert

Document house conventions for the neolink-gatekeeper identity and IAM service.

Updated Apr 22, 2026

Search Tags:#authentication #jwt #golang #iam #gin #gatekeeper

Ready to run

npx skills add https://github.com/Shockwave2k/team-claude-skills --skill neolink-gatekeeper-expert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: neolink-gatekeeper-expert
Source: https://github.com/Shockwave2k/team-claude-skills/tree/main/skills/backend/neolink-gatekeeper-expert
Command: npx skills add https://github.com/Shockwave2k/team-claude-skills --skill neolink-gatekeeper-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Neolink-gatekeeper provides house conventions for the shared identity, authentication, and IAM service used by Neolink and Hive, enabling consistent governance, tenancy isolation, and secure integrations across modules.

Core Features & Use Cases

Documents and enforces tenancy boundaries and per-tenant routing prefixes to prevent cross-tenant data leakage.
Defines three authentication flavors and a unified security posture for APIs, services, and internal actors.
Standardizes error envelopes, token handling, and crypto paths to ensure consistent behavior across the platform.
Serves as the reference for module ownership, deployment wiring, and developer guidance when extending the gatekeeper in new services.

Quick Start

Review the gatekeeper house conventions and follow the tenant-specific routing and security rules when extending or integrating services.

Frequently Asked Questions about neolink-gatekeeper-expert

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

FAQPage Schema

How do I enforce multi-tenant authentication and prevent cross-tenant data leakage in a Golang API?▼

Multi-tenant authentication prevents data leakage by enforcing per-tenant routing prefixes and policy ownership. This Skill defines house conventions for the Neolink/Hive gatekeeper to maintain strict tenancy isolation and secure integrations across modules.

What are the standard JWT token handling and error envelope conventions for an IAM service?▼

Standard JWT token handling requires unified crypto paths and consistent error envelopes across all services. This Skill specifies architectural constraints for token handling and error responses to ensure consistent behavior across the platform.

How do I define authentication flavors for internal actors and services in a Gin application?▼

Defining authentication flavors for internal actors involves establishing a unified security posture for APIs and services. This Skill documents three distinct authentication flavors to govern internal actors and external service integrations.

Can I use a shared identity service for per-tenant routing and policy ownership across multiple modules?▼

A shared identity service supports per-tenant routing and policy ownership across multiple modules. This Skill serves as the reference for module ownership and deployment wiring when extending the gatekeeper in new services.

Why do I need architectural constraints for a gatekeeper service in a multi-tenant environment?▼

Architectural constraints are needed for a gatekeeper service to maintain consistency and security across a multi-tenant environment. This Skill specifies these constraints to ensure standardized token handling, routing, and error management.