Citation Management
neflibata-feng/MyArxiv-Agent
Comprehensive citation management for academic research. An agent skill from neflibata-feng/MyArxiv-Agent.
Use the Claude Code CLI to consult Claude and delegate coding tasks for prototyping, debugging, and code review.
Install Collaborating With Claude
$ npx skills add appautomaton/latex-arxiv-SKILL --skill collaborating-with-claude -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install appautomaton/latex-arxiv-SKILL collaborating-with-claude --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/appautomaton/latex-arxiv-SKILL.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/collaborating-with-claude .claude/skills/collaborating-with-claude && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "collaborating-with-claude" agent skill from https://github.com/appautomaton/latex-arxiv-SKILL/tree/main/.codex/skills/collaborating-with-claude into .claude/skills/collaborating-with-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "collaborating-with-claude", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/appautomaton/latex-arxiv-SKILL/tree/main/.codex/skills/collaborating-with-claudeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add appautomaton/latex-arxiv-SKILL --skill collaborating-with-claude -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install appautomaton/latex-arxiv-SKILL collaborating-with-claude --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appautomaton/latex-arxiv-SKILL.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/collaborating-with-claude .agents/skills/collaborating-with-claude && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "collaborating-with-claude" agent skill from https://github.com/appautomaton/latex-arxiv-SKILL/tree/main/.codex/skills/collaborating-with-claude into .agents/skills/collaborating-with-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "collaborating-with-claude", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add appautomaton/latex-arxiv-SKILL --skill collaborating-with-claude -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install appautomaton/latex-arxiv-SKILL collaborating-with-claude --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appautomaton/latex-arxiv-SKILL.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/collaborating-with-claude .cursor/skills/collaborating-with-claude && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "collaborating-with-claude" agent skill from https://github.com/appautomaton/latex-arxiv-SKILL/tree/main/.codex/skills/collaborating-with-claude into .cursor/skills/collaborating-with-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "collaborating-with-claude", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/appautomaton/latex-arxiv-SKILL.git --path .codex/skills/collaborating-with-claude--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add appautomaton/latex-arxiv-SKILL --skill collaborating-with-claude -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install appautomaton/latex-arxiv-SKILL collaborating-with-claude --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appautomaton/latex-arxiv-SKILL.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/collaborating-with-claude .gemini/skills/collaborating-with-claude && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "collaborating-with-claude" agent skill from https://github.com/appautomaton/latex-arxiv-SKILL/tree/main/.codex/skills/collaborating-with-claude into .gemini/skills/collaborating-with-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "collaborating-with-claude", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install appautomaton/latex-arxiv-SKILL collaborating-with-claudeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add appautomaton/latex-arxiv-SKILL --skill collaborating-with-claude -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/appautomaton/latex-arxiv-SKILL.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/collaborating-with-claude .github/skills/collaborating-with-claude && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "collaborating-with-claude" agent skill from https://github.com/appautomaton/latex-arxiv-SKILL/tree/main/.codex/skills/collaborating-with-claude into .github/skills/collaborating-with-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "collaborating-with-claude", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add appautomaton/latex-arxiv-SKILL --skill collaborating-with-claude -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install appautomaton/latex-arxiv-SKILL collaborating-with-claude --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appautomaton/latex-arxiv-SKILL.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/collaborating-with-claude .opencode/skills/collaborating-with-claude && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "collaborating-with-claude" agent skill from https://github.com/appautomaton/latex-arxiv-SKILL/tree/main/.codex/skills/collaborating-with-claude into .opencode/skills/collaborating-with-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "collaborating-with-claude", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
collaborating-with-claude- GitHub stars
- 458
- Used in
- 1 other repo
- Token cost
- ~1.5k tokens
- SKILL.md length
- 655 words
- Files
- 4 (incl. scripts, references, assets)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use the Claude Code CLI to consult Claude and delegate coding tasks for prototyping, debugging, and code review.
- Works in 3 steps: Ask Claude to open files itself → Enforce safe output for code changes → Use Claude for what it’s good at
- Tasks that involve Prototyping
- SKILL.md covers When to use, When not to use, Core rules and Model selection, plus 7 more sections
- Runs Python scripts from its folder; calls python3
What it does
Collaborating With Claude is an agent skill from appautomaton/latex-arxiv-SKILL. Use the Claude Code CLI to consult Claude and delegate coding tasks for prototyping, debugging, and code review. Supports multi-turn sessions via SESSIONID. Optimized for low-token, file/line-based handoff.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts, reference files and assets (for example `assets/prompt-template.md`, `references/shell-quoting.md` and `scripts/claude_bridge.py`).
It sits in Research & Science, covering Prototyping, Design tokens and Citation management. It works with LaTeX. The repository describes itself as: A highly customizable agentic harness for arXiv-ready ML/AI review papers (and beyond). It drives agentic AI like Codex CLI and Claude Code through a gated LaTeX workflow with… The licence is MIT.
When your agent uses it
- Tasks that involve Prototyping
- Tasks that involve Design tokens
- Tasks that involve Citation management
Example prompts
- “/collaborating-with-claude”
Requirements
- Python 3
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b5b0583. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Collaborating With Claude loads about 1.5k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 655 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from appautomaton/latex-arxiv-SKILL at commit b5b0583, republished under its MIT licence (© appautomaton). 655 words, ~1,541 tokens.
Download SKILL.mdSave it as
.claude/skills/collaborating-with-claude/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- collaborating-with-claude
- description
- Use the Claude Code CLI to consult Claude and delegate coding tasks for prototyping, debugging, and code review. Supports multi-turn sessions via SESSION_ID. Optimized for low-token, file/line-based handoff.
- metadata.short-description
- Delegate to Claude Code CLI
Collaborating with Claude Code (Codex)
Use Claude Code CLI as a collaborator while keeping Codex as the primary implementer.
Host note: this skill is written for a Codex host. If you are already running inside Claude Code, do not bridge to Claude Code (that would be circular); use your own capabilities or another collaborator skill.
This skill provides a lightweight bridge script (scripts/claude_bridge.py) that returns structured JSON and supports multi-turn sessions via SESSION_ID.
When to use
- You want a second opinion (design tradeoffs, edge cases, missing tests).
- You want Claude to propose or review a unified diff (Claude does not edit files).
- You want multi-turn back-and-forth while you implement locally.
When not to use
- The task is trivial or one-shot (do it directly in Codex).
- You need authoritative facts that require browsing/citations (Claude may guess).
- You might paste sensitive data (secrets, private keys, prod logs).
Core rules
- Claude is a collaborator; you own the final result and must verify changes locally.
- Do not invoke
claudedirectly; always use the bridge script (scripts/claude_bridge.py) so output/session handling stays consistent. - Prefer file/line references over pasting snippets. Run the bridge with
--cdset to the repo root (it sets theclaudeprocess working directory); use--add-dirwhen Claude needs access to additional directories. - For code changes, request Unified Diff Patch ONLY and forbid direct file modification.
- Always run the bridge script with
--helpfirst if you are unsure of parameters. - Always capture
SESSION_IDand reuse it for follow-ups to keep the collaboration conversation-aware. - For automation, prefer
--SESSION_ID(resume). Session selectors are mutually exclusive: choose one of--SESSION_ID,--continue, or--session-id. - Keep a short Collaboration State Capsule updated while this skill is active.
- Default timeout: when invoking via the Codex command runner, set
timeout_msto 600000 (10 minutes) unless a shorter/longer timeout is explicitly required. - Default model: prefer
sonnetfor routine work; useopusonly for complex tasks or when explicitly requested. - Ensure Claude Code is logged in before running headless commands (run
claudeand/loginonce if needed). - Streamed JSON requires
--verbose; the bridge enables this automatically.
Model selection
Claude Code supports model aliases, so you can use --model sonnet / --model opus instead of hard-coding versioned model IDs.
- If you omit
--model, Claude Code uses its configured default (typically from~/.claude/settings.json, optionally overridden by.claude/settings.jsonand.claude/settings.local.json). - If you need strict reproducibility, pass a full model name via
--model <full-name>.
Show full SKILL.md (259 more words)Show less
Quick start (shell-safe)
⚠️ If your prompt contains Markdown backticks (`like/this`), do not pass it directly via --PROMPT "..." (your shell may treat backticks as command substitution). Use a heredoc instead; see references/shell-quoting.md.
PROMPT="$(cat <<'EOF'
Review src/auth.py around login() and propose fixes.
OUTPUT: Unified Diff Patch ONLY.
EOF
)"
python3 .codex/skills/collaborating-with-claude/scripts/claude_bridge.py --cd "." --model sonnet --PROMPT "$PROMPT" --output-format stream-jsonOutput: JSON with success, SESSION_ID, agent_messages, and optional error / all_messages.
Multi-turn sessions
# Start a session
PROMPT="$(cat <<'EOF'
Analyze the bug in foo(). Keep it short.
EOF
)"
python3 .codex/skills/collaborating-with-claude/scripts/claude_bridge.py --cd "." --PROMPT "$PROMPT" --output-format stream-json
# Continue the same session
PROMPT="$(cat <<'EOF'
Now propose a minimal fix as Unified Diff Patch ONLY.
EOF
)"
python3 .codex/skills/collaborating-with-claude/scripts/claude_bridge.py --cd "." --SESSION_ID "<SESSION_ID>" --PROMPT "$PROMPT" --output-format stream-jsonPrompting patterns (token efficient)
Use assets/prompt-template.md as a starter when crafting --PROMPT.
1) Ask Claude to open files itself
Provide:
- Entry file(s) and approximate line numbers
- Objective and constraints
- Output format (diff vs analysis)
Avoid:
- Pasting large code blocks
- Multiple competing objectives in one request
2) Enforce safe output for code changes
Append this to prompts when requesting code:
OUTPUT: Unified Diff Patch ONLY. Strictly prohibit any actual modifications.
3) Use Claude for what it’s good at
- Alternative solution paths and edge cases
- UI/UX and readability feedback
- Review of a proposed patch (risk spotting, missing tests)
Verification
- Smoke-test the bridge:
python3 .codex/skills/collaborating-with-claude/scripts/claude_bridge.py --help. - If you need a session: run one prompt with
--output-format stream-jsonand confirm the JSON containssuccess: trueand aSESSION_ID. - Note:
--output-format textwon’t include a newly generated session id; usestream-json/jsonto capture it. If you resume with--SESSION_IDintextmode, the bridge echoes thatSESSION_IDin its JSON output.
Safety & guardrails
- Never paste secrets (private keys, API keys, seed phrases) into prompts.
- For code changes, request Unified Diff Patch ONLY and apply changes yourself.
- Treat Claude output as suggestions; verify locally (tests, lint, build) before merging.
Collaboration State Capsule
Keep this short block updated near the end of your reply while collaborating:
[Claude Collaboration Capsule]
Goal:
Claude SESSION_ID:
Files/lines handed off:
Last ask:
Claude summary:
Next ask:References
assets/prompt-template.md(prompt patterns)references/shell-quoting.md(shell quoting/backticks)
© appautomaton, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts, references, assets) in .codex/skills/collaborating-with-claude of appautomaton/latex-arxiv-SKILL.
- SKILL.md
- assets/prompt-template.md
- references/shell-quoting.md
- scripts/claude_bridge.py
Open the folder on GitHubat commit b5b0583
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in appautomaton/latex-arxiv-SKILL, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Collaborating With Claude next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Collaborating With Claude this skillappautomaton/latex-arxiv-SKILL | 458 | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Citation Managementneflibata-feng/MyArxiv-Agent | 126 | 19 repos | ~8.1k | Automated safety check: Notes | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Literature Review AgentAr9av/PaperOrchestra | 677 | 1 repos | ~5.2k | Automated safety check: Pass | Custom licence | |
| Academic Searchustc-ai4science/academic-search | 666 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Arxiv MCP Serverblazickjp/arxiv-mcp-server | 3.2k | — | ~353 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Literature Review Agent
Ar9av/PaperOrchestra
Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). An agent skill from Ar9av/PaperOrchestra.
Academic Search
ustc-ai4science/academic-search
A skill your agent uses when the user asks to search or review academic papers, retrieve scholarly metadata or citation counts, validate or deduplicate scholarly records, find an author's…
Arxiv MCP Server
blazickjp/arxiv-mcp-server
A skill your agent uses when finding, comparing, reading, or monitoring arXiv papers, including requests for abstracts, citation graphs, original LaTeX, section-level technical details, or…
Zotero
congcongwang0122/zotero-skill
Use Zotero Desktop to enable/probe the local API, search a local Zotero library, list items/collections/tags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full…
More from appautomaton/latex-arxiv-SKILL
Arxiv Paper Writer
appautomaton/latex-arxiv-SKILL
Write LaTeX ML/AI review articles for arXiv using the IEEEtran template and verified BibTeX citations.
Collaborating With Gemini
appautomaton/latex-arxiv-SKILL
Use the Gemini CLI to consult Gemini and delegate coding tasks for prototyping, debugging, and code review.
Latex Rhythm Refiner
appautomaton/latex-arxiv-SKILL
Post-process LaTeX project prose to improve readability through varied sentence and paragraph lengths.
Related
Works with
Categories
Questions about Collaborating With Claude
What does Collaborating With Claude do?
Use the Claude Code CLI to consult Claude and delegate coding tasks for prototyping, debugging, and code review. Collaborating With Claude is an agent skill from appautomaton/latex-arxiv-SKILL. Use the Claude Code CLI to consult Claude and delegate coding tasks for prototyping, debugging, and code review.
When should I use Collaborating With Claude?
Collaborating With Claude fits situations like: tasks that involve Prototyping; tasks that involve Design tokens; tasks that involve Citation management.
How do I install Collaborating With Claude in Claude Code?
Run `npx skills add appautomaton/latex-arxiv-SKILL --skill collaborating-with-claude -a claude-code`. Or copy the skill folder (.codex/skills/collaborating-with-claude in appautomaton/latex-arxiv-SKILL) into .claude/skills/collaborating-with-claude in your project. Claude Code loads it when a task matches its description.
How do I install Collaborating With Claude in Codex?
Run `npx skills add appautomaton/latex-arxiv-SKILL --skill collaborating-with-claude -a codex`. Or copy the skill folder (.codex/skills/collaborating-with-claude in appautomaton/latex-arxiv-SKILL) into .agents/skills/collaborating-with-claude in your project. Codex loads it when a task matches its description.
Can I use Collaborating With Claude in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add appautomaton/latex-arxiv-SKILL --skill collaborating-with-claude -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/collaborating-with-claude, .gemini/skills/collaborating-with-claude, .github/skills/collaborating-with-claude and .opencode/skills/collaborating-with-claude in your project.
What does Collaborating With Claude need to run?
Going by SKILL.md and its folder, Collaborating With Claude needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Collaborating With Claude access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Collaborating With Claude safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Collaborating With Claude use?
Collaborating With Claude is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Collaborating With Claude use?
About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 316 tokens, read only when the agent opens those files.
What are the alternatives to Collaborating With Claude?
Skills that share tags, products or a category with Collaborating With Claude: Citation Management (neflibata-feng/MyArxiv-Agent, 126 stars), Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars), Literature Review Agent (Ar9av/PaperOrchestra, 677 stars) and Academic Search (ustc-ai4science/academic-search, 666 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Collaborating With Claude?
appautomaton (a GitHub organization) maintains it in appautomaton/latex-arxiv-SKILL, which has 458 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 13, 2026.
Source: appautomaton/latex-arxiv-SKILL on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.