/ Directory / Playground / julia-agent-skills
● Community JuliaGenAI ⚡ Instant

julia-agent-skills

by JuliaGenAI · JuliaGenAI/julia-agent-skills

JuliaGenAI's skill collection for AI agents writing Julia — starts with DocumenterVitepress.jl, aimed to expand across the Julia ecosystem.

julia-agent-skills is an early-stage collection of Julia-specific skills for Claude Code, Cursor, Gemini CLI, and other agent-skill-compatible tools. At time of writing, the documented skill is documenter-vitepress, which teaches agents to set up and iterate on Julia documentation sites built with DocumenterVitepress.jl. The repo is maintained by JuliaGenAI — the community behind Julia's GenAI tooling.

Why use it

Key features

Live Demo

What it looks like in practice

julia-agent-skill.replay ▶ ready
0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "julia-agent-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/JuliaGenAI/julia-agent-skills",
        "~/.claude/skills/julia-agent-skills"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "julia-agent-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/JuliaGenAI/julia-agent-skills",
        "~/.claude/skills/julia-agent-skills"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "julia-agent-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/JuliaGenAI/julia-agent-skills",
        "~/.claude/skills/julia-agent-skills"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "julia-agent-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/JuliaGenAI/julia-agent-skills",
        "~/.claude/skills/julia-agent-skills"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "julia-agent-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/JuliaGenAI/julia-agent-skills",
        "~/.claude/skills/julia-agent-skills"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json
{
  "context_servers": {
    "julia-agent-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/JuliaGenAI/julia-agent-skills",
          "~/.claude/skills/julia-agent-skills"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add julia-agent-skill -- git clone https://github.com/JuliaGenAI/julia-agent-skills ~/.claude/skills/julia-agent-skills

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use julia-agent-skills

Bootstrap a DocumenterVitepress.jl documentation site for a Julia package

👤 Julia package maintainers ⏱ ~30 min intermediate

When to use: You have a Julia package and want modern Vitepress-based docs instead of default Documenter HTML.

Prerequisites
  • Skill cloned — git clone https://github.com/JuliaGenAI/julia-agent-skills ~/.claude/skills/julia-agent-skills
  • Julia ≥ 1.10 installed — juliaup default release
Flow
  1. Ask the skill to scaffold docs
    Use documenter-vitepress skill — set up DocumenterVitepress.jl docs for MyPackage.jl.✓ Copied
    → Claude creates docs/ with Project.toml, make.jl, index.md configured for Vitepress
  2. Run the local preview
    Give me the exact commands to preview locally.✓ Copied
    → julia --project=docs docs/make.jl + npm dev server instructions
  3. Wire up CI
    Add GitHub Actions to deploy to gh-pages on main.✓ Copied
    → Standard Julia doc-deploy workflow YAML

Outcome: A working docs site you can extend.

Pitfalls
  • Version mismatch between DocumenterVitepress.jl and node/vitepress — Pin versions as the skill suggests; DocumenterVitepress releases move fast
Combine with: github

Iterate on docs theme and sidebar structure

👤 Maintainers unhappy with defaults ⏱ ~20 min intermediate

When to use: Docs work but the navigation / theme isn't landing.

Flow
  1. Describe the change
    documenter-vitepress — reorganize sidebar into Getting Started / Tutorials / API / Design sections.✓ Copied
    → Vitepress config diff matching Julia docs conventions
  2. Preview and tune
    Preview looks off on dark mode — fix the code-block contrast.✓ Copied
    → Specific CSS / theme override, not guessing

Outcome: Docs that actually match your package's story.

Combinations

Pair with other MCPs for X10 leverage

julia-agent-skill + github

Open a PR adding Vitepress docs to a Julia package

Scaffold the docs and open a PR to MyPackage.jl with the new docs/ and CI workflow.✓ Copied
julia-agent-skill + filesystem

Edit docs content alongside setup in one session

Set up DocumenterVitepress, then write index.md and Getting Started pages.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
scaffold_docs package name + basic info First-time docs setup 0
update_config desired change (sidebar, theme, plugin) Tuning existing Vitepress setup 0
ci_deploy repo + target branch (usually gh-pages) Automating deploys 0

Cost & Limits

What this costs to run

API quota
None
Tokens per call
Small — config + boilerplate
Monetary
Free — skills are local files
Tip
Docs work is modest context; no special budget needed.

Security

Permissions, secrets, blast radius

Credential storage: No credentials — pure prompts
Data egress: None

Troubleshooting

Common errors and fixes

Skill not invoked — Claude sets up plain Documenter.jl instead

Say 'use documenter-vitepress skill' explicitly.

Verify: ls ~/.claude/skills/julia-agent-skills/
SKILL.md frontmatter wrong

Check the documenter-vitepress subfolder.

Verify: head ~/.claude/skills/julia-agent-skills/documenter-vitepress/SKILL.md
Wrong trigger keywords — plain Documenter.jl output

'Vitepress' is the key word; without it, Claude will default to HTML Documenter.

Alternatives

julia-agent-skills vs others

AlternativeWhen to use it insteadTradeoff
Plain Documenter.jlYou want the classic Julia docs look with no JS build stepLess modern UI, simpler setup
VitePress hand-rolledNon-Julia projectNo Julia package integration (doctests, @docs blocks)

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills