Jason Academic Writing

High-level: the skill appears to do what it says — an end-to-end academic writing pipeline that queries Semantic Scholar/CrossRef and sends manuscript content to an LLM for multi-role review and revisions. Before installing or running: - Review your OPENAI_BASE_URL and OPENAI_API_KEY policies: the pipeline sends full manuscript text to the external LLM; use an API key with appropriate scope and rotate/limit it if needed. Avoid using organization-wide keys if you have privacy concerns. - Check for a .env file in the working directory (or other directories that dotenv might load). The scripts call load_dotenv(), so local secrets in a .env could be read and used; remove or audit .env before running. - Inspect and test in an isolated environment (container or throwaway VM) because the skill writes files and makes network calls. - Be aware the code has brittle JSON-parsing of LLM outputs and at least one partially truncated/buggy function (review.py shows non-robust math and a truncated fallback) — expect runtime errors or unexpected reviewer outputs; plan to validate outputs manually. - If you will process unpublished or sensitive manuscripts, treat outputs and logs carefully: they are stored locally and may be transmitted to third-party APIs. If you want, I can point out the exact lines that call dotenv and where LLM outputs are parsed, or help you harden the scripts (e.g., remove load_dotenv, add explicit JSON-safe wrappers, sanitize/excerpt text sent to LLM).