Smithery's MCP Proxy and managed identity shut down on October 31. See what's changing
Set up, check, pause, upgrade or try Profile-Wrap...
Set up the Profile-Wrap workspace, check the machine, and keep it healthy. Work in stages: analyse the ask, look up before improvising, plan with file checkpoints, run, review against the request. Every stage leaves a file the next stage reads, so a stop resumes where it left off.
The command is profile-wrap (install with uv tool install profile-wrap, or from the release; check with profile-wrap --version).
Read references/compliance.md in this skill folder before anything else. This package uses
the official LinkedIn API only, through the user's own developer app. If a request conflicts with
it (logging in to LinkedIn, driving a browser against it, reading messages, sending invitations,
editing a profile, hiding automation), refuse that part and offer the draft-only alternative. If
the user offers a LinkedIn login secret, stop and tell them it is never needed, never stored and
never used.
| The user says | Do this |
|---|---|
| "show me", "try it", no LinkedIn app yet | profile-wrap init --demo (zero questions; fictional persona; a temp workspace) |
| "quick setup" | express path: the 7 questions of step 2, defaults for the rest |
| "set me up" | full path: all steps below |
| "doctor", "why did it fail" | profile-wrap doctor and explain each WARN or FAIL with its hint |
| "pause" | `profile-wrap pause [--posting |
| "upgrade", "new version" | see Upgrade |
Ask through direct questions, in batches of at most 4 questions, with options. Never leave a
question as prose. The exact questions, options and the mapping to the answers file are in
references/questions.md. After every batch, write that step's answers into the answers file
(shape in references/answers-file.md) and apply it, so a stop loses nothing:
| # | Step | Command |
|---|---|---|
| 0 | Preflight | profile-wrap doctor; show the table. Stop only if Python is too old or no AI provider is configured; offer the demo instead |
| 1 | Where | workspace path and profile id (default ~/profile-wrap/<profile>) |
| 2 | Who | name, handle, role, niche, audience, regions, languages, time zone (auto-detected, confirm), goal |
| 3 | Privacy | private_terms (employers, clients, products), sensitive subjects |
| 4 | Facts | 10 to 15 questions; rows are written as draft |
| 5 | Voice | 3 to 5 past posts, or 6 style questions; style preset plain, impact_copy or adhd_emoji |
| 6 | Brand | font source (open-licence default, or the user's own licensed files; never copied out), palette mode, identity card |
| 7 | Cadence and caps | show the conservative defaults and the risk of raising each, up to the ceiling |
| 8 | Models | tiered or single; login or API key (recommended for unattended runs) |
| 9 | LinkedIn app | skippable; the checklist is docs/linkedin-app-setup.md; credentials are typed by the user into a hidden prompt, never into chat |
| 10 | Mode consent | one card per action class; the user types the acknowledgement themselves |
| 11 | Scheduler | profile-wrap schedule install --dry-run; the user confirms before anything is installed |
| 12 | Profile | optional paste or data-export ingest |
| 13 | First week | profile-wrap calendar fill --weeks 1, or say which facts are missing |
| 14 | Wrap-up | AGENTS.md, handoff.md, first commit, profile-wrap leaks scan --workspace; say what is automated, what is manual, what happens next |
Apply an answers file with profile-wrap init --answers answers.json --yes (new workspace), or re-enter one
step on an existing workspace with profile-wrap init --section <name> --answers answers.json.
.njl/onboarding.json records which steps are done, skipped or handled by another command.
draft. The user verifies each one in a
terminal with profile-wrap facts verify <ID> --evidence <path|url>; the command refuses when run by an
agent. A gate proves traceability to the user's register, not that the register is true. Say so.profile-wrap config ack <action> prompts for the phrase in a terminal.
Never type it for them and never put it in an answers file you wrote yourself. Skipping keeps the
safe default (draft only, human clicks).profile-wrap config show; say what it risks. Ceilings cannot be raised by config.profile-wrap upgrade --check previews. 2. profile-wrap upgrade --apply overwrites untouched managed files,
keeps files the user edited, and writes <file>.new where both changed (exit 3)..new files, delete them, run profile-wrap upgrade --resolve. 4. profile-wrap migrate runs the
idempotent migrations; one that touches a safety setting asks first and shows a diff.profile-wrap doctor. Backups are in .njl/backup/.After a plugin update, profile-wrap doctor shows runtime drift; profile-wrap runtime sync refreshes the stable
copy schedulers call. Jobs keep working meanwhile.
Run profile-wrap doctor before guessing. Read docs/TROUBLESHOOTING.md for the symptom. Exit codes:
0 ok, 1 fail, 2 usage, 3 conflicts to resolve, 4 paused.
The workspace exists, profile-wrap config validate and profile-wrap handoff check pass, profile-wrap doctor shows no
FAIL, and the user knows the next command. Say plainly what was not verified.
