Handing it to other software

pskl mcp install --for <tool> connects a coding tool — Claude Code, Codex, Cursor, VS Code, Google Antigravity, PyCharm and the other JetBrains IDEs, and every tool in the table below — on macOS, Windows and Linux. It writes each tool’s own file in its own format, changing only the ProjectSkills entry and keeping the previous version as <file>.projectskills.bak. The connection is read-only: no tool changes anything. pskl mcp doctor checks the whole path each agent takes — the token, the server, its tools, the linked project and every tool configured here — and prints the fix for whatever fails, in your own shell.

Two scopes. In a repository (--scope project, the default where a tool supports it) the file is meant to be committed, so it holds no credential: VS Code asks for the token once and keeps it in its secret storage, and the other tools read PROJECTSKILLS_TOKEN from the environment in their own syntax. On this machine (--scope user) the tool starts pskl mcp serve, a local relay that uses your pskl login — nothing to set, and it works for an editor opened from the Dock or the Start menu, which never sees a shell’s variables. It is started by absolute path to Node and the CLI, so it needs no shell on Windows either.

Every answer opens with the snapshot it describes — its number, commit and date — and says so when the commit you are editing is not the analysed one, or a newer analysis is still running. Text quoted from the repository sits on lines that begin │, which the server tells the agent to read as data, never as instructions. A fact that was inferred rather than verified says (inferred), and its evidence follows as — path:line. Answers are sized for an agent’s context, and one that had to be cut says how much and how to narrow the question.

Access is the web’s: the same project membership, the same plan checks and the same per-feature rate limits, spent from the same allowance. Both protocol generations connect — the 2026-07-28 revision without a handshake, and 2025-11-25, 2025-06-18 and 2025-03-26 with one.

Each delivery is signed over the timestamp and the body together, so a captured request cannot be replayed with a rewritten header. Redirects are not followed — the address that was checked would not be the address fetched.

A destination that keeps failing is disabled rather than retried forever, and the row says so — a webhook that stopped working is otherwise invisible from the outside.

For a client, a reviewer, or somebody deciding whether to work with you. The page carries no file contents, no excerpts and no identifiers, and it is excluded from search indexes.

The link is the credential, so it is shown once, stored only as a hash, and expires. Expired, revoked and never-existed all answer with the same sentence — telling somebody a link *was* valid tells them they guessed a real one.

It is built from the dependency manifests in the repository, not from an installed tree, so it declares itself incomplete rather than asserting completeness by silence.

• Versions come from a lock file where one is readable, and are left absent otherwise — never read off a range, because a caret range permits a version an advisory match would miss.
• No licences are stated. This analysis reads the manifests that name packages and never the packages themselves, and a guessed licence is the one field a compliance reader trusts most.

pskl explain composes what the analysis already produced — the detected stack, the structural scan, the written summary — into plain language: no pillar, no verdict, no provenance glyphs. Those words are precise and they are exactly the ones that lose somebody on their first day.

Every section says what it could not establish, next to the claim it qualifies. A document that explains a codebase to somebody who cannot check it is the easiest place in this product to be quietly wrong.