Structured bug investigation using formal models for hypothesis-driven debugging. Builds scoped Alloy models (normative rules, data constraints, causal chains, observability) to generate distinguishing experiments and narrow the causality cone around a symptom. Use whenever the user reports a bug, incident, or unexpected behavior and wants rigorous investigation. Trigger on "investigate", "root cause", "debug this", "why does this happen", "find the bug", "postmortem", or any unexplained symptom. Valuable for: business-rule bugs, state machine errors, workflow inconsistencies, cross-service disagreements, investigations where the obvious explanation was already checked. Not for simple stack traces or typos — use when the problem space is large enough that unstructured search would waste time or miss the real cause.
EnglishWrite, run, and interpret Alloy 6 formal models for software systems, business processes, and skill/workflow design. Use this skill whenever the user asks to model, verify, or prove properties about state machines, lifecycle flows, data invariants, API contracts, integration boundaries, permission systems, or business rules. Also trigger when the user mentions Alloy, formal methods, formal verification, model checking, counterexample, temporal logic, or wants to "prove" something about their system. Use even for seemingly simple state-machine questions — the solver catches edge cases that humans miss. This skill applies to any domain: SaaS, e-commerce, fintech, DevOps, or business process design.
English
AGENT SKILLS ATLASIncludes Formal Debugger and Formal Modeling.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Formal Debugger
Structured bug investigation using formal models for hypothesis-driven debugging. Builds scoped Alloy models (normative rules, data constraints, causal chains, observability) to generate distinguishing experiments and narrow the causality cone around a symptom. Use whenever the user reports a bug, incident, or unexpected behavior and wants rigorous investigation. Trigger on "investigate", "root cause", "debug this", "why does this happen", "find the bug", "postmortem", or any unexplained symptom. Valuable for: business-rule bugs, state machine errors, workflow inconsistencies, cross-service disagreements, investigations where the obvious explanation was already checked. Not for simple stack traces or typos — use when the problem space is large enough that unstructured search would waste time or miss the real cause.
Formal Modeling
Write, run, and interpret Alloy 6 formal models for software systems, business processes, and skill/workflow design. Use this skill whenever the user asks to model, verify, or prove properties about state machines, lifecycle flows, data invariants, API contracts, integration boundaries, permission systems, or business rules. Also trigger when the user mentions Alloy, formal methods, formal verification, model checking, counterexample, temporal logic, or wants to "prove" something about their system. Use even for seemingly simple state-machine questions — the solver catches edge cases that humans miss. This skill applies to any domain: SaaS, e-commerce, fintech, DevOps, or business process design.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Formal Debugger skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- License details are not provided in these listings. Check the author’s terms before using the skills.