Skip to content
SkillCheatSheet Sign in

maintain-formal-verification-skill

An AI agent skill from cursor/plugins, scored 78 out of 100 by code.

78/ 100B

Code score by group

  • Spec20/20
  • Description12/20
  • Procedure12/15
  • Done criteria15/15
  • Resources7/10
  • Scripts5/8
  • Safety7/7
  • Upkeep0/5

It loses the most points in Description (8), the group that checks whether the description says what the skill does and when to use it.

What the author says it does

Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, "is the model still true to the code", or after merges and refactors that touched verified code without rechecking it.

This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.

Repository
cursor/plugins
Folder
pstack/skills/maintain-formal-verification-skill
License
Not identified by GitHub
GitHub stars
16,078
SKILL.md lines
59
Other files
0

Add maintain-formal-verification-skill to your agent

npx skills add cursor/plugins --skill maintain-formal-verification-skill

The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored. GitHub identifies no license for this repository, so check its terms before you use it.

Labelled for

More skills from cursor/plugins

  1. create-verification-skill

    Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control sk…

    78B
  2. why

    Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence ca…

    72B
  3. benchmark-checklist

    Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or r…

    71B
  4. debug-voice

    Use when the user runs /debug-voice, says voice mode has flaws, asks to see or capture what happened in a Grok realtime voice session, or a voice integration has no debug logging…

    71B
  5. maintain-verification-skill

    Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of prov…

    71B
  6. review-plugin-submission

    Audit a Cursor plugin for marketplace readiness. Use when validating manifests, component metadata, discovery paths, and submission quality before publishing.

    71B
  7. figure-it-out

    Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, r…

    70B
  8. correct

    Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and writ…

    68C

All skills in cursor/plugins

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.