菜单
"Use when extracting Overleaf login cookies from Chrome on macOS for the VSCode Overleaf Workshop extension. Decrypts Chrome's cookie store and outputs the session cookie in the exact format the extension expects. Triggers: "overleaf cookie", "overleaf login", "overleaf workshop cookie", "get overleaf cookie", "vscode overleaf login"
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when turning recent agent-session evidence into durable skill updates. Triggers: "consolidate lessons", "update skills from sessions", "prevent repeated fixes", "recurring mistakes", "capture workflow learnings"
Use when running workloads on LUMI supercomputer, including GPU job submission, PyTorch with ROCm/AMD MI250X, container workflows, and LUMI-specific Slurm configuration. Triggers: "LUMI", "MI250X", "ROCm", "AMD GPU", "CSC", "LUMI-G"
Use when integrating W&B experiment tracking into ML training pipelines, including logging strategy, run configuration, and online/offline mode management. Triggers: "W&B", "wandb", "weights and biases", "experiment logging", "wandb.log", "wandb.init", "training dashboard"
Use when preparing to launch any remote or multi-GPU ML experiment. Triggers include "preflight", "sanity check", "launch validation", "before training", "GPU check", "dataset check", "environment check"
Use when pushing changes in a repository that contains git submodules, especially when the submodule has its own commits that must not be left stranded. Triggers include "push", "git push", "submodule", "commit submodule", "workspace push"
Use when evaluating academic papers or surveying a research topic. Gathers venue, citations, GitHub stats, social buzz, reproducibility, and author signals to produce a scored markdown report. Triggers: "evaluate paper", "paper review", "research survey", "literature review", "is this paper good", "find papers on", "compare papers", "paper impact"
| name | overleaf-cookie |
| description | "Use when extracting Overleaf login cookies from Chrome on macOS for the VSCode Overleaf Workshop extension. Decrypts Chrome's cookie store and outputs the session cookie in the exact format the extension expects. Triggers: "overleaf cookie", "overleaf login", "overleaf workshop cookie", "get overleaf cookie", "vscode overleaf login" |
overleaf_session2 cookie string without manually opening DevToolsbrowser_cookie3 installed (pip install browser_cookie3)python skills/apps/overleaf-cookie/scripts/get_overleaf_cookie.py
Output:
overleaf_session2=s:XXXXXXXXXXXX.XXXXXXXXXXXX
Copy the entire line and paste it into VSCode → Overleaf Workshop: Login with Cookies → Server: https://www.overleaf.com.
Chrome encrypts cookies using AES-128-CBC (v10) or AES-256-GCM (v11) on macOS. The encryption key lives in the macOS Keychain under "Chrome Safe Storage". The browser_cookie3 library handles the keychain access and decryption automatically.
The script:
~/Library/Application Support/Google/Chrome/Default/Cookiesoverleaf_session2 on .overleaf.comname=value stringThe Overleaf Workshop extension's cookiesLogin() method parses the /project page HTML to extract user-id, user-email, and csrf-token from <meta> tags. Overleaf renamed these tags:
| Old (extension expects) | New (Overleaf serves) |
|---|---|
name="user-id" | name="ol-user_id" |
name="user-email" | name="ol-usersEmail" |
name="csrf-token" | name="ol-csrfToken" |
This causes "Failed to get User ID" even with a perfectly valid cookie. The cookie itself is correct — the extension's regex is outdated.
Workarounds:
out/api/base.js (or src/api/base.ts) to match the new ol-* meta tag namesiamhyc/Overleaf-Workshopcurl or wget to test the cookie — Overleaf's /project endpoint returns different HTML to non-browser user-agents, making verification unreliablebrowser_cookie3 documentation for cross-platform cookie extraction