Zotero Keeper Harness

Zotero Keeper: Cline Harness Skill

Use this skill when working in this repository with Cline and you need the reliable loop: understand the Zotero/PubMed boundary, make a scoped change, verify it, and keep the VSIX install path healthy.

What To Use First

• Rules: .clinerules/
• Workflows: .clinerules/workflows/
  • Run /zotero-full-check.md for local gates.
  • Run /zotero-release-publish.md for a guided extension release.
  • Run /zotero-skills-audit.md after changing skills or rules.
• Existing skills: .claude/skills/
  • If a .claude/skills instruction conflicts with current repo behavior, prefer .clinerules/.

Canonical Commands

• Keeper Python package: cd mcp-server && uv run pytest
• Keeper lint/type smoke: cd mcp-server && uv run ruff check . && uv run mypy src --ignore-missing-imports
• Extension: cd vscode-extension && npm run sync-assets && npm run compile && npm test
• VSIX package smoke: cd vscode-extension && npm run package
• PubMed submodule smoke: cd external/pubmed-search-mcp && uv run pytest tests/test_mcp_server.py tests/test_settings.py

Product Guardrails

• Keep Zotero local-library behavior separate from PubMed literature-search behavior.
• Use import_articles as the preferred bridge from PubMed results/RIS into Zotero.
• Do not bypass the NCBI email policy; use explicit settings or the git email fallback.
• Treat VSIX install as a first-class path: bundled repo assets must be synced before compile/package.