agency-identity-access-engineer

Design OAuth 2.0, OIDC, SAML, and SCIM authentication systems.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-identity-access-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-identity-access-engineer
Source: https://github.com/imMamdouhaboammar/kaku-chatgpt-harness/tree/main/.agents/skills/engineering-identity-access-engineer
Command: npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-identity-access-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity and high-risk nature of implementing authentication and authorization systems, preventing common security vulnerabilities like insecure token handling, broken access control, and improper SSO integration.

Core Features & Use Cases

  • Secure Auth Flows: Implements OAuth 2.0 and OIDC with PKCE, ensuring robust state and nonce validation.
  • Enterprise Identity: Provides blueprints for SAML/OIDC SSO, SCIM provisioning, and multi-tenant RBAC/ABAC models.
  • Use Case: When building a multi-tenant SaaS platform, use this Skill to design a secure session architecture that enforces tenant isolation at the data layer and supports enterprise-grade SSO requirements.

Quick Start

Use the agency-identity-access-engineer skill to generate a secure OIDC authorization code flow implementation with PKCE for a new web application.

Frequently Asked Questions about agency-identity-access-engineer

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

FAQPage Schema
How do I implement a secure OAuth 2.0 and OIDC flow with PKCE for a web application?

Implement secure OAuth 2.0 and OIDC by generating an authorization code flow with PKCE, ensuring robust state and nonce validation to prevent common token handling vulnerabilities and insecure session architectures.

What is the best way to design multi-tenant RBAC and SSO for a SaaS platform?

Design multi-tenant RBAC and SSO using blueprints for SAML/OIDC integration and SCIM provisioning, enforcing tenant isolation at the data layer while supporting enterprise-grade single sign-on requirements.

How does SCIM provisioning work with SAML SSO in enterprise identity systems?

SCIM provisioning automates user lifecycle management across SAML SSO enterprise identity systems, providing standardized blueprints to securely synchronize user accounts and access privileges in multi-tenant SaaS stacks.

How do I enforce phishing-resistant authentication using WebAuthn?

Enforce phishing-resistant authentication by architecting WebAuthn implementations that rely on standardized cryptographic primitives and threat-model-driven security to establish verifiable, phishing-proof user identity verification.

Why does my multi-tenant SaaS application have broken access control and improper SSO integration?

Broken access control and improper SSO integration often stem from complex identity stacks lacking proper tenant isolation, multi-tenant RBAC/ABAC models, and verifiable audit trails to prevent insecure token handling.

When do I need threat-model-driven security for my authentication architecture?

You need threat-model-driven security when architecting complex authentication and authorization systems to satisfy requirements for standardized cryptographic primitives, verifiable audit trails, and robust session management.