メニュー
Use Jacobian's MCP operations for nontrivial mathematical computation, finite search, structural analysis, formal checking, probability, or optimization.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/morluto/jacobian --skill jacobian-mathコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Decompose a bounded corpus of mathematical proofs, formalizations, scripts, and certificates into recurring solution techniques and the smallest reusable Jacobian postconditions. Use for repository- or corpus-level “what can Jacobian learn?” audits; do not use for one operation contract or one agent trajectory.
Review completed or paused mathematical agent transcripts, visible reasoning, code, searches, tool calls, corrections, and final claims to extract evidence-backed lessons for Jacobian operations, discovery, contracts, skills, evaluations, and documentation. Use for mathematical workflow retrospectives and "what should we learn from this trajectory?" requests. Do not use to continue solving the problem or infer hidden chain-of-thought.
Audit one bounded Jacobian mathematical slice for missing or unusable executable vocabulary using source demand, catalog composition, contract evidence, and maintained-backend feasibility. Use for proactive gap audits that are broader than one operation but narrower than a repository-wide inventory; do not use for reviewing one changed operation or running a full conjecture evaluation.
SKILL.md を表示中
| name | jacobian-math |
| description | Use Jacobian's MCP operations for nontrivial mathematical computation, finite search, structural analysis, formal checking, probability, or optimization. |
Use Jacobian when a mathematical task benefits from exact computation or a
bounded check. Search with math.find, then execute a selected operation with
math.run.
Keep the mathematical reasoning in the agent. Treat operations as atomic instruments: compose their typed results yourself rather than asking discovery to prescribe a proof strategy or workflow.
Before running an operation:
math.find.Use returned values and certificates only for the conclusion they establish. Absence of a witness, a timeout, or an incomplete search is not a proof of a global mathematical claim.