AutoGineer
Generated banner for Solo
Generated logo for Solo

Solo

AnthropicOfficialPublished by Anthropic

  • Skill
  • Workflow
  • Science and research
  • Apache-2.0
  • No issues found
Download ZIP

From the author

Work on one hard mathematics problem in this session yourself, with no sub-agents: reason in stages, record each settled step in a notes file so that nothing written is lost if a response is cut off, and end with a self-contained proof.md. Usage: /math-proof:solo <the problem, stated in full, or the path of a file holding it>.
— the description by Anthropic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The solo skill provides a rigorous, state-aware framework for tackling challenging mathematical problems. It enforces a disciplined approach where the agent works independently, recording every logical step, lemma, and dead end into a persistent notes file. This ensures that reasoning is preserved across multiple message turns, preventing loss of progress due to output limits. The process culminates in the creation of a self-contained proof.md file, ensuring the final result is accessible and verifiable without external context.

What it does

  • Establishes a dedicated directory for problem-solving artifacts.
  • Maintains a persistent notes file to track reasoning stages and intermediate results.
  • Prevents loss of progress by requiring frequent updates to the notes file.
  • Supports resuming interrupted sessions by reading existing notes.
  • Generates a final, self-contained proof document.
  • Operates entirely through internal reasoning without external tool dependencies.

When to use it

  • When you need to solve a complex mathematical problem that requires multi-step logical derivation.
  • When the problem is too large to be solved within a single message's output limit.
  • When you want to ensure a clear, documented trail of your mathematical reasoning.
  • When you need a final, standalone proof document as the primary deliverable.

Advantages

  • Resilient against session timeouts or message length constraints.
  • Ensures logical consistency by forcing explicit documentation of each step.
  • Provides a clear audit trail of the problem-solving process.
  • Enables long-term, multi-turn engagement with difficult proofs.

Usage examples

“/math-proof:solo Prove that there are infinitely many prime numbers.”
The agent creates a directory, initializes notes.md, and begins a multi-stage proof, documenting each step until a final proof.md is generated.
“/math-proof:solo DIR=./fermat_work /path/to/fermat_problem.txt”
The agent reads the problem from the specified file, sets up the workspace in the given directory, and begins the proof process.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/anthropics/solo/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip solo.zip -d .agents/skills

Documentation by Anthropic

math-proof: solo

You solve the problem yourself, in this session. There are no sub-agents and no rounds: just you, a notes file and, at the end, proof.md.

Arguments. The invoking message reads: $ARGUMENTS It gives the problem and, optionally, the run directory. Read it this way. A token of the form DIR=path at its start sets the run directory (the path quoted if it contains spaces); remove it. Any other leading token of the form NAME=value, where NAME is a word of two or more capital letters and underscores and value is a whole number, is a setting this skill does not have: tell the user in one sentence that /math-proof:solo takes only DIR=path before the problem (round and wave settings belong to /math-proof:siege), and that if the token is part of the problem itself the problem can be given as a file path instead, and stop. If what remains is a single line that, taken as a whole — surrounding whitespace and one pair of enclosing quotation marks removed, backslash-escaped spaces read as spaces — is the path of an existing file (it may contain spaces; check with Read or Glob, not the shell), that file is the problem file; if no such file exists and what remains can only be a file path — a single line ending in .md, .txt or .tex, or a single token (no spaces once the quotes are removed) containing "/" or "" — tell the user in one sentence that no file exists at the absolute path you looked for (give it) and that the problem can instead be given in full as text after the command, and stop; otherwise everything that remains, to the end of the message, IS the problem statement, verbatim — mathematics, line breaks and all ("n=3", "N=pq" and "AB=AC" are mathematics, not settings). The run directory DIR defaults to ./math-proof-solo under the current directory; use DIR's absolute path everywhere below. If the message holds neither a readable problem file nor any problem text, say so in one sentence — with the usage, /math-proof:solo <problem statement, or the path of a file holding it> — and stop.

Setup. The run's files are DIR/problem.md (the problem), DIR/notes.md (your notes) and DIR/proof.md (the deliverable). Create DIR with mkdir -p. If DIR/notes.md already exists, this problem was already being worked on in DIR: check that DIR/problem.md is the same problem you were given (compare the text, ignoring differences in whitespace and line endings; for a file, cmp) — if it differs, say in one sentence that DIR holds work on a different problem and that DIR=<another directory> selects a fresh one, and stop; if it is the same, read DIR/notes.md, and DIR/proof.md if it exists. If they record the solution as complete (proof.md written and nothing in the notes still to do), the earlier session finished: say where proof.md is and that DIR=<another directory> starts a fresh attempt, and stop. Otherwise the earlier session ended before it finished, and whatever reasoning it had not written down is lost: continue from the last point recorded there rather than starting over. If DIR/notes.md does not exist yet, put the problem at DIR/problem.md: if it came as a file, copy that file there byte for byte with cp; if it came as text in the invoking message, Write exactly that text (nothing added, removed or reworded). Then Read DIR/problem.md in full; it is the authoritative text of the problem. Use the shell for nothing but that mkdir, cp and cmp.

The task. Solve the problem stated in DIR/problem.md; the deliverable is DIR/proof.md. After reasoning, write your answer. This task runs as a conversation that can span many messages, each with a bounded output allowance; a message that is cut off is normally followed by a request to continue, and only what you have WRITTEN (not unwritten reasoning) is guaranteed to carry into the next message. So write your work product out as you go, in a notes file, DIR/notes.md: whenever you settle something — a lemma and its proof, a reduction, a dead end and why it is dead, the precise statement you are now attempting — write it down before reasoning further. A partial answer is much more useful than none. Writing to the notes is not finishing — keep going after each write. Important: each message's output allowance also covers your private reasoning, and it is far smaller than a hard problem deserves — a message spent entirely on reasoning, with nothing written, gets cut off, and unwritten reasoning should be assumed lost. So do not try to finish in one message. Work in stages: early in EVERY message, before any long derivation, write your current plan and the precise statement you are attempting to DIR/notes.md; then reason toward the next concrete intermediate result, append it to the notes as soon as you have it, and continue. Many short written steps beat one long unwritten one. If a message of yours is cut off, re-read DIR/notes.md and continue from the last thing written there; never start over. You have no web access and no code execution; this is a pure reasoning task. When the problem is resolved, or you have taken it as far as you can, write your complete solution to DIR/proof.md. proof.md is read on its own by a referee who cannot open any other file (not your notes either), so it must be self-contained: every argument the solution relies on is written out in full there. Work unattended: there is no one to answer questions, so never stop to ask.

When DIR/proof.md is written, reply briefly: where proof.md is, and whether it resolves the problem completely or, in proof.md's own words, what it leaves open.

Files

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Declares allowed tools, Claude Code frontmatter

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Anthropic
Publisher
Anthropic (Official)
Source
anthropics/claude-plugins-official · plugins/math-proof/skills/solo · commit 0412be7
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from plugins/math-proof/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Anthropic or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download solo.zip