SKILLEMALL.ai
GitHub ↗ RU Sign in

CC proof-checker

Rigorous mathematical proof verification and fixing workflow. Reads a LaTeX proof, identifies gaps via fresh-agent Codex GPT-6-Astra ultra review, fixes each gap with full derivations, re-reviews, and generates an audit report. Base review is same-family provisional. Use when user says "检查证明", "verify proof", "proof check", "审证明", "check this proof", or wants rigorous mathematical verification of a theory paper.

wanshuiyin/Auto-claude-code-research-in-sleep Claude Code author: wanshuiyin MIT 1 file body ≈ 7 747 tokens Open the sourcegithub.com↗ analyzed 5 h ago

Rigorous mathematical proof verification and fixing workflow.

As a process C 56/100 · Has gaps — References files that are not bundled: ../shared-references/reviewer-backends.md, ../shared-references/fan-out-pattern.md, ../lean-formalize/SKILL.md

ProcedureLaTeXAI and agentsSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
84/100
safety, quality, tests
Safety 60%
94
Quality 40%
70
Run on models
none yet
Process rating
C
56/100
Has gaps
References files that are not bundled: ../shared-references/reviewer-backends.md, ../shared-references/fan-out-pattern.md, ../lean-formalize/SKILL.md
Tools and files w 18
0
Inputs and preconditions w 11
0
When it triggers w 12
50
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 2

✓ No critical or high findings

Medium and low: 2
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash(*)
    allowed-tools: Bash(*) Read Grep Glob Write Edit mcp__antigravity__antigravity mcp__antigravity__antigravity-reply mcp__grok__grok mcp__grok__grok-reply mcp__claude-review__review mcp__claude-review__
  • low Risky intent intent-offensive-security SKILL.md:294
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    ### Phase 1.5: Counterexample Red Team

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 7747 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../shared-references/reviewer-backends.md
  • warning missing-ref reference to a missing file: ../shared-references/fan-out-pattern.md
  • warning missing-ref reference to a missing file: ../lean-formalize/SKILL.md

Process rating: all ten parameters 56/100

Will not run. References files that are not bundled: ../shared-references/reviewer-backends.md, ../shared-references/fan-out-pattern.md, ../lean-formalize/SKILL.md
  • 0Tools and files. 3 referenced file(s) missing: ../shared-references/reviewer-backends.md, ../shared-references/fan-out-pattern.md, ../lean-formalize/SKILL.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 70Execution cost. Instruction body is 7747 tokens
  • 85Steps. 68 steps, 1 vague phrases
  • 100Result and completion. Output format and completion criterion are stated
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 10 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 3 example trigger phrases
  • +3Description length 415: enough signal without eating the budget
  • +4Structure: 53 headings
  • +3Step-by-step instructions: 68 items
  • +3Output format is stated explicitly
  • +4Has examples (13 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.