Skip to main content
Run any Skill in Manus
with one click
binarybison
GitHub creator profile

binarybison

Repository-level view of 5 collected skills across 1 GitHub repositories.

skills collected
5
repositories
1
updated
2026-06-24
repository map

Where the skills live

Top repositories by collected skill count, with their share of this creator catalog and occupation spread.

repository explorer

Repositories and representative skills

audit-proof
postsecondary-teachers-all-other

Deep audit of a single proof (theorem, lemma, corollary, or proposition). Use this when the user wants to scrutinize one specific formal result — checking logical gaps, assumption consistency, boundary cases, dependency correctness, and quantifier scope. Triggers on phrases like "audit the proof of Theorem N", "is this proof correct", "check the proof of Lemma M", "find issues in this proof".

2026-06-24
evaluate-paper
postsecondary-teachers-all-other

First-pass author-facing review of a real-time systems (or related formal) paper. Use this when the user wants an overall quality assessment, score sheet, or an inventory of every formal result with per-result verdicts before submission. Triggers on phrases like "review my paper", "first pass on this draft", "score this submission", "list every theorem and flag the shaky ones".

2026-06-24
prepare-paper-context
postsecondary-teachers-all-other

Normalize a paper input (PDF, LaTeX source, multi-file LaTeX project, or pre-extracted text) into a clean structured representation that downstream Proofreader skills can consume. Use this once at the start of any non-trivial Proofreader session so the audit, counterexample, defender, and writeup skills don't each re-parse the source. Especially useful for LaTeX projects, where it preserves theorem-environment fidelity that PDF extraction loses. Triggers on "prepare this paper", "set up context for my .tex source", "extract theorems from this project", or when the user supplies a .tex / project root.

2026-06-24
writeup-finding
technical-writers

Draft a clean, self-contained technical brief documenting a correctness finding — usable to share with coauthors, to record in a project log, or to drop into a paper revision as the basis for a fix. Produces LaTeX or Markdown depending on the user's preference. Use when the user says "write this up", "draft a finding for X", "write a brief on the Theorem N issue", or after `audit-proof` + `find-counterexample` + `stress-test-defense` have produced material to synthesize.

2026-06-24
annotate-latex
software-developers

Inject Proofreader audit findings as comment-only annotations into the paper's LaTeX source so the author can review them in their editor next to the actual proof text. Output is plain `%` comments that do NOT affect the rendered PDF and do NOT require any new packages. Produces a unified diff for review before applying. Triggers on "annotate my LaTeX with the findings", "add audit comments to my .tex", "patch my source with the audit results".

2026-05-14
Showing 1 of 1 repositories
All repositories loaded