Loading...
Loading...
Found 9 Skills
Verifies factual claims in documents using web search and official sources, then proposes corrections with user confirmation. Use when the user asks to fact-check, verify information, validate claims, check accuracy, or update outdated information in documents. Supports AI model specs, technical documentation, statistics, and general factual statements.
Use when fact-checking a single wiki page against its cited sources — verifies that every footnote actually supports its claim and surfaces uncited factual claims. Run after ingesting a high-stakes page or any time you want confidence in one page's accuracy.
Converts Markdown files to one MS Word document per file using plugin-local scripts. V2 includes L5 Delegated Constraint Verification for strict binary artifact linting.
Use when validating markdown links or Mermaid diagrams.
Extract cited obligations, deadlines, tasks from documents.
Pre-submission checklist for LaTeX academic papers. Use when the user wants to submit a paper, check submission readiness, prepare camera-ready, switch to final mode, or verify a paper is ready for a conference deadline.
Use when parameter values appear in multiple documents and consistency must be verified, especially for quantitative values that may differ due to measurement context or require reconciliation
Verify that a Markdown file has correct formatting — headings, lists, links, code blocks, spacing, and consistent style.
Explains concepts, PRs, and designs for a specific reader as concise crash-course material without unnecessary verbosity, and verifies the diagrams and claims with tools. Build the reader persona—including what they already know, what they do not know, and how they read—from questions and public information, and write only the resulting delta. Create diagrams with vlmkit-anim against a fact sheet, re-run and cross-check code and output quoted in the body, and pass the HTML through vlmkit's validation gates. Use when the user says “explain this to me / to <person>”, “crash-course material”, “explanatory documentation”, “I want to understand this PR”, “explain it so I understand”, “I can't keep up with what the agent wrote”, or when a reviewer asks what a change does and the answer needs more than a paragraph. Also use it when the user wrote an explanation themselves and lost confidence in it.