Artifact skills now tell agents how to fix a broken Bisque sign-in

When a Bisque key is missing, stale, or stuck in the macOS keychain, an agent had no written steps to follow. This pull request writes it down. Two skill files change: artifacts and artifact-comments. The artifacts skill also gains a short section on pinning.

That is the whole body, one line, so the reasoning lives in the diff. Both changes are in markdown that tells an agent what to do. The artifacts skill gets 23 added lines and the artifact-comments skill gets 14. No code runs differently; agents behave differently because they read different instructions.

The old text sent an agent with no key toward a connector URL, and mentioned the present skill's login as a side note. The new text leads with the shared file. Run bisque login where the bisque command exists, or node present.mjs login where the present skill does, and the key lands in the same config file. The connector URL stays as the fallback.

Profiles in the config file can lack a key. Version 0.25.0 and earlier of bisque kept it in the macOS keychain, where only that command can read it. The skill now has the agent ask the user to run bisque update, then bisque login for that profile, which writes the key into the config file. The agent must not read the keychain itself, and must not send the user to a different sign-in for the same account.

A 401 with the message Invalid API key means the key was revoked or replaced. The skill tells the agent to say so, and to have the user sign in again as that same profile. With bisque installed, that is bisque login with the profile name. With only the present skill, it is node present.mjs login. Either one writes the new key over the dead one.

The one addition that has nothing to do with sign-in. The skill now documents pin_artifact and unpin_artifact. A pin puts an Artifact at the top of the user's own library, the same as the Pin button, and the agent should use it when the user asks to keep something where they can find it. The skill is explicit that a pin is private to the user.

The change is 37 added lines and 7 removed, all in two markdown files. The body gives no reason for it, and nothing in the pull request shows an agent following these steps. The 0.25.0 keychain cutoff is stated in the diff and is the claim most worth checking against the bisque release history. There are no review comments yet.

An agent follows these lines to the letter, so the useful review is on the commands and the version number, since the pull request does not show them running. If they hold, a missing key, a keychain profile, and a revoked key each end in a command the user can type. The pull request is number 5 in the artifacts repository.