Agent skill

Verify Sequential Statements

by frenzymath in frenzymath/Danus

Verify a markdown proof in the order it is written. An agent skill from frenzymath/Danus.

Apache-2.0Auto-check passedDocuments & Office

Install Verify Sequential Statements

skills CLI
$ npx skills add frenzymath/Danus --skill verify-sequential-statements -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install frenzymath/Danus verify-sequential-statements --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/frenzymath/Danus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agents/skills/verify/verify-sequential-statements .claude/skills/verify-sequential-statements && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
verify-sequential-statements
GitHub stars
471
Token cost
~798 tokens
SKILL.md length
390 words
Files
2
Skills in repo
16
Repo updated
First seen
Licence
Apache-2.0

At a glance

Verify a markdown proof in the order it is written. An agent skill from frenzymath/Danus.

  • Works in 10 steps: Extract the assumptions and hypotheses… → Iterate through the statements/subproofs… → For each item, determine a location key → …
  • The task is to check local correctness
  • SKILL.md covers Input Contract, Procedure, Output Contract and Tools
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Verify Sequential Statements is an agent skill from frenzymath/Danus. Verify a markdown proof in the order it is written. Use when the task is to check local correctness, theorem applicability, and reasoning gaps statement by statement through a paper-style proof.

Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Documents & Office. The repository describes itself as: Orchestrating Mathematical Reasoning Agents with Fact-Graph Memory. The licence is Apache-2.0.

When your agent uses it

  • The task is to check local correctness
  • Theorem applicability
  • Reasoning gaps statement by statement through a paper-style proof

Example prompts

  • “/verify-sequential-statements”

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. Extract the assumptions and hypotheses from Statement before checking the proof.
  2. Iterate through the statements/subproofs in the order they appear in the markdown.
  3. For each item, determine a location key
  4. Check local reasoning
  5. Pay special attention to assumptions that an object exists or satisfies a property — sometimes such an object has not been constructed, or…
  6. Audit whether the assumptions from Statement are actually used in the proof.
  7. If some assumptions seem unused, do not assume they are harmless. Reason carefully about whether
  8. Classify findings
  9. Also apply the Hard Prohibitions defined in the verifier contract (agents/contracts/verifier.md, "Hard Prohibitions to enforce"): P1…
  10. Keep each checked item in context for the synthesis step. You persist nothing —

What it can do on your machine

Read from SKILL.md and the folder at commit 6d92e8d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verify Sequential Statements loads about 798 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 390 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~798

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from frenzymath/Danus at commit 6d92e8d, republished under its Apache-2.0 licence (© frenzymath). 390 words, ~798 tokens.

Download SKILL.mdSave it as .claude/skills/verify-sequential-statements/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
verify-sequential-statements
description
Verify a markdown proof in the order it is written. Use when the task is to check local correctness, theorem applicability, and reasoning gaps statement by statement through a paper-style proof.

Verify Sequential Statements

Check each statement and subproof in order and log all local issues.

Input Contract

Assume:

  • Proof is markdown text.
  • The proof is written in good mathematical order.
  • Statement contains the target theorem statement and its hypotheses.

Do not split the proof with utility code. Read the markdown in order and use its own structure.

Procedure

  1. Extract the assumptions and hypotheses from Statement before checking the proof.
  2. Iterate through the statements/subproofs in the order they appear in the markdown.
  3. For each item, determine a location key:
    • use the displayed theorem/lemma/claim heading if present,
    • otherwise use a local textual locator such as proof paragraph 2.
  4. Check local reasoning:
    • Is the inference valid?
    • Are assumptions stated and sufficient?
    • Is each theorem application valid in context?
    • Are there skipped or hand-wavy steps?
  5. Pay special attention to assumptions that an object exists or satisfies a property — sometimes such an object has not been constructed, or it exists but has not been proved to satisfy the claimed property.
  6. Audit whether the assumptions from Statement are actually used in the proof.
  7. If some assumptions seem unused, do not assume they are harmless. Reason carefully about whether:
    • the assumption is truly redundant, or
    • the proof is silently omitting a necessary use of it and therefore has a gap or error.
  8. Classify findings:
    • critical_error: logical contradiction, invalid theorem use, false implication.
    • gap: missing derivation, vague justification, unsupported step, or suspiciously unused assumptions whose role is not justified.
  9. Also apply the Hard Prohibitions defined in the verifier contract (agents/contracts/verifier.md, "Hard Prohibitions to enforce"): P1 (citing problem.md / data/<NAME>.md as a substantive math source), P3 (an unproven conditional premise with no same-paragraph fact_id citation), P5 (a vague gesture at a "well-known"/"classical" result without a specific citation), and P6 (a statement that is not self-contained). Do not restate or fork the prohibition wording here — read and apply it from the contract so there is a single source of truth. These prohibitions are strictly additive: they only ever add findings (reject more), never remove them.
  10. Keep each checked item in context for the synthesis step. You persist nothing — the verifier is stateless; the worker does all writing.
Show full SKILL.md (24 more words)Show less

Output Contract

Produce one record per checked item, kept in context for synthesis:

json
{
  "location": "Lemma 3",
  "status": "checked",
  "critical_errors": [
    {"location": "Lemma 3", "issue": "Incorrect implication from A to B."}
  ],
  "gaps": [
    {"location": "Lemma 3", "issue": "Missing justification of boundedness."}
  ]
}

