tlaplus-security-skill

Generate TLA+ specifications and TLC configurations for formal security verification.

1|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/dtsong/claude-code-windows-setup --skill tlaplus-security-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tlaplus-security-skill
Source: https://github.com/dtsong/claude-code-windows-setup/tree/main/skills/soc-security/skills/tlaplus-security-skill
Command: npx skills add https://github.com/dtsong/claude-code-windows-setup --skill tlaplus-security-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill translates security findings and protocol behaviors into formal TLA+ specifications, enabling rigorous model checking with TLC to verify security properties.

Core Features & Use Cases

  • Formal Specification: Generates TLA+ modules for security properties like authentication, access control, noninterference, and boot integrity.
  • Model Checking Guidance: Provides concrete TLC configurations and state space estimations for verification.
  • Use Case: Formalize a security invariant for a critical authentication protocol to ensure it cannot be bypassed, using TLA+ patterns for state machines and access control.

Quick Start

Use the tlaplus-security-skill to formalize the security property 'no unauthorized state transition' for the TDISP protocol.

Frequently Asked Questions about tlaplus-security-skill

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

FAQPage Schema
How do I formalize security invariants for a protocol using TLA+?

To formalize security invariants in TLA+, you provide detailed system descriptions and security property types to generate TLA+ modules, enabling rigorous model checking with TLC to verify state machines and protocol security.

Can TLA+ model checking verify noninterference properties for access control systems?

Yes, TLA+ model checking can verify noninterference and access control properties by generating specific TLA+ specifications and TLC configurations that validate security invariants against unauthorized state transitions.

What inputs are needed to generate a TLA+ specification for formal security verification?

Generating TLA+ specifications for formal security verification requires detailed system descriptions, specific security property types, and defined abstraction levels to produce valid TLA+ modules and matching TLC configurations.

How do I configure TLC for verifying liveness properties in TLA+ security specifications?

Configuring TLC for liveness verification involves generating concrete TLC configurations alongside your TLA+ security specifications, providing state space estimations to effectively model check liveness properties and security invariants.

When should I use formal methods for security verification instead of traditional testing?

Use formal methods for security verification when you need to mathematically prove critical authentication protocols cannot be bypassed, applying TLA+ patterns to state machines and access control to find vulnerabilities testing misses.

Does the tlaplus-security-skill support formalizing boot integrity and authentication protocols?

Yes, the tlaplus-security-skill supports formalizing boot integrity and authentication protocols by translating security findings and protocol behaviors into formal TLA+ specifications for rigorous model checking with TLC.