services · git:20261112.a386cd4 · 2026-11-12 · sha256 378ebbd47db392f3
services git:20261112.a386cd4A
Immutable. This exact content never changes and is served at /api/v1/blob/378ebbd47db392f3.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_afz373ksyjgap3o2/378ebbd47db392f34b9fc2bdbf7d53cc9b4c61eeda6a6b5b9cb640cb375f5020.json
Then /plugin install services@markdownregistry-afz373ksyjgap3o2 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: services description: Use an outside service (Notion, Stripe, a CRM…): call it through the app, or write code that calls it. user-invocable: false --- # Services The app holds each service's key; use it through the helper: `node scripts/company-api.mjs` in WongStack, else `node "$(git rev-parse --show-toplevel)/.claude/skills/access/scripts/services.mjs"`. [The services list](https://github.com/matthewwong525/WongStack/blob/main/wiki/stack/service-catalogue.md) owns the why and the rest. 1. Run `services` to find the key and its notes page. Read the notes page for the key, its levels and its limits. 2. Run `api <key>`, then `api <key> <call>` before you call or write code. Never open the service's `openapi.json`: the short view is enough. 3. For a call `api` doesn't list, read the service's guide, then call it with `<key>.read` or `<key>.change`. When the helper says the call isn't added yet, run the `record` command it prints, then write the call's `summary` (what we use it for) and `description` (how we use it, its quirks) in `openapi.json`. 4. Add what you learn about one call to its `description`, not to the notes page. 5. In code, type the answer with the service's types file, and test it on the saved examples: [service examples](https://github.com/matthewwong525/WongStack/blob/main/wiki/stack/testing.md#service-examples).