easypaper-setup-environment

Use this skill when the plugin is first installed or when environment setup is needed.

Setup Workflow

1. Check Python Environment

• Detect if uv is available (preferred) or python/python3
• If uv is available, use it to create an isolated virtual environment
• If not, check for venv or virtualenv and create a virtual environment
• Environment should be created in a project-local directory (e.g., .venv or .easypaper-env)

2. Install EasyPaper Package

• If uv is available:

  uv venv .easypaper-env
  source .easypaper-env/bin/activate  # or .easypaper-env/Scripts/activate on Windows
  uv pip install -e .  # if in repo root
  # OR
  uv pip install easypaper[server]  # if installing from PyPI
  

• If using standard Python:

  python -m venv .easypaper-env
  source .easypaper-env/bin/activate
  pip install -e .  # or pip install easypaper[server]
  

3. Check LaTeX Installation

• Check for LaTeX distribution:
  • On macOS: Check for pdflatex command, suggest brew install --cask mactex or brew install basictex
  • On Linux: Check for pdflatex, suggest sudo apt-get install texlive-full or texlive-base
  • On Windows: Check for pdflatex, suggest installing MiKTeX or TeX Live
• Verify installation by running: pdflatex --version
• If not installed, provide clear installation instructions for the user's OS

4. Create or Validate Configuration

• Check for an existing EasyPaper YAML config in this order:
  • User-provided path in the conversation
  • AGENT_CONFIG_PATH
  • ./easypaper_config.yaml
  • ./configs/openrouter.yaml
  • ./configs/example.yaml
• If no usable config exists, create ./easypaper_config.yaml from the bundled sibling template file config.example.yaml.
• The bundled config.example.yaml must stay byte-for-byte synchronized with the repository source template configs/example.yaml; do not hand-write a partial config in this skill.
• After creating the file, ask the user for the required LLM API key/provider value and replace only the placeholder values they explicitly provide (for example YOUR_OPENROUTER_KEY). Do not invent credentials.
• Keep the generated config path explicit for later SDK calls, either by using EasyPaper(config_path="<absolute path to easypaper_config.yaml>") or by setting AGENT_CONFIG_PATH for commands that call load_config().
• The template enables the skills system. Users do not need a local ./skills folder: EasyPaper loads packaged built-in skills first, then overlays user skills from skills_dir when that directory exists.