install.md — Weekly LinkedIn analytics agent installer A developer has created an installer for a weekly LinkedIn analytics agent that runs as a Cowork scheduled task. The agent opens LinkedIn analytics via the Claude in Chrome extension, exports data, parses the resulting xlsx file, writes a snapshot to the user's project folder, and sends a digest in chat. The installer guides users through prerequisite checks and customization questions before setting up the project folder structure and template files. You are an installer. Read this file end-to-end, then guide the user through setting up a weekly LinkedIn analytics agent. Be conversational and efficient — this should take 2-3 messages back and forth. The user has just told you something like "install this for me" or "follow install.md and set up the LinkedIn analytics workflow". Treat that as the trigger. Don't make them re-read what's below — you do the reading, you do the work. A Cowork scheduled task that, once a week, opens LinkedIn analytics via the Claude in Chrome extension, clicks Export, parses the resulting xlsx, writes a snapshot file to the user's project folder, and sends them a digest in chat. Three parts: a scheduled prompt, a connected-folder pair ~/Downloads + the user's project folder , and the Claude in Chrome extension. No code, no third-party automation tools. Ask the user in one message all three at once : Before I install this, three quick checks: - Is ~/Downloads connected to Cowork as a project folder? Settings → Connected folders - Do you have a project folder where the analytics should live, also connected to Cowork? - Is Claude in Chrome extension installed, and is Chrome currently logged into your LinkedIn account? If any of these is "no", let me know which one and I'll explain how to set it up. If any answer is "no" — pause, explain that specific prerequisite, wait for confirmation, then re-ask the missing items. Do not proceed to Step 1 until all three are confirmed. Once prerequisites are confirmed, ask in one message all three questions at once : Three questions to customize the agent for your setup: Project folder path— the absolute path where analytics snapshots and post files should live. Example: ~/Documents/Projects/LinkedinAnalytics Schedule— when should the agent fire? Examples: Monday 12:00 , Friday 17:00 , Sunday 20:00 Digest language— what language for the chat digest? English , Russian , your choice Store the answers as: ${PROJECT FOLDER} — absolute path string ${SCHEDULE} — day-of-week + time, to be converted to cron in Step 4 ${LANGUAGE} — language name string If the user gives partial answers, ask follow-ups for the missing values before continuing. Run silently. Don't narrate to the user — just confirm at the end with a one-line summary if anything was created. mkdir -p "${PROJECT FOLDER}" mkdir -p "${PROJECT FOLDER}/analytics/snapshots" mkdir -p "${PROJECT FOLDER}/analytics/posts" The weekly prompt references three context files in Step 2 and updates them in Step 4. Create empty templates for each, only if the file does not already exist . Do not overwrite an existing file. ${PROJECT FOLDER}/analytics/themes and patterns.md : Themes and patterns Observed patterns across posts. Evidence-driven only — add an entry only when 2+ posts confirm a pattern or a single datapoint contradicts an existing one. Patterns populated by weekly analysis over time ${PROJECT FOLDER}/analytics/idea bank.md : Idea bank Post ideas queued for future. Append at next free . Never renumber. | | status | idea | rationale | |---|---------|------|-----------| ${PROJECT FOLDER}/analytics/follow ups.md : Follow-ups Dated watch list. Add items when a post needs a re-check e.g., "promising at 72h, re-check at 7d" . Move resolved items to the Resolved section — don't delete. Active Resolved ${PROJECT FOLDER}/linkedin analytics.md INDEX : LinkedIn analytics — INDEX Curated map of this project. Keep under 10KB. Latest snapshots populated by weekly analysis Active follow-ups populated by weekly analysis File map - analytics/snapshots/ — one .md per week - analytics/posts/ — one .md per post - analytics/themes and patterns.md — observed patterns - analytics/idea bank.md — post idea queue - analytics/follow ups.md — dated watch list Confirm to the user with a single line: "Project structure ready at ${PROJECT FOLDER} — analytics/ subfolders created, knowledge-base templates added." Skip mentioning any file that already existed and wasn't touched. Check if ${PROJECT FOLDER}/CLAUDE.md already exists. If it exists: skip this step entirely. If it doesn't exist , ask the user: You don't have a CLAUDE.md with your rules yet. The scheduled prompt references it — thresholds for breakout/underperformed posts, voice rules, file conventions. Want me to create a starter template you can adapt later? yes / no If yes : write the template from the CLAUDE.md template section at the bottom of this file to ${PROJECT FOLDER}/CLAUDE.md . Confirm to the user: "Created ${PROJECT FOLDER}/CLAUDE.md — edit it later to tune thresholds and voice rules." If no : skip, but flag to the user that they'll need to either edit Step 0 of the scheduled prompt remove the Read CLAUDE.md line or create the file later. Use Cowork's create scheduled task tool with these arguments: Name: Weekly LinkedIn analytics Description: Auto-export LinkedIn analytics, parse weekly metrics, write snapshot + digest. Schedule cron expression : convert ${SCHEDULE} to standard cron format. Examples: Monday 12:00 → 0 12 1 Tuesday 09:00 → 0 9 2 Friday 17:00 → 0 17 5 Sunday 20:00 → 0 20 0 Prompt: take the entire text inside the fenced block in the Prompt body section at the bottom of this file. Before passing it to the tool, do two find-replace operations on the string:- Replace every occurrence of ~/Projects/LinkedinAnalytics/ with ${PROJECT FOLDER} be careful with trailing slashes - Replace Russian, no fluff with ${LANGUAGE}, no fluff - Replace every occurrence of Verify the scheduled task created successfully before moving on. Tell the user: Installed. Scheduled task Weekly LinkedIn analytics is set to fire ${SCHEDULE} . Want me to run it once now as a dry-run, to verify everything works end-to-end? yes / no If yes : trigger the task immediately via Cowork's run-now mechanism. Surface anything that fails no Chrome, wrong path, missing folder mount . If the dry-run succeeds, the user should see a chat digest within ~30-90 seconds. If no : stop. Tell them the agent will fire at the scheduled time and they'll see the digest then. User says they don't want CLAUDE.md and don't want to edit the prompt — write a minimal CLAUDE.md anyway with Hard rules: TODO as a placeholder, so the Read CLAUDE.md line doesn't fail. Tell the user. User's schedule answer is ambiguous e.g., just Monday — ask for a specific time before generating cron. User wants to schedule more than once a week — that's outside this installer's scope, but you can offer: "This installer sets one weekly run. If you want daily or multiple times per week, I can adjust the cron after — just let me know what cadence." User wants the digest in multiple languages — pick the primary language for the prompt, mention they can edit Step 5 of the scheduled prompt later to add a translation pass. Write this exact content to ${PROJECT FOLDER}/CLAUDE.md : LinkedIn analytics — hard rules These are the project-level rules the weekly analytics agent follows. Tune to your taste. Thresholds - Breakout: impressions ≥ 3,000 OR engagement rate ≥ 2% in first 72h - Underperformed: impressions < 1,000 OR engagement rate < 0.3% in first 72h - Normal: everything between - Promising: below 1K impressions but ER ≥ 1.5% at <72h with positive trajectory Voice rules - Hook in line 1, no warmup - Numbers over adjectives - Short paragraphs 1-3 lines - No "I'm excited to announce" energy - Banned constructions: "Not just X, but also Y", trailing -ing clauses, em-dashes as decoration File conventions - Snapshots: analytics/snapshots/YYYY-MM-DD.md - Posts: analytics/posts/YYYY-MM-DD