One-click install
npx skills add https://github.com/tractorjuice/arckit-kimi --skill arckit-us-icam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arckit-us-icam
Source: https://github.com/tractorjuice/arckit-kimi/tree/main/skills/arckit-us-icam
Command: npx skills add https://github.com/tractorjuice/arckit-kimi --skill arckit-us-icam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the complex task of designing Identity, Credential, and Access Management (ICAM) architectures that meet stringent US federal compliance standards like OMB M-19-17 and NIST SP 800-63-3.

Core Features & Use Cases

  • Risk-Based Assurance Mapping: Automatically determines IAL, AAL, and FAL levels based on specific use case risk profiles.
  • Compliance Pattern Generation: Provides standardized architectural patterns for PIV-based employee access and login.gov-based citizen access.
  • Use Case: An architect needs to define the identity proofing and authentication requirements for a new public-facing federal portal to ensure it meets NIST 800-63-3 standards for IAL2/AAL2.

Quick Start

Invoke the arckit-us-icam skill to generate the identity architecture documentation for the project named federal-portal-v1.

Frequently Asked Questions about arckit-us-icam

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

FAQPage Schema
How do I design an ICAM architecture that meets NIST SP 800-63-3 assurance levels?

To design an ICAM architecture compliant with NIST SP 800-63-3, map your system's specific use case risk profiles to the appropriate Identity, Credential, and Access Management assurance levels, selecting matching identity providers and authentication methods.

What is the best way to determine IAL, AAL, and FAL requirements for a federal portal?

Determining IAL, AAL, and FAL requirements involves executing risk-based assurance mapping against the portal's use cases to automatically establish the necessary Identity, Authentication, and Federation Assurance Levels defined by NIST standards.

How does ICAM compliance pattern generation work for federal employees versus citizens?

ICAM compliance pattern generation works by providing standardized architectural templates, such as utilizing PIV-based access patterns for federal employees and login.gov-based federation patterns for citizen access.

Can I use this approach to satisfy OMB M-19-17 and FIPS 201-3 federal identity mandates?

Yes, you can satisfy OMB M-19-17 and FIPS 201-3 mandates by generating architectural designs that map identity proofing and authentication controls directly to these specific federal regulatory requirements.

When do I need to map use cases to NIST SP 800-63-3 assurance levels?

You need to map use cases to NIST SP 800-63-3 assurance levels when designing public-facing federal portals or internal systems, ensuring identity proofing and authentication mechanisms match the required risk profiles.

What are the limitations of using standardized ICAM compliance patterns for diverse user populations?

Limitations arise because standardized ICAM compliance patterns must accommodate diverse user populations, requiring distinct federation approaches like PIV for employees and login.gov for citizens rather than a single unified authentication method.