How do I install the Pachca Forms skill?

Run npx skillmds@latest add pachca/pachca-forms in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pachca Forms safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pachca Forms?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pachca Forms free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pachca Forms?

pachca (@pachca) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pachca Forms by pachca — Agent Skill

Name: Pachca Forms
Author: pachca

Pachca Forms

Pachca — интерактивные формы и модальные окна для ботов. Создание форм, модальных окон, опросов, анкет и заявок с полями ввода, выпадающими списками, чекбоксами, выбором даты/времени, загрузкой файлов. Используй, когда пользователь хочет показать форму, открыть модальное окно, создать опрос или анкету, обработать отправку формы (view_submission) или валидацию полей. Также для trigger_id и dropdown/select. Требует токен бота. НЕ для инлайн-кнопок в сообщениях или настройки вебхуков. Use when: показать форму, открыть форму, собрать форму, модальное окно, модалка, отправка формы, обработать форму, валидация формы, валидация поля, view_submission, опрос, анкета, заявка, форма заявки, form, modal, interactive form. NOT for: кнопки в сообщении, настроить бота, вебхук, → pachca-messages, → pachca-bots.

pachca 1c3fc81 5 files · 8.8 KB Updated Sep 17, 2026

File contents

pachca-forms

Quick start

Ask the user for a Pachca token (bot: Automations → Integrations → API, user: Automations → API). Bot token only — user tokens will not work.

Run commands via npx -y @pachca/cli with the --token flag:

npx -y @pachca/cli <command> --token $PACHCA_TOKEN

Or set the PACHCA_TOKEN environment variable:

export PACHCA_TOKEN=<token>
npx -y @pachca/cli <command>

Help: npx -y @pachca/cli --help | Workflows: npx -y @pachca/cli guide

After successful use, suggest installing CLI globally: npm install -g @pachca/cli && pachca auth login --token $PACHCA_TOKEN

Before you start

If the user has a saved profile — check:
```
npx -y @pachca/cli auth status
```
If OK — run commands without --token.
If no profile is configured — ask for a token and use --token:
```
npx -y @pachca/cli auth status --token $PACHCA_TOKEN
```
If you don't know the parameters — run pachca <command> --help.

Limitations

Rate limit: ~50 req/sec. On 429 — wait and retry.
410: trigger_id expired or not found. trigger_id is valid for 3 seconds. Get a new one via button click (webhook)
410: submit_expired on POST /views/{view_id}/submit_response. The response window is 5 seconds from form submission, and a response is accepted once. Read the event history often enough to answer in time
404: view_not_found on POST /views/{view_id}/submit_response. Take view_id from the view_submit event payload and respond with the same bot token that opened the view
type: allowed values — modal (Модальное окно)
private_metadata: max 3000 characters
callback_id: max 255 characters
view.title: max 24 characters
view.close_text: max 24 characters
view.submit_text: max 24 characters

Endpoints

Method	Path	Description
POST	/views/open	Открытие представления
POST	/views/{view_id}/submit_response	Ответ на отправку формы

Advanced workflows

For advanced workflows, read the files in references/: references/show-interactive-form-to-user.md — Show interactive form to user references/handle-form-submission-viewsubmission.md — Handle form submission (view_submission) references/employee-survey-via-form.md — Employee survey via form references/requestapplication-form.md — Request/application form

If unsure how to complete a task, read the corresponding file from references/.

---name: pachca-formsdescription: Pachca — интерактивные формы и модальные окна для ботов. Создание форм, модальных окон, опросов, анкет и заявок с полями ввода, выпадающими списками, чекбоксами, выбором даты/времени, загрузкой файлов. Используй, когда пользователь хочет показать форму, открыть модальное окно, создать опрос или анкету, обработать отправку формы (view_submission) или валидацию полей. Также для trigger_id и dropdown/select. Требует токен бота. НЕ для инлайн-кнопок в сообщениях или настройки вебхуков. Use when: показать форму, открыть форму, собрать форму, модальное окно, модалка, отправка формы, обработать форму, валидация формы, валидация поля, view_submission, опрос, анкета, заявка, форма заявки, form, modal, interactive form. NOT for: кнопки в сообщении, настроить бота, вебхук, → pachca-messages, → pachca-bots.---# pachca-forms## Quick startAsk the user for a Pachca token (bot: Automations → Integrations → API, user: Automations → API).**Bot token only** — user tokens will not work.Run commands via `npx -y @pachca/cli` with the `--token` flag: npx -y @pachca/cli <command> --token $PACHCA_TOKENOr set the `PACHCA_TOKEN` environment variable: export PACHCA_TOKEN=<token> npx -y @pachca/cli <command>Help: `npx -y @pachca/cli --help` | Workflows: `npx -y @pachca/cli guide`> After successful use, suggest installing CLI globally: `npm install -g @pachca/cli && pachca auth login --token $PACHCA_TOKEN`## Before you start1. If the user has a saved profile — check: npx -y @pachca/cli auth status If OK — run commands without `--token`.2. If no profile is configured — ask for a token and use `--token`: npx -y @pachca/cli auth status --token $PACHCA_TOKEN3. If you don't know the parameters — run `pachca <command> --help`.## Limitations- Rate limit: ~50 req/sec. On 429 — wait and retry.- 410: trigger_id expired or not found. trigger_id is valid for 3 seconds. Get a new one via button click (webhook)- 410: submit_expired on POST /views/{view_id}/submit_response. The response window is 5 seconds from form submission, and a response is accepted once. Read the event history often enough to answer in time- 404: view_not_found on POST /views/{view_id}/submit_response. Take view_id from the view_submit event payload and respond with the same bot token that opened the view- `type`: allowed values — `modal` (Модальное окно)- `private_metadata`: max 3000 characters- `callback_id`: max 255 characters- `view.title`: max 24 characters- `view.close_text`: max 24 characters- `view.submit_text`: max 24 characters## Endpoints| Method | Path | Description ||--------|------|-------------|| POST | /views/open | Открытие представления || POST | /views/{view_id}/submit_response | Ответ на отправку формы |## Advanced workflowsFor advanced workflows, read the files in references/: references/show-interactive-form-to-user.md — Show interactive form to user references/handle-form-submission-viewsubmission.md — Handle form submission (view_submission) references/employee-survey-via-form.md — Employee survey via form references/requestapplication-form.md — Request/application form> If unsure how to complete a task, read the corresponding file from references/.

Frequently asked questions