Skip to content
Alma Mobility MarketplacesAlma Mobility MarketplacesAlma Mobility Marketplaces developer docs

Install the AJOMARK Claude skills

We keep a set of shared Claude skills in ai-ops-playbook so that a Jira ticket, a Confluence spec or an ADR comes out in the same shape whoever asked for it. They carry our templates, our project keys and our conventions, so you do not describe them from scratch each time.

There is nothing to build. Install them once, then describe what you want in plain language.

Prerequisites: Claude Code, claude.ai or Claude Desktop, plus working Git credentials for the organisation. The repository is private and the marketplace fetches it over Git, so organisation membership alone is not enough — browser SSO does not authenticate Git. The check that matters is whether this already works:

Terminal window
git ls-remote https://github.com/alma-mobility-marketplaces/ai-ops-playbook.git

If that prompts or fails, set up a credential helper first (gh auth setup-git does it if you use the GitHub CLI).

Claude Code

Section titled “Claude Code”
/plugin marketplace add alma-mobility-marketplaces/ai-ops-playbook
/plugin install ajomark-assistants@ai-ops-playbook

That installs every skill at once. Copying skill folders by hand also works, but then nothing connects them to the source, so you never learn that a skill changed.

Verify by typing / and looking for the ajomark-assistants: entries.

Updates are not automatic by default — a marketplace install gives you a route to them, not a subscription, and a running session may need reloading before new skill versions appear. The current refresh commands are in ai-ops-playbook’s installation guides; they track the plugin system, so this page does not restate them.

claude.ai and Claude Desktop

Section titled “claude.ai and Claude Desktop”

On a Team or Enterprise plan an Organisation Owner uploads each skill under Organisation settings → Skills, and every member then has it with nothing to install themselves.

Two toggles in that same place have to be on first — Code execution and file creation, and Skills. Skills need code execution to run, so with it off they do not appear at all, and nothing says why. Check both before concluding an upload failed; the vendor’s provisioning guide has the current details.

What an owner uploads is a .zip, so the result is a snapshot rather than something that follows ai-ops-playbook — expect to re-upload when a skill changes.

If you are not an owner, ask for this rather than installing per person — a per-person install means six people running six versions, which is the problem the shared skills exist to solve.

What you get

Section titled “What you get”

Six skills: Jira Assistant, Confluence Spec Assistant, ADR Writer, Documentation Writer, Spec-Driven Development and Karpathy Guidelines.

What each one does, what it asks you for, and the operating rules it follows — including why it will refuse to write to a repository while creating Jira issues — are in ai-ops-playbook’s own guides, one installation guide and one plain-language user guide per skill.

Section titled “Related”