ilml-plugin-linkedin 1.2.1 → 1.3.0

package/CHANGELOG.md

@@ -0,0 +1,39 @@
+# Changelog
+
+## 1.3.0
+- **Behavior change — LinkedIn session cookies now live in the active ilml scope** instead of in the plugin install directory. New path: `<scope>/.ilivemylife/plugins-state/linkedin/cookies.json` (production) / `./cookies.json` next to `ilml-plugin.json` (dev mode, unchanged). This means:
+  - `ilml plugin update linkedin` no longer wipes your LinkedIn session — sessions survive plugin updates
+  - `ilml logout` correctly clears the LinkedIn session in that scope (alongside other user-tied data)
+  - Different ilml login scopes (e.g. global vs `--local` per project) hold separate LinkedIn sessions — useful for multiple LinkedIn accounts
+  - **One-time:** after upgrading to 1.3.0, run `ilml linkedin login` once. The old session was inside the install dir which got wiped by the upgrade
+- README rewritten with marketing-first framing — leads with what users *get* (your LinkedIn data finally yours, AI-assisted messaging, terminal-first automation, Easy Apply that actually thinks) before diving into install/configure
+- New section: **Save AI tokens — tune the node settings** — explains how to use `ilml editSettings` to set `intelligence: disabled` (cheaper model) and `rootAccess: disabled` (skip whole-graph context lookup) on the Easy Apply node to control token spend
+- Improved **Where things live** table — clearer per-row "wiped on plugin update?" / "wiped on `ilml logout`?" columns; explicitly highlights that `DATA_DIR` survives both
+- Internal: new `src/cookiesStore.mjs` is the single source of truth for cookie path resolution. All cookie readers/writers in published entries (`src/browser.mjs`, `src/saveLoginState.mjs`, `run.mjs`, `funnelRunner.mjs`) go through it. SDK and CLI APIs unchanged
+
+## 1.2.2
+- README polish based on real-user feedback:
+  - Cleaner top — removed the metadata bullet list (npm/tracker/license) that was the very first thing visitors saw on the npm page; now opens straight into "What it does"
+  - Removed the entire `Developer Notes` section — it was internal-only and not useful for end users (release process and architecture notes live in `CLAUDE.md` and the SDK's plugin spec)
+  - Clarified the `LINKEDIN_SEARCH_URL` instruction (no more raw URL parameters like `f_AL=true` — just "open LinkedIn → Jobs, set filters, copy URL")
+  - New **Author & contact** section with personal page, LinkedIn, and a **DigitalTwins.team** call-to-action for custom plugin development
+- `CHANGELOG.md` is now shipped in the npm tarball (added to `package.json#files`), so the npm package page renders release notes next to the README
+- New **Feedback & support** section in the README pointing at a dedicated **Support** node in iLiveMyLife (`0000019dde81b04f-2e534bb8ebad0000`) — users can write directly to the maintainer via the in-graph messenger or `ilml send` from the terminal
+
+## 1.2.1
+- Documentation overhaul — `README.md` rewritten in English, split into **User Guide** (install, configure, run, update) and **Developer Notes** (release process, architecture, security checklist)
+- Removed outdated `.env`-based user instructions — the plugin is now fully self-configuring via `ilml plugin install linkedin` + first-run prompts (or `ilml plugin config linkedin set KEY VALUE`)
+- Added `CHANGELOG.md` (this file)
+- Added `CLAUDE.md` — project-level guide for the AI assistant covering release process and key architecture pointers
+- Added a `Releases` node in the iLiveMyLife graph for in-app release notifications
+
+## 1.2.0
+- First public publish on npm as `ilml-plugin-linkedin`
+- `src/config.mjs` refactored to use `getPluginConfig()` from `@ilivemylife/graph-sdk` v1.0.17
+  - Resolved configuration is merged into `process.env` so the rest of the codebase (16+ files reading `process.env.X`) keeps working unchanged
+  - The manual `LINKEDIN_NAME` bootstrap check is removed — schema validation in the SDK handles it
+  - Works in both **production** (`ilml linkedin <command>`) and **development** (`node run.mjs` with `.env` next to manifest), without any code changes between modes
+- Bumped `@ilivemylife/graph-sdk` peer to `^1.0.17`
+- `package.json` polish for npm publish — `author`, `license: UNLICENSED`, `keywords`, strict `files: ["dist", "ilml-plugin.json"]` whitelist
+- `ilml-plugin.json` declares config via `config.sections[].fields[]` (richer manifest format supported by SDK 1.0.17): grouped fields with `label`, `hint`, types (`text`, `secret`, `path`, `nodeId`, `url`, `number`, `boolean`)
+- All sensitive files (`.env`, `cookies.json`, raw sources, internal handoff docs, runtime data) excluded from the npm tarball via `.npmignore`

package/README.md

@@ -1,33 +1,26 @@
-# ilml-plugin-linkedin
+# Your LinkedIn — finally yours
 
-LinkedIn job-search and networking automation as a plugin for the [`ilml`](https://www.npmjs.com/package/@ilivemylife/graph-sdk) CLI.
+LinkedIn keeps your **connections, conversations, and the notes you write about people** locked inside their interface. You can't export message threads. You can't query an AI on your own contact history. You can't run batch operations from a script. You can't keep a personal database of who said what when.
 
-- **npm:** https://www.npmjs.com/package/ilml-plugin-linkedin
-- **Tracker / Releases (in iLiveMyLife):** open the **Releases** node inside the **LinkedIn Automation** project in your iLiveMyLife app
-- **License:** UNLICENSED — all rights reserved
+This plugin pulls all of that onto your machine and into your [iLiveMyLife](https://ilivemylife.io) knowledge graph — where it's searchable, syncable, AI-queryable, and yours to keep forever. Even if you uninstall the plugin or switch ilml accounts, **your accumulated data stays where you put it**.
 
----
-
-## What it does
+It also automates LinkedIn from the terminal — applying to jobs, drafting outreach, processing recruiter funnels — so you can script what LinkedIn's web UI makes you do one click at a time.
 
-A toolkit that drives LinkedIn from your machine via a real browser (Puppeteer + stealth), with results synced into your [iLiveMyLife](https://ilivemylife.io) knowledge graph:
+---
 
-- **Easy Apply** — auto-fills and submits LinkedIn job applications. The graph's AI assistant (**Lifebot**) reads your profile node to answer custom application questions in your voice.
-- **Inbox sync** — scans LinkedIn messages, detects changes, and mirrors threads into your graph.
-- **Message bot** — draft → review → send batch messaging workflow (you approve before anything is sent).
-- **Connection funnel** — process recruiter / founder / investor profiles in batches (connect, skip, message).
-- **Scout** — find jobs without applying; reports back which match your filters.
-- **Profile activity** — track who viewed your profile, who you visited, etc.
+## What you get
 
-All persistent data (job DB, profile DB, conversation history, cookies) is stored locally in a directory you choose — never in a cloud you don't control.
+- **A full local mirror of your LinkedIn graph.** Connections, conversation threads, message history, profile metadata, your private notes about people — synced into your iLiveMyLife graph and a local database. Nothing stays trapped in linkedin.com.
+- **AI-assisted messaging.** [Lifebot](https://ilivemylife.io) reads the full context of each thread (history, your notes, tags) and helps you draft replies in your voice. No copy-pasting into ChatGPT, no losing context, no generic templates.
+- **Terminal-first automation.** Batch operations — apply to dozens of jobs at once, draft 50 outreach messages then review them all in one pass, run a connection campaign on a schedule. Scriptable. Re-runnable. Logged.
+- **Easy Apply that actually thinks.** Auto-fills LinkedIn job applications, with Lifebot answering custom questions ("Why are you interested in this role?") in your voice using context from your graph — not boilerplate.
+- **Your data outlives the plugin.** The connection database, conversation history, and your notes live in a directory **you** choose (`DATA_DIR`). Plugin updates don't wipe them. Logging out of ilml doesn't wipe them. Uninstalling the plugin doesn't wipe them. Only **you** decide when they go.
 
 ---
 
-# User Guide
-
 ## Prerequisites
 
-- **Node.js 18+** — [download](https://nodejs.org/) (the Long-Term Support version is fine).
+- **Node.js 18+** — [download](https://nodejs.org/) (the LTS version is fine).
 - **iLiveMyLife account** — free signup at [iLiveMyLife.io](https://ilivemylife.io).
 - **LinkedIn account** — your personal one.
 
@@ -48,9 +41,9 @@ ilml login
 ilml plugin install linkedin
 ```
 
-That's the whole install. The bare-name `linkedin` resolves to `npm:ilml-plugin-linkedin` via the ilml plugin convention. The CLI downloads the latest version from npm, extracts it under `~/.ilivemylife/plugins/linkedin/`, and runs `npm install` for its runtime dependencies (mainly Puppeteer's bundled Chromium — first install takes a couple of minutes).
+The bare-name `linkedin` resolves to `npm:ilml-plugin-linkedin` via the ilml plugin convention. The CLI downloads the latest version from npm, extracts it under `~/.ilivemylife/plugins/linkedin/`, and runs `npm install` for runtime dependencies (mainly Puppeteer's bundled Chromium — first install takes a couple of minutes).
 
-Verify it's installed:
+Verify:
 
 ```bash
 ilml plugin list
@@ -59,7 +52,7 @@ ilml linkedin
 
 ## Configure
 
-The plugin needs a few things to know who you are and where to log activity. The first time you run any `ilml linkedin <command>`, the CLI will prompt you for the **required** fields. You can also pre-configure:
+The first time you run `ilml linkedin <command>`, the CLI will prompt for required fields. You can also pre-configure:
 
 ```bash
 ilml plugin config linkedin set LINKEDIN_NAME "Your Full Name"
@@ -67,18 +60,16 @@ ilml plugin config linkedin set NODE_EASY_APPLY_MAIN <node-id>
 ilml plugin config linkedin set NODE_EASY_APPLY_ERRORS <node-id>
 ```
 
-To inspect (secret values are masked):
-
+Inspect (secrets masked):
 ```bash
 ilml plugin config linkedin
 ```
 
-To change a value later or remove one:
-
+Change later or wipe:
 ```bash
 ilml plugin config linkedin set LINKEDIN_NAME "New Name"
 ilml plugin config linkedin unset OPTIONAL_KEY
-ilml plugin config linkedin reset                      # wipe all; will re-prompt next run
+ilml plugin config linkedin reset                  # re-prompt on next run
 ```
 
 ### Configuration fields
@@ -86,15 +77,15 @@ ilml plugin config linkedin reset                      # wipe all; will re-promp
 | Section | Field | Required | What it is |
 |---|---|---|---|
 | LinkedIn account | `LINKEDIN_NAME` | yes | Your full name **exactly** as it appears on LinkedIn (used to identify your own messages in threads). |
-| | `LINKEDIN_LOGIN` | no | LinkedIn email — only used for auto-fill during one-time login. |
-| | `LINKEDIN_PASS` | no, secret | LinkedIn password — only used for auto-fill during one-time login. Stored locally on disk; never sent anywhere. |
+| | `LINKEDIN_LOGIN` | no | LinkedIn email — only used for auto-fill during one-time browser login. |
+| | `LINKEDIN_PASS` | no, secret | LinkedIn password — auto-fill only. Stored locally on disk; never sent anywhere. |
 | iLiveMyLife integration | `NODE_EASY_APPLY_MAIN` | yes | Node ID where job applications are tracked. See "Setting up your graph" below. |
 | | `NODE_EASY_APPLY_ERRORS` | yes | Node ID where Easy Apply errors are logged. |
 | | `NODE_RUN_REPORTS` | no | Node ID where end-of-session summaries are posted (enable notifications on it to get pings when long jobs finish). |
-| Data storage | `DATA_DIR` | no | Absolute path to a directory for the local DB / cookies. **Recommended** — keeps data outside the plugin install folder so it survives plugin updates. |
+| Data storage | `DATA_DIR` | no | Absolute path to a directory for your local databases (connections, conversations, profile cache). **Strongly recommended** — keeps your accumulated data outside the plugin install folder so it survives plugin updates, ilml logout, and reinstalls. |
 | Apply bot | `City` | no | Default city for filters. Default: `Toronto`. |
 | | `MAX_APPLY_FOR_RUN` | no | Stop after this many applications per run. Default: `50`. |
-| | `LINKEDIN_SEARCH_URL` | no | Default LinkedIn jobs search URL with your filters (use `f_AL=true` for Easy Apply). |
+| | `LINKEDIN_SEARCH_URL` | no | Default LinkedIn jobs search URL. Open LinkedIn → Jobs, set your filters, make sure Easy Apply is on, copy the resulting URL from the address bar. |
 | Scouting | `LINKEDIN_SCOUT_URLS` | no | Comma-separated job search URLs to scan without applying. |
 | Resume / CV | `CV_TEXT`, `RESUME_PDF_URL`, `RESUME_FILENAME` | no | CV snippet, public PDF URL, suggested filename. Used in messages to recruiters. |
 | Funnel | `FUNNEL_USE_CUSTOM_MESSAGE` | no | Send a custom note with connection requests. Default: `false`. |
@@ -129,9 +120,27 @@ The Easy Apply bot uses iLiveMyLife's AI assistant (**Lifebot**) to answer custo
 
 7. Create a sibling node titled **"Easy Apply Errors"** (no AI needed). Copy its ID and set it: `ilml plugin config linkedin set NODE_EASY_APPLY_ERRORS <id>`.
 
+### Save AI tokens — tune the node settings
+
+Lifebot uses AI tokens for every form question it answers. Two settings on the Easy Apply node let you tune cost vs. quality without touching the plugin:
+
+```bash
+# Use a cheaper, faster AI model (good enough for filling forms):
+ilml editSettings <NODE_EASY_APPLY_MAIN> --intelligence disabled
+
+# Skip whole-graph context lookup — just use this node's description:
+ilml editSettings <NODE_EASY_APPLY_MAIN> --rootAccess disabled
+```
+
+`intelligence: disabled` switches Lifebot to a cheaper model (think GPT-3.5 / Claude Haiku tier instead of GPT-4 / Claude Opus). For application form filling, the cheap model is usually fine — questions are mechanical.
+
+`rootAccess: disabled` stops Lifebot from searching your entire knowledge graph for context every time it answers. The Easy Apply node's description and child nodes already have everything Lifebot needs — extra context costs tokens for no benefit.
+
+To switch back: pass `--intelligence enabled` or `--rootAccess enabled`. To reset to your account default: pass `null`.
+
 ## First-time LinkedIn login
 
-LinkedIn requires an authenticated session, so a one-time browser login is needed. Run:
+LinkedIn requires an authenticated browser session, so a one-time login is needed:
 
 ```bash
 ilml linkedin login
@@ -139,6 +148,12 @@ ilml linkedin login
 
 A real browser window opens. Sign in to LinkedIn (manually solve any captcha or 2FA). When you see your feed, close the window — your session cookies are saved locally for future runs.
 
+Sessions live in your active ilml scope (`<scope>/.ilivemylife/plugins-state/linkedin/cookies.json`), so:
+
+- Different ilml scopes (e.g. `ilml login` globally vs `ilml login --local` in a project folder) keep **separate** LinkedIn sessions — useful if you have multiple LinkedIn accounts.
+- Plugin updates do **not** wipe your session — you don't need to re-login after `ilml plugin update linkedin`.
+- `ilml logout` does wipe the session in that scope (alongside other user-tied data) — clean handoff between users on a shared machine.
+
 ## Daily commands
 
 | Command | What it does |
@@ -156,11 +171,11 @@ A real browser window opens. Sign in to LinkedIn (manually solve any captcha or
 | `ilml linkedin daily` | Compound routine combining several commands. |
 | `ilml linkedin login` | Re-save LinkedIn cookies after a session expires. |
 
-Run `ilml linkedin` (no subcommand) to see the list anytime.
+Run `ilml linkedin` (no subcommand) any time to see the list.
 
 ## Updating
 
-Updates ship via npm. The CLI checks the registry and only downloads when there's a newer version:
+Updates ship via npm. The CLI checks the registry and only downloads when a newer version is actually available:
 
 ```bash
 ilml plugin update linkedin    # check this plugin
@@ -169,20 +184,27 @@ ilml update                    # update the SDK and all plugins together
 ```
 
 You'll see one of:
-- `linkedin: already on latest version (1.2.1)` — nothing downloaded
-- `linkedin: 1.2.1 → 1.3.0` followed by re-install — newer version pulled
+- `linkedin: already on latest version (1.3.0)` — nothing downloaded
+- `linkedin: 1.3.0 → 1.3.1` then re-install — newer version pulled
 
-Your saved configuration is preserved across updates (it lives outside the install dir). If a new version requires a new field, the next run will prompt you for just the new field.
+**Your config and your data both survive updates.** Only the plugin code dir gets refreshed; everything user-tied lives elsewhere.
 
-## Where data lives
+## Where things live
 
-| Path | What's there | Survives plugin update? | Cleared by `ilml logout`? |
+| Path | What's there | Wiped on plugin update? | Wiped on `ilml logout`? |
 |---|---|---|---|
-| `~/.ilivemylife/plugins/linkedin/` | Plugin code (re-extracted on update) | Replaced | No |
-| `~/.ilivemylife/plugins-state/linkedin.json` (or per-project local) | Your configured values | Yes | Yes (with that scope) |
-| Directory you set as `DATA_DIR` | Local DBs, cookies, scraped profiles | Yes | No (you manage it) |
+| `~/.ilivemylife/plugins/linkedin/` | Plugin code | yes (re-extracted) | no |
+| `<scope>/.ilivemylife/plugins-state/linkedin.json` | Your configured values (LINKEDIN_NAME, node IDs, etc.) | no | yes (with that scope) |
+| `<scope>/.ilivemylife/plugins-state/linkedin/cookies.json` | LinkedIn session cookies | no | yes (with that scope) |
+| Directory you set as `DATA_DIR` | Local DBs, scraped profiles, message history, your notes | **no** | **no** |
+
+If you didn't set `DATA_DIR`, runtime data files default to inside the plugin's install dir — meaning a plugin reinstall **wipes them**. Setting `DATA_DIR` to a sibling folder like `~/linkedin-plugin-data/` is **strongly recommended**:
 
-If you didn't set `DATA_DIR`, data files default to inside the plugin's install dir — meaning a plugin reinstall wipes them. Setting `DATA_DIR` to a sibling folder like `~/linkedin-plugin-data/` is strongly recommended.
+```bash
+ilml plugin config linkedin set DATA_DIR /absolute/path/to/your/linkedin-data
+```
+
+Once set, you can sync `DATA_DIR` to a backup drive, a cloud folder, or another machine — the data is plain SQLite-style JSON, fully portable.
 
 ## Removing the plugin
 
@@ -190,113 +212,37 @@ If you didn't set `DATA_DIR`, data files default to inside the plugin's install
 ilml plugin remove linkedin
 ```
 
-This wipes the install dir. To also clear your saved configuration in the active scope:
-
+This wipes the install dir. Your config in the active scope:
 ```bash
 ilml plugin config linkedin reset
 ```
 
-To clean up the data directory (cookies, DBs), delete the folder you set as `DATA_DIR` manually.
+The data in `DATA_DIR` is yours — delete the folder manually if you want it gone, or keep it.
 
 ---
 
-# Developer Notes
-
-> Single-developer project. The reference for plugin architecture and SDK contracts is the iLiveMyLife graph-sdk repo's [`PLUGINS.md`](https://github.com/iLiveMyLife/graph-sdk.iLiveMyLife.io/blob/main/PLUGINS.md). Most of what follows is just reminders for me when I come back to this in a few months.
-
-## Layout
+## Feedback & support
 
-```
-ilml-plugin.json     # manifest: name, version, commands, config.sections[].fields[]
-package.json         # npm metadata; "files": ["dist", "ilml-plugin.json"] is the publish whitelist
-.npmignore           # belt-and-suspenders excludes (.env, cookies.json, sources, etc.)
-.env / .env.example  # dev only; gitignored
-
-run.mjs / syncAll.mjs / messageBot.mjs / scout.mjs / ...  # entry points (one per ilml subcommand)
-src/
-  config.mjs         # reads via SDK getPluginConfig(); merges into process.env so the rest of the codebase keeps using process.env.X
-  graphClient.mjs    # SDK client wrapper
-  database.mjs       # local JSON DB at DATA_DIR
-  saveLoginState.mjs # entry: ilml linkedin login
-  ... domain modules ...
-scripts/
-  build-plugin.mjs   # esbuild bundler — outputs dist/*.mjs (minified, no sourcemaps)
-                     # externalizes: puppeteer, dotenv, @ilivemylife/graph-sdk
-```
-
-## Configuration model
-
-- The plugin reads its config **only** through `getPluginConfig()` from `@ilivemylife/graph-sdk` (called once in `src/config.mjs`).
-- Resolved values are merged into `process.env` so existing files reading `process.env.LINKEDIN_NAME` etc. keep working unchanged. New code should read directly from the SDK return value when feasible.
-- Auth token: `process.env.ILML_TOKEN` — injected by ilml CLI in production; resolved by the SDK in dev (local config / `.env` / global config / env var).
-- Active scope dir: `process.env.ILML_SCOPE_DIR` — set in production only. Plugin code never reads it directly; the SDK does.
-
-## Two run modes
-
-| Mode | How invoked | Where config comes from |
-|---|---|---|
-| **Production** | `ilml linkedin <command>` | The active ilml scope's `<scope>/.ilivemylife/plugins-state/linkedin.json` |
-| **Dev** | `node run.mjs` (etc.) | `.env` next to `ilml-plugin.json` (auto-detected by SDK) |
-
-The plugin code is identical between the two. `ILML_SCOPE_DIR`'s presence is the only signal.
-
-## Local dev iteration
-
-When the plugin code itself is what's changing:
-
-```bash
-# 1. (optional) edit ilml-plugin.json or src/*
-# 2. Build
-npm run build:plugin
-
-# 3a. Quick check via direct run (uses .env)
-node run.mjs
+Bug reports, feature requests, and general questions land in the plugin's **Support** node inside iLiveMyLife. Send a message there and we'll get back to you:
 
-# 3b. Full check via ilml CLI — needs the plugin re-packed and re-installed
-npm pack
-ilml plugin install linkedin file:///$(pwd)/ilml-plugin-linkedin-X.Y.Z.tgz
-ilml linkedin <command>
-```
-
-When the **SDK** is what's changing alongside, also rebuild and re-install the SDK from the sibling `graph-sdk.iLiveMyLife.io` repo:
-
-```bash
-# In ../graph-sdk.iLiveMyLife.io
-npm run build && npm pack
-
-# In this repo
-npm install ../graph-sdk.iLiveMyLife.io/ilivemylife-graph-sdk-X.Y.Z.tgz --no-save
-npm run build:plugin
-```
+- In any iLiveMyLife app (web / mobile / desktop): open https://app.ilivemylife.io/item/0000019dde81b04f-2e534bb8ebad0000 and use the messenger panel
+- From the terminal: `ilml send 0000019dde81b04f-2e534bb8ebad0000 "your message"`
 
-## Release process
+## Links
 
-1. **Update `CHANGELOG.md`** — add an entry at the top describing what changed for users.
-2. **Bump version in BOTH** `package.json#version` AND `ilml-plugin.json#version`. They must match — `ilml plugin update` compares the manifest version against npm's `dist-tags.latest`. Drift here causes false update loops or silent skips.
-3. **Commit with explicit paths only:**
-   ```bash
-   git commit -- package.json ilml-plugin.json CHANGELOG.md <other-changed-files> -m "v1.X.Y: short description"
-   ```
-4. **Push:** `git push`.
-5. **Publish:** `npm publish --access public`. The `prepublishOnly` script runs `build:plugin` automatically — `dist/` is rebuilt from current sources before packing.
-6. **Update the Releases node in the graph** — sync description with the new CHANGELOG entry.
-
-## Security checklist before each `npm publish`
+- This plugin on npm: https://www.npmjs.com/package/ilml-plugin-linkedin
+- `ilml` CLI on npm: https://www.npmjs.com/package/@ilivemylife/graph-sdk
+- iLiveMyLife: https://ilivemylife.io
 
-- `npm pack --dry-run` — verify only `dist/`, `ilml-plugin.json`, `package.json`, `README.md` end up in the tarball (~13 files). No `.env`, `cookies.json`, `*.json` data files, source `.mjs` at the repo root, `node_modules/`, internal handoff `.md`, `tmpclaude-*`, `.git/`.
-- `grep -E "ilya|sorokin|password|token|@gmail" dist/*.mjs dist/src/*.mjs` — no real personal data should appear in bundled output. (Examples in `README.md` like `ivan@example.com` are fine — they're documentation placeholders.)
-- `ls dist/*.map dist/**/*.map 2>/dev/null` — must return nothing (no sourcemaps).
-- `npm whoami` — confirm correct npm account before publish.
+---
 
-## Useful pointers
+## Author & contact
 
-- iLiveMyLife graph-sdk Plugin spec & 12 architecture rules: [`PLUGINS.md`](https://github.com/iLiveMyLife/graph-sdk.iLiveMyLife.io/blob/main/PLUGINS.md)
-- SDK source: https://github.com/iLiveMyLife/graph-sdk.iLiveMyLife.io
-- This plugin on npm: https://www.npmjs.com/package/ilml-plugin-linkedin
-- ilml CLI on npm: https://www.npmjs.com/package/@ilivemylife/graph-sdk
+**[Ilya Sorokin](https://www.digitaltwins.team/team/ilya-sorokin)** — creator of [iLiveMyLife.io](https://ilivemylife.io) and this plugin.
 
----
+- LinkedIn: [linkedin.com/in/ilyasorokin](https://www.linkedin.com/in/ilyasorokin/)
+- Email: info@ilivemylife.io
 
-## Author
+### Need a custom plugin or extension?
 
-Ilya Sorokin · [iLiveMyLife.io](https://ilivemylife.io) · info@ilivemylife.io
+[**DigitalTwins.team**](https://www.digitaltwins.team/) — my consulting company — designs and builds custom automation, SDK extensions, and bespoke plugins for the iLiveMyLife ecosystem (and beyond). If you want to integrate your own workflow with iLiveMyLife, extend this plugin's behavior, or commission something new, get in touch.