Individual skill
pachca-api
API Пачки из кода, скриптов и CI: токен и права для скрипта или сервиса, обход всех страниц, ошибки и повторы без дублей (401/403/422, 429, 5xx), файлы в коде, SDK и генератор, CLI в скриптах, массовые выгрузки, поиск метода. Когда: «напиши скрипт для API Пачки», «какой токен дать скрипту, сервису или CI», «мой код получает 401/403/422 от API», «упёрлись в 429», «поиск вернул 504 timeout, повторить?», «обойти все страницы», «скрипт, который выгружает всех сотрудников», «загрузка файла из кода», «SDK Пачки», «какой метод API», "call the Pachca API from code", "token for a script or CI job", "401/403/422 in my code", "cursor pagination", "429 Retry-After", "upload a file from my code", "Pachca SDK", "pachca CLI in CI", "which endpoint". Not for: connecting an agent or MCP client, a 401/403 from an MCP tool → pachca; writing messages, a file to a chat now → pachca-messaging; bots, webhooks, events → pachca-bots; OAuth for employees → pachca-oauth; token policy, all-tokens tab, message export → pachca-admin.
plugins/pachca/skills/pachca-api/SKILL.md
Source commit 542014c04cf308d45040194e9290551570a1aee8
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 11
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 25,477 bytesSKILL.mdcore · 25,477 bytesreferences/cli-scripting.mddoc · 12,871 bytesreferences/errors-and-retries.mddoc · 15,286 bytesreferences/pagination.mddoc · 8,655 bytes
Read excerpt
# Pachca API, SDK and CLI in scripts
The judgment around calling the Pachca REST API from a script, a service, CI, an SDK or the `pachca` CLI. The per-method reference lives elsewhere: MCP tool descriptions, `pachca ... --help`, and the method `.md` pages. Do not restate it; look it up.
## When to use
- Writing or fixing code that calls `https://api.pachca.com/api/shared/v1` directly, through an SDK, or through `pachca` in a shell script or CI job.
- A call fails (`401`, `403`, `409`, `422`, `429`, `5xx`) and you must decide: fix the request, fix the token, or wait.
- Walking a whole list (all employees, all chats, a chat's history) or polling for new records.
- Uploading a file from disk or downloading an attachment in code.
- Choosing a token and scopes for a new script or integration.
- You do not know which method does the job.
With MCP tools connected, a one-off action is just a tool call. The rules below still hold underneath: every tool call is an API request under the same token, scopes and limits.