arxiv-to-md
Convert arXiv papers to LLM-consumable markdown. Invoke when user provides an arXiv ID or URL, or when syncing academic papers…
Invoke IMMEDIATELY via python script when user requests structured reasoning for open-ended analytical questions. Do NOT explore first - the script orchestrates the thinking workflow.
Claude Code
$ npx -y skills add solatis/claude-config --skill deepthink --agent claude-code
Codex
$ npx skills add solatis/claude-config --skill deepthink -a codex -y
Cursor
$ npx skills add solatis/claude-config --skill deepthink -a cursor -y
Gemini CLI
$ npx skills add solatis/claude-config --skill deepthink -a gemini-cli -y
GitHub Copilot
$ npx skills add solatis/claude-config --skill deepthink -a github-copilot -y
OpenCode
$ npx skills add solatis/claude-config --skill deepthink -a opencode -y
Windsurf
$ npx skills add solatis/claude-config --skill deepthink -a windsurf -y
name: deepthink description: Invoke IMMEDIATELY via python script when user requests structured reasoning for open-ended analytical questions. Do NOT explore first - the script orchestrates the thinking workflow.
When this skill activates, IMMEDIATELY invoke the script. The script IS the workflow.
Invoke:
<invoke working-dir=".claude/skills/scripts" cmd="python3 -m skills.deepthink.think --step 1" />
Do NOT explore or analyze first. Run the script and follow its output.
I use Claude Code for most of my work. After months of iteration, I noticed a pattern: LLM-assisted code rots faster than hand-written code.
Convert arXiv papers to LLM-consumable markdown. Invoke when user provides an arXiv ID or URL, or when syncing academic papers…
Reference documentation for analyzing Claude Code conversation history files
Invoke IMMEDIATELY via python script when user requests codebase understanding, architecture comprehension, or repository…
Invoke IMMEDIATELY via python script to stress-test decisions and reasoning. Do NOT analyze first - the script orchestrates the…
Synchronizes docs across a repository. Use when user asks to sync docs.
Detect and resolve incoherence in documentation, code, specs vs implementation.
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.