Agent skill · Design & Presentation

skill-model-checker

Research and develop semantic theories using ModelChecker with Z3 SMT solver. Define operators, adjust frame constraints, create examples, run tests, and report findings. Invoke with /mc or when working with model-checker, semantic theories, or Z3 constraints.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill skill-model-checker-benbrastmckie-modelchecker-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 18 KB
Bundled scripts: none
Allowed tools: ReadWriteEditGlobGrepBash(PYTHONPATH=*pytest*)Bash(PYTHONPATH=*python*)Bash(cd
Path: skills/analysis/skill-model-checker-benbrastmckie-modelchecker-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# ModelChecker Research Skill Comprehensive skill for developing and testing modular semantic theories using the ModelChecker framework with Z3 SMT solver. ## Trigger Conditions This skill activates when: - User invokes `/mc` command - Working with semantic theories (logos, exclusion, imposition, bimodal) - Defining or modifying operators - Creating or adjusting frame constraints - Writing model-checker examples - Running theory tests - Analyzing countermodels or theorem results ## Context Loading Load these context files as needed during skill execution: ### Core ModelChecker Context (Always Load) - @.claude/context/project/modelchecker/architecture.md - System architecture and package structure - @.claude/context/project/modelchecker/theories.md - Theory library overview (logos, exclusion, imposition, bimodal) - @.claude/context/project/modelchecker/z3-patterns.md - Z3 solver patterns and best practices ### Domain Context (Load When Relevant) - @.claude/context/project/logic/domain/kripke-semantics-overview.md - Modal semantics background ### Installation Context (Load for Troubleshooting) - @.claude/context/project/modelchecker/installation.md - Installation and CLI usage ## Sub

What's inside
Steps it walks through
  1. Trigger Conditions
  2. Context Loading
  3. Core ModelChecker Context (Always Load)
  4. Domain Context (Load When Relevant)
  5. Installation Context (Load for Troubleshooting)
  6. Sub-Commands
  7. Quick Start
  8. Running the Model Checker
  9. Running Tests
  10. Operator Definition Workflow
  11. When to Use
  12. Theory Structure
  13. Operator Class Template
  14. Operator Registration
Ships with 1 file
  • metadata.json
Commands it runs
Development CLI (recommended)
cd Code && ./dev_cli.py examples/my_example.py
Installed package
model-checker examples.py              # Basic run
model-checker examples.py --maximize   # Compare theories
model-checker examples.py --save       # Export results
All tests
Specific theory
With coverage
Specific test file
More from claude-skill-registry
All skills →
About this skill
What does the skill-model-checker skill do?

Research and develop semantic theories using ModelChecker with Z3 SMT solver. Define operators, adjust frame constraints, create examples, run tests, and report findings. Invoke with /mc or when working with model-checker, semantic theories, or Z3 constraints.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill skill-model-checker-benbrastmckie-modelchecker-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going