Tools

  • None — pure reasoning over the proof; findings stay in context.

© frenzymath, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in agents/skills/verify/verify-sequential-statements of frenzymath/Danus.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 6d92e8d

Compare with similar skills

Verify Sequential Statements next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Verify Sequential Statements compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify Sequential Statements this skillfrenzymath/Danus471—~798Automated safety check: PassApache-2.0
Markdown Article FormatterJimLiu/baoyu-skills26k6 repos~3.5kAutomated safety check: PassMIT
MarkitdownImCa0/just-laws78114 repos~3.2kAutomated safety check: NotesMIT
Obsidian MarkdownAtmosphere/atmosphere3.8k20 repos~1.3kAutomated safety check: PassApache-2.0
DOCXrvdbreemen/OTGW-firmware20733 repos~4.3kAutomated safety check: PassProprietary
Gzh Designisjiamu/gzh-design-skill3.9k1 repos~2.2kAutomated safety check: PassAGPL-3.0

Similar skills

  • Markdown Article Formatter

    JimLiu/baoyu-skills

    Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.

    26k GitHub starsUsed in 6 repos~3.5k tokens
    Documents & OfficeAuto-check passed
  • Markitdown

    ImCa0/just-laws

    Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.

    781 GitHub starsUsed in 14 repos~3.2k tokens
    Documents & OfficeAuto-check: notes
  • Obsidian Markdown

    Atmosphere/atmosphere

    Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.

    3.8k GitHub starsUsed in 20 repos~1.3k tokens
    Documents & OfficeAuto-check passed
  • DOCX

    rvdbreemen/OTGW-firmware

    A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).

    207 GitHub starsUsed in 33 repos~4.3k tokens
    Documents & OfficeAuto-check passed
  • Gzh Design

    isjiamu/gzh-design-skill

    微信公众号文章排版引擎,将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取,自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入(非 Markdown…

    3.9k GitHub starsUsed in 1 repo~2.2k tokens
    Documents & OfficeAuto-check passed
  • Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.

    41k GitHub stars~2.5k tokensUpdated 3 days ago
    Documents & OfficeAuto-check passed

More from frenzymath/Danus

All 16 skills in this repo
  • Validate externally referenced theorems by querying arXiv theorem search first and Codex's built-in web search second.

    471 GitHub stars~852 tokensUpdated 1 mo ago
    Auto-check passed
  • Construct candidate counterexamples to test a proposed conjecture, lemma, or intermediate claim by keeping the assumptions true while making the claimed conclusion fail.

    471 GitHub stars~790 tokensUpdated 1 mo ago
    Auto-check passed
  • Construct Toy Examples

    frenzymath/Danus

    Generate and analyze simpler examples that satisfy both the assumptions and the conclusion of a theorem statement or subgoal.

    471 GitHub stars~541 tokensUpdated 1 mo ago
    Auto-check passed
  • Direct Proving

    frenzymath/Danus

    Screen a decomposition plan by first trying to prove all of its subgoals directly, then identifying the key stuck points if the plan does not fully go through.

    471 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Identify Key Failures

    frenzymath/Danus

    Synthesize the common stuck points across failed decomposition plans.

    471 GitHub stars~586 tokensUpdated 1 mo ago
    Auto-check passed
  • Derive immediate mathematical consequences from a theorem statement or subgoal.

    471 GitHub stars~587 tokensUpdated 1 mo ago
    Auto-check passed

Questions about Verify Sequential Statements

What does Verify Sequential Statements do?

Verify a markdown proof in the order it is written. An agent skill from frenzymath/Danus. Verify Sequential Statements is an agent skill from frenzymath/Danus. Verify a markdown proof in the order it is written.

When should I use Verify Sequential Statements?

Verify Sequential Statements fits situations like: the task is to check local correctness; theorem applicability; reasoning gaps statement by statement through a paper-style proof.

How do I install Verify Sequential Statements in Claude Code?

Run `npx skills add frenzymath/Danus --skill verify-sequential-statements -a claude-code`. Or copy the skill folder (agents/skills/verify/verify-sequential-statements in frenzymath/Danus) into .claude/skills/verify-sequential-statements in your project. Claude Code loads it when a task matches its description.

How do I install Verify Sequential Statements in Codex?

Run `npx skills add frenzymath/Danus --skill verify-sequential-statements -a codex`. Or copy the skill folder (agents/skills/verify/verify-sequential-statements in frenzymath/Danus) into .agents/skills/verify-sequential-statements in your project. Codex loads it when a task matches its description.

Can I use Verify Sequential Statements in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add frenzymath/Danus --skill verify-sequential-statements -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-sequential-statements, .gemini/skills/verify-sequential-statements, .github/skills/verify-sequential-statements and .opencode/skills/verify-sequential-statements in your project.

What does Verify Sequential Statements need to run?

SKILL.md names no scripts, command-line tools or credentials: Verify Sequential Statements is instructions for the agent only.

Does Verify Sequential Statements access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Verify Sequential Statements safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Verify Sequential Statements use?

Verify Sequential Statements is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify Sequential Statements use?

About 798 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Verify Sequential Statements?

Skills that share tags, products or a category with Verify Sequential Statements: Markdown Article Formatter (JimLiu/baoyu-skills, 26k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and DOCX (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify Sequential Statements?

frenzymath (a GitHub organization) maintains it in frenzymath/Danus, which has 471 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on August 27, 2026.

Source: frenzymath/Danus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.