[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EN9PRZFNEA99X41BWPYVAB":3,"skill-same:01M6EN9PRZFNEA99X41BWPYVAB":142},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6EN9PRZFNEA99X41BWPYVAB","pulse-cli",null,"Inspect and operate Camunda 7, Operaton and CIB seven process engines through their REST API with the Pulse CLI (deployments, process instances, user tasks, external tasks, incidents, jobs, history, variables, decisions), and drive process instances with its workflow commands (inspect, wait, advance, retry, deploy, status). Use it whenever a task needs to read or change the state of such an engine.","Miragon\u002Fpulse","Miragon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F58698887?v=4","01M6EN8W7TCK4BRJB1S2GEW8C3","01M6EN8WC4V4QYAV5C8FMYZ4R9",8,"MIT","https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"pulse","cli","pulse cli","wait","status","commands","read","change","Variables","incidents","inspect","retry","operate","api","tasks","workflow","deployments","advance","history","instances","2026-11-10 10:12:30",false,"---\nname: pulse-cli\ndescription: Inspect and operate Camunda 7, Operaton and CIB seven process engines through their REST API with the Pulse CLI (deployments, process instances, user tasks, external tasks, incidents, jobs, history, variables, decisions), and drive process instances with its workflow commands (inspect, wait, advance, retry, deploy, status). Use it whenever a task needs to read or change the state of such an engine.\n---\n\n# Pulse CLI: the Camunda 7 REST API from the command line\n\n`pulse` calls the REST API (`\u002Fengine-rest`) of Camunda 7 process engines: Operaton, CIB seven\nand Camunda 7 CE\u002FEE. Every REST operation is a command generated from the OpenAPI spec:\n`pulse \u003Cgroup> \u003Ccommand> [path-args...] [options]`; workflow commands such as\n`pulse inspect` combine several requests. It never prompts, prints JSON when stdout is not a\nterminal, reports errors as one JSON line on stderr (the last line) and uses stable exit codes.\nThis core guide covers everyday use; `pulse guide \u003Ctopic>` prints the details of a topic (see\nTopics at the end).\n\n## Setup\n\nIf `pulse` is missing, try `pulse-cli`: the same program under its second name. Without either,\nrun `npx -y @miragon\u002Fpulse-cli` in its place or ask the user to install\nit with `npm i -g @miragon\u002Fpulse-cli` (Node.js 22.12+). The REST API root defaults to\n`http:\u002F\u002Flocalhost:8080\u002Fengine-rest`. Set it per shell, then check the connection:\n\n```sh\nexport PULSE_CLI_URL=http:\u002F\u002Flocalhost:8080\u002Fengine-rest\npulse ping\n```\n\nA repository may ship its engines as profiles in a project file (`.pulse.json`): check\n`pulse config list` first (scope `project`); without `PULSE_CLI_URL` a bare `pulse ping` then uses\nits default.\n\nOr keep each engine in a profile and pick one with `--profile`. Unset `PULSE_CLI_URL` first: beside\n`--profile` it overrides the profile's URL (and its credentials go along), and without `--profile`\nit uses no profile, as a `--url` does:\n\n```sh\nunset PULSE_CLI_URL\npulse config set local --url http:\u002F\u002Flocalhost:8080\u002Fengine-rest --default\npulse config set prod --url https:\u002F\u002Fcamunda.example.com\u002Fengine-rest --read-only\npulse ping --profile prod\n```\n\n- `pulse ping` prints `{url, engine, reachable, version, engines, latencyMs, auth}` (`user`\n  too).\n- Precedence for every setting: flag > environment variable > profile > default.\n  A URL (`--url`, `PULSE_CLI_URL`) without `--profile` selects no profile: nothing of one applies.\n  Beside `--profile`, a `--url` of another origin fails for a profile of yours that holds headers\n  or credentials.\n- Links to Cockpit: take `values.cockpitUrl` from `pulse config show -o json`; when it is null,\n  ask the user for the Cockpit URL instead of guessing it from the engine URL.\n- Profiles, project files, environment variables, named engines and headers:\n  `pulse guide config`. Basic auth, bearer tokens, token commands and OAuth logins:\n  `pulse guide auth`.\n\n## Discover, describe, preview, run\n\nNever guess commands or flags. Look them up, preview writes, then run:\n\n```sh\npulse commands\npulse commands --search incident\npulse describe process-definition start\npulse process-definition start invoice --var amount=250 --dry-run\npulse process-definition start invoice --var amount=250\n```\n\n- `pulse commands` lists the groups (and `workflow`); `pulse commands \u003Cgroup>` the commands\n  of a group with method, path, effect and summary; `--search` finds commands whose command, alias,\n  operationId, summary or path contain every word (`--search 'process instance'`); `--effect`\n  filters by `read`, `write`, `delete` or `bulk`.\n- `pulse describe \u003Cgroup> \u003Ccommand>` (or an operationId or workflow command) shows arguments,\n  options, the request body schema, responses and examples (JSON when piped, text with `-o table`).\n- `pulse \u003Cgroup> \u003Ccommand> --help` shows the options; `pulse guide` prints this guide.\n\n## Workflow commands\n\nTop-level commands that combine requests, so no id passes through you. They select an instance by\nid, `--business-key` or `--process-definition-key \u003Ckey> --latest`; `next` lists follow-ups:\n\n- `pulse inspect`: where an instance waits and why: wait states, root incidents, variables.\n- `pulse wait`: until the instance is idle, or\n  `--until ended|incident|task[:key]|activity:\u003Cid>`.\n- `pulse advance`: completes what it waits for: user or external task, message, timer, job.\n- `pulse retry`: sets the retries behind open incidents; `--now` executes the jobs.\n- `pulse deploy`: deploys changed files and directories, reports the versions in effect.\n- `pulse status`: grouped incidents with root cause, overdue jobs, external task workers.\n\n```sh\npulse deploy bpmn --start --business-key B-1 --var amount=250\npulse inspect --business-key B-1\npulse advance --business-key B-1 --var approved=true --wait\npulse retry --business-key B-1 --now\npulse wait --business-key B-1 --until ended\npulse status\n```\n\nUse `pulse wait` or `--wait` (advance, retry, deploy) instead of `sleep`; it fails on incidents\nwith exit code 9, which still prints the view. Options and rules: `pulse guide workflow`.\n\n## Invocation conventions\n\n- Path parameters are positional arguments in path order; query parameters and body properties are\n  kebab-case flags (`businessKey` → `--business-key`); global options work after the command.\n- Variables: `--var name=value`, repeatable and auto typed; force a type with `name:Type=value`,\n  e.g. `--var zip:String=01234`.\n- `--body \u003Cjson>`, `--body @file.json` or `--body -` (stdin) is the base JSON body for nested\n  structures; flags are merged on top, and the body is validated against the API schema.\n- List commands with `--max-results` also take `--all` to fetch every page.\n- Booleans, arrays, dates, variable types, files and the global options: `pulse guide input`.\n\n## Output\n\n- stdout carries exactly the engine response (workflow commands: their view): JSON, compact when\n  piped, indented on a terminal or with `--pretty`, always ending with a newline.\n- `--fields id,name,variables.amount` keeps only these properties; `-o table` prints a table.\n- No content (HTTP 204): stdout stays empty, stderr gets `Done: \u003CMETHOD> \u003Cpath> → 204 No Content`.\n- XML, text and binary responses, `--out-file`, `--dry-run` and `--verbose`:\n  `pulse guide output`.\n\n## Errors and exit codes\n\nErrors are one JSON line on stderr, its last line (`-o table` prints readable text instead):\n\n```text\n{\"error\":{\"code\":\"NOT_FOUND\",\"exitCode\":5,\"message\":\"HTTP 404 Not Found: ...\",\"status\":404,\"engineType\":\"InvalidRequestException\",\"hint\":\"...\",\"request\":{\"method\":\"GET\",\"url\":\"...\"}}}\n```\n\n| exit | meaning                                                                                                |\n| ---- | ------------------------------------------------------------------------------------------------------ |\n| 0    | success                                                                                                |\n| 1    | internal error                                                                                         |\n| 2    | usage error, invalid body (`VALIDATION`), `READ_ONLY`, `CONFIRMATION_REQUIRED`                         |\n| 3    | configuration error, also an HTTP redirect (`HTTP_REDIRECT`, see below)                                |\n| 4    | auth failed: 401, 403, `LOGIN_REQUIRED` (a person must log in), `LOGIN_FAILED`, `TOKEN_EXPIRED`        |\n| 5    | not found (404)                                                                                        |\n| 6    | other 4xx: the engine rejected the request, read `engineMessage`                                       |\n| 7    | engine error (5xx)                                                                                     |\n| 8    | network error or timeout                                                                               |\n| 9    | expected state not reached: `WAIT_TIMEOUT`, `INCIDENT`, `INSTANCE_ENDED`, `JOB_FAILED`, `CHECK_FAILED` |\n\nRead `hint` first: it names the fix (`pulse describe ...`, `--yes`, `--no-validate`, the\naccepted date forms, ...); for unknown names it starts with \"Did you mean ...?\". Redirects are never\nfollowed: a 3xx answer is `HTTP_REDIRECT` (exit 3), fix `--url` (`https`, a login page). Camunda 7\nengines report many rule violations as HTTP 500 (exit 7), e.g. a task that is already claimed:\nread `engineMessage` and fix the cause instead of retrying. On exit 4: `pulse guide auth`.\n\n## Safety\n\n- `--dry-run` prints the request (`method`, `url`, `headers`, `body`, `curl`) without sending it.\n  Use it before writes you are unsure about; it works in read-only mode too.\n- Commands with effect `delete` or `bulk` (batches, query based updates, all versions of a key,\n  `pulse retry --process-definition-key` alone) refuse to run without `--yes` (exit 2,\n  `CONFIRMATION_REQUIRED`). Add `--yes` only when the user asked for exactly that change.\n- `--read-only`, `PULSE_CLI_READ_ONLY=1` or a profile created with `--read-only` refuse every\n  command whose effect is not `read` (exit 2, `READ_ONLY`). Use read-only profiles for production;\n  a profile guards only the commands that use it, and a URL without `--profile` uses none.\n\n## Topics\n\n`pulse guide \u003Ctopic>` prints the details of a topic; `pulse guide --list` lists the topics:\n\n- `workflow`: Workflow commands in detail: selection, inspect, wait, advance, retry, deploy, status\n- `input`: Arguments, flags, booleans, arrays, dates, variables, request bodies, files, paging\n- `output`: JSON and tables, --fields, XML, text and binary responses, --out-file, previews\n- `config`: Profiles, config and project files, environment variables, engines, headers, timeouts\n- `auth`: Basic auth, bearer tokens and token commands, OAuth logins, what to do on exit 4\n- `recipes`: Command lines for everyday tasks: deploy, tasks, incidents, messages, history, api\n\n```sh\npulse guide --list\npulse guide recipes\n```\n\nAn older pulse-cli without topics answers \"Too many arguments for 'guide'\": run\n`npx -y @miragon\u002Fpulse-cli@latest guide \u003Ctopic>` instead, or ask the user to update it.\n","# Pulse CLI: the Camunda 7 REST API from the command line\n\n`pulse` calls the REST API (`\u002Fengine-rest`) of Camunda 7 process engines: Operaton, CIB seven\nand Camunda 7 CE\u002FEE. Every REST operation is a command generated from the OpenAPI spec:\n`pulse \u003Cgroup> \u003Ccommand> [path-args...] [options]`; workflow commands such as\n`pulse inspect` combine several requests. It never prompts, prints JSON when stdout is not a\nterminal, reports errors as one JSON line on stderr (the last line) and uses stable exit codes.\nThis core guide covers everyday use; `pulse guide \u003Ctopic>` prints the details of a topic (see\nTopics at the end).\n\n## Setup\n\nIf `pulse` is missing, try `pulse-cli`: the same program under its second name. Without either,\nrun `npx -y @miragon\u002Fpulse-cli` in its place or ask the user to install\nit with `npm i -g @miragon\u002Fpulse-cli` (Node.js 22.12+). The REST API root defaults to\n`http:\u002F\u002Flocalhost:8080\u002Fengine-rest`. Set it per shell, then check the connection:\n\n```sh\nexport PULSE_CLI_URL=http:\u002F\u002Flocalhost:8080\u002Fengine-rest\npulse ping\n```\n\nA repository may ship its engines as profiles in a project file (`.pulse.json`): check\n`pulse config list` first (scope `project`); without `PULSE_CLI_URL` a bare `pulse ping` then uses\nits default.\n\nOr keep each engine in a profile and pick one with `--profile`. Unset `PULSE_CLI_URL` first: beside\n`--profile` it overrides the profile's URL (and its credentials go along), and without `--profile`\nit uses no profile, as a `--url` does:\n\n```sh\nunset PULSE_CLI_URL\npulse config set local --url http:\u002F\u002Flocalhost:8080\u002Fengine-rest --default\npulse config set prod --url https:\u002F\u002Fcamunda.example.com\u002Fengine-rest --read-only\npulse ping --profile prod\n```\n\n- `pulse ping` prints `{url, engine, reachable, version, engines, latencyMs, auth}` (`user`\n  too).\n- Precedence for every setting: flag > environment variable > profile > default.\n  A URL (`--url`, `PULSE_CLI_URL`) without `--profile` selects no profile: nothing of one applies.\n  Beside `--profile`, a `--url` of another origin fails for a profile of yours that holds headers\n  or credentials.\n- Links to Cockpit: take `values.cockpitUrl` from `pulse config show -o json`; when it is null,\n  ask the user for the Cockpit URL instead of guessing it from the engine URL.\n- Profiles, project files, environment variables, named engines and headers:\n  `pulse guide config`. Basic auth, bearer tokens, token commands and OAuth logins:\n  `pulse guide auth`.\n\n## Discover, describe, preview, run\n\nNever guess commands or flags. Look them up, preview writes, then run:\n\n```sh\npulse commands\npulse commands --search incident\npulse describe process-definition start\npulse process-definition start invoice --var amount=250 --dry-run\npulse process-definition start invoice --var amount=250\n```\n\n- `pulse commands` lists the groups (and `workflow`); `pulse commands \u003Cgroup>` the commands\n  of a group with method, path, effect and summary; `--search` finds commands whose command, alias,\n  operationId, summary or path contain every word (`--search 'process instance'`); `--effect`\n  filters by `read`, `write`, `delete` or `bulk`.\n- `pulse describe \u003Cgroup> \u003Ccommand>` (or an operationId or workflow command) shows arguments,\n  options, the request body schema, responses and examples (JSON when piped, text with `-o table`).\n- `pulse \u003Cgroup> \u003Ccommand> --help` shows the options; `pulse guide` prints this guide.\n\n## Workflow commands\n\nTop-level commands that combine requests, so no id passes through you. They select an instance by\nid, `--business-key` or `--process-definition-key \u003Ckey> --latest`; `next` lists follow-ups:\n\n- `pulse inspect`: where an instance waits and why: wait states, root incidents, variables.\n- `pulse wait`: until the instance is idle, or\n  `--until ended|incident|task[:key]|activity:\u003Cid>`.\n- `pulse advance`: completes what it waits for: user or external task, message, timer, job.\n- `pulse retry`: sets the retries behind open incidents; `--now` executes the jobs.\n- `pulse deploy`: deploys changed files and directories, reports the versions in effect.\n- `pulse status`: grouped incidents with root cause, overdue jobs, external task workers.\n\n```sh\npulse deploy bpmn --start --business-key B-1 --var amount=250\npulse inspect --business-key B-1\npulse advance --business-key B-1 --var approved=true --wait\npulse retry --business-key B-1 --now\npulse wait --business-key B-1 --until ended\npulse status\n```\n\nUse `pulse wait` or `--wait` (advance, retry, deploy) instead of `sleep`; it fails on incidents\nwith exit code 9, which still prints the view. Options and rules: `pulse guide workflow`.\n\n## Invocation conventions\n\n- Path parameters are positional arguments in path order; query parameters and body properties are\n  kebab-case flags (`businessKey` → `--business-key`); global options work after the command.\n- Variables: `--var name=value`, repeatable and auto typed; force a type with `name:Type=value`,\n  e.g. `--var zip:String=01234`.\n- `--body \u003Cjson>`, `--body @file.json` or `--body -` (stdin) is the base JSON body for nested\n  structures; flags are merged on top, and the body is validated against the API schema.\n- List commands with `--max-results` also take `--all` to fetch every page.\n- Booleans, arrays, dates, variable types, files and the global options: `pulse guide input`.\n\n## Output\n\n- stdout carries exactly the engine response (workflow commands: their view): JSON, compact when\n  piped, indented on a terminal or with `--pretty`, always ending with a newline.\n- `--fields id,name,variables.amount` keeps only these properties; `-o table` prints a table.\n- No content (HTTP 204): stdout stays empty, stderr gets `Done: \u003CMETHOD> \u003Cpath> → 204 No Content`.\n- XML, text and binary responses, `--out-file`, `--dry-run` and `--verbose`:\n  `pulse guide output`.\n\n## Errors and exit codes\n\nErrors are one JSON line on stderr, its last line (`-o table` prints readable text instead):\n\n```text\n{\"error\":{\"code\":\"NOT_FOUND\",\"exitCode\":5,\"message\":\"HTTP 404 Not Found: ...\",\"status\":404,\"engineType\":\"InvalidRequestException\",\"hint\":\"...\",\"request\":{\"method\":\"GET\",\"url\":\"...\"}}}\n```\n\n| exit | meaning                                                                                                |\n| ---- | ------------------------------------------------------------------------------------------------------ |\n| 0    | success                                                                                                |\n| 1    | internal error                                                                                         |\n| 2    | usage error, invalid body (`VALIDATION`), `READ_ONLY`, `CONFIRMATION_REQUIRED`                         |\n| 3    | configuration error, also an HTTP redirect (`HTTP_REDIRECT`, see below)                                |\n| 4    | auth failed: 401, 403, `LOGIN_REQUIRED` (a person must log in), `LOGIN_FAILED`, `TOKEN_EXPIRED`        |\n| 5    | not found (404)                                                                                        |\n| 6    | other 4xx: the engine rejected the request, read `engineMessage`                                       |\n| 7    | engine error (5xx)                                                                                     |\n| 8    | network error or timeout                                                                               |\n| 9    | expected state not reached: `WAIT_TIMEOUT`, `INCIDENT`, `INSTANCE_ENDED`, `JOB_FAILED`, `CHECK_FAILED` |\n\nRead `hint` first: it names the fix (`pulse describe ...`, `--yes`, `--no-validate`, the\naccepted date forms, ...); for unknown names it starts with \"Did you mean ...?\". Redirects are never\nfollowed: a 3xx answer is `HTTP_REDIRECT` (exit 3), fix `--url` (`https`, a login page). Camunda 7\nengines report many rule violations as HTTP 500 (exit 7), e.g. a task that is already claimed:\nread `engineMessage` and fix the cause instead of retrying. On exit 4: `pulse guide auth`.\n\n## Safety\n\n- `--dry-run` prints the request (`method`, `url`, `headers`, `body`, `curl`) without sending it.\n  Use it before writes you are unsure about; it works in read-only mode too.\n- Commands with effect `delete` or `bulk` (batches, query based updates, all versions of a key,\n  `pulse retry --process-definition-key` alone) refuse to run without `--yes` (exit 2,\n  `CONFIRMATION_REQUIRED`). Add `--yes` only when the user asked for exactly that change.\n- `--read-only`, `PULSE_CLI_READ_ONLY=1` or a profile created with `--read-only` refuse every\n  command whose effect is not `read` (exit 2, `READ_ONLY`). Use read-only profiles for production;\n  a profile guards only the commands that use it, and a URL without `--profile` uses none.\n\n## Topics\n\n`pulse guide \u003Ctopic>` prints the details of a topic; `pulse guide --list` lists the topics:\n\n- `workflow`: Workflow commands in detail: selection, inspect, wait, advance, retry, deploy, status\n- `input`: Arguments, flags, booleans, arrays, dates, variables, request bodies, files, paging\n- `output`: JSON and tables, --fields, XML, text and binary responses, --out-file, previews\n- `config`: Profiles, config and project files, environment variables, engines, headers, timeouts\n- `auth`: Basic auth, bearer tokens and token commands, OAuth logins, what to do on exit 4\n- `recipes`: Command lines for everyday tasks: deploy, tasks, incidents, messages, history, api\n\n```sh\npulse guide --list\npulse guide recipes\n```\n\nAn older pulse-cli without topics answers \"Too many arguments for 'guide'\": run\n`npx -y @miragon\u002Fpulse-cli@latest guide \u003Ctopic>` instead, or ask the user to update it.\n",{"name":5,"description":7},"main","ff711bb6e1eb952767e56e3bdd4d7c249ced5b68","apps\u002Fcli\u002Fskills\u002Fpulse-cli",0,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse","https:\u002F\u002Fmiragon.github.io\u002Fpulse\u002F","https:\u002F\u002Fgithub.com\u002FMiragon","https:\u002F\u002Fwww.miragon.io","We enable organizations to become truly digital.","2026-11-14 03:34:19",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Miragon\u002Fpulse --skill pulse-cli",{"tool":59,"command":60},"bunx","bunx skills add Miragon\u002Fpulse --skill pulse-cli",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Miragon\u002Fpulse --skill pulse-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002FSKILL.md",true,[67,73,77,81,85,89,93,97,101,105,109,113,116,120,124,127,131,135,138],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},".claude-plugin\u002Fplugin.json","REFERENCE","参考文档",612,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002F.claude-plugin\u002Fplugin.json",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"commands\u002Fstatus.md",2086,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fcommands\u002Fstatus.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"evals\u002Fbpmn-question\u002Fgraders\u002Fanswer.md",105,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fbpmn-question\u002Fgraders\u002Fanswer.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"evals\u002Fbpmn-question\u002Fgraders\u002Fno-skill.md",210,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fbpmn-question\u002Fgraders\u002Fno-skill.md",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"evals\u002Fbpmn-question\u002Fprompt.md",224,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fbpmn-question\u002Fprompt.md",{"path":90,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":91,"sourceHtmlUrl":92},"evals\u002Fcamunda8-question\u002Fgraders\u002Fanswer.md",116,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fcamunda8-question\u002Fgraders\u002Fanswer.md",{"path":94,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":95,"sourceHtmlUrl":96},"evals\u002Fcamunda8-question\u002Fgraders\u002Fno-cli.md",216,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fcamunda8-question\u002Fgraders\u002Fno-cli.md",{"path":98,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":99,"sourceHtmlUrl":100},"evals\u002Fcamunda8-question\u002Fgraders\u002Fno-skill.md",205,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fcamunda8-question\u002Fgraders\u002Fno-skill.md",{"path":102,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":103,"sourceHtmlUrl":104},"evals\u002Fcamunda8-question\u002Fprompt.md",250,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fcamunda8-question\u002Fprompt.md",{"path":106,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":107,"sourceHtmlUrl":108},"evals\u002Fdeploy-and-start\u002Fgraders\u002Fdeploy-command.md",163,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fdeploy-and-start\u002Fgraders\u002Fdeploy-command.md",{"path":110,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":111,"sourceHtmlUrl":112},"evals\u002Fdeploy-and-start\u002Fgraders\u002Fskill-fired.md",127,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fdeploy-and-start\u002Fgraders\u002Fskill-fired.md",{"path":114,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":111,"sourceHtmlUrl":115},"evals\u002Fdeploy-and-start\u002Fgraders\u002Fvariable.md","https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fdeploy-and-start\u002Fgraders\u002Fvariable.md",{"path":117,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":118,"sourceHtmlUrl":119},"evals\u002Fdeploy-and-start\u002Fprompt.md",243,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fdeploy-and-start\u002Fprompt.md",{"path":121,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":122,"sourceHtmlUrl":123},"evals\u002Fopen-incidents\u002Fgraders\u002Fpulse-cli-command.md",182,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fopen-incidents\u002Fgraders\u002Fpulse-cli-command.md",{"path":125,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":111,"sourceHtmlUrl":126},"evals\u002Fopen-incidents\u002Fgraders\u002Fskill-fired.md","https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fopen-incidents\u002Fgraders\u002Fskill-fired.md",{"path":128,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":129,"sourceHtmlUrl":130},"evals\u002Fopen-incidents\u002Fprompt.md",227,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Fopen-incidents\u002Fprompt.md",{"path":132,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":133,"sourceHtmlUrl":134},"evals\u002Funrelated-code\u002Fgraders\u002Fanswer.md",104,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Funrelated-code\u002Fgraders\u002Fanswer.md",{"path":136,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":137},"evals\u002Funrelated-code\u002Fgraders\u002Fno-skill.md","https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Funrelated-code\u002Fgraders\u002Fno-skill.md",{"path":139,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":140,"sourceHtmlUrl":141},"evals\u002Funrelated-code\u002Fprompt.md",202,"https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Fapps\u002Fcli\u002Fskills\u002Fpulse-cli\u002Fevals\u002Funrelated-code\u002Fprompt.md",[143,181,190,217,242,266],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":160,"publishedAt":38},"01M6ENA6VEQJXWWXWE52B9JPZK","setup-server","Set up, configure, run, brand, and deploy this composed MCP server. Use whenever connecting a Camunda 7 \u002F CIB seven engine, selecting modules or toolsets (`MCP_ACTIVE_MODULES`), renaming the `@acme` scope, building the Docker image, running behind an MCP gateway, or troubleshooting boot warnings or inspector issues.","https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Ftemplates\u002Fcomposed-server\u002F.claude\u002Fskills\u002Fsetup-server\u002FSKILL.md",[149,154,157],{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":155,"categoryName":156,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":158,"categoryName":159,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000023","Skill与智能体开发",[161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180],"setup server","server","setup","modules","SET","gateway","prometheus","brand","scope","docker","up","issues","MCP","use","boot","configure","image","Bash","mcp server","running",{"skillNo":182,"name":183,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":38},"01M6ENA321FCXRTT8X06D0K4A0","create-module","https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Ftemplates\u002Fcomposed-server\u002F.claude\u002Fskills\u002Fcreate-module\u002FSKILL.md",[],[187,188,189],"create module","module","create",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":199,"publishedAt":38},"01M6EN9ZEDJZMEAJH3RP50NV5S","add-widget","Step-by-step house pattern for adding an interactive widget to a module (the React component built from the design kit `@miragon\u002Fpulse-ui` and widget-shell's view runtime, the `show_*` widget tool, the app-only `*_data` feed, the view map keyed by the show tool's name, and a widget test under `TestViewHost`). Use whenever adding or changing widgets, `show_*` tools, `*_data` feeds, in-widget data fetching, or when debugging a widget that renders empty, unstyled, or hangs on \"Loading…\".","https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002Ftemplates\u002Fcomposed-server\u002F.claude\u002Fskills\u002Fadd-widget\u002FSKILL.md",[196],{"categoryNo":197,"categoryName":198,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000009","前端开发",[200,201,202,203,204,205,206,188,207,174,208,178,209,210,211,212,213,214,215,216],"add widget","widget","add","app","feeds","show","tool","only","debugging","view","for","loading","runtime","design","kit","map","when",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":223,"publishedAt":38},"01M6EN9J8S9R51AP99F0YBBQM7","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", or \"switch to --preset\".","https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[219,203,224,225,226,227,228,229,230,231,208,232,233,234,235,189,236,237,238,239,240,210,216,241],"projects","component docs","switch","project","init","triggers","codes","false","file","components","examples","preset","component","json","project context","styling","usage","with",{"skillNo":243,"name":244,"nameZh":6,"description":245,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":246,"categories":247,"keywords":250,"publishedAt":38},"01M6EN9ETKR0TQJRVBVEHW17VM","mcp-apps-builder","Where to look before changing MCP server code in this repo (tools, resources, prompts, widgets, auth). Points to the house skills, the CLAUDE.md invariants, widget-shell's view runtime and the official MCP SDK's typings and docs; it teaches no framework API itself.","https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmcp-apps-builder\u002FSKILL.md",[248,249],{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},{"categoryNo":158,"categoryName":159,"taxonomyType":152,"taxonomyTypeDesc":153},[251,173,252,253,254,162,255,256,257,258,259,174,179,260,209,212,261,262,201,31,263,264,265],"builder","apps","mcp apps builder","mcp apps","resources","widgets","auth","repo","look","code","shell","invariants","official","mcp sdk","sdk",{"skillNo":267,"name":268,"nameZh":6,"description":269,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":270,"categories":271,"keywords":275,"publishedAt":38},"01M6EN9BKN04C3NG1Q6CXBR92T","create-ticket","Create or update a GitHub issue for Pulse using the `gh` CLI. Use when the user asks to \"file a bug\", \"create a feature request\", \"open a GitHub issue\", or \"update an existing one\". Supports feature, bug, and refactor issue types with structured templates; shows a draft for confirmation before creating or editing; looks up existing issues by number or URL for updates.","https:\u002F\u002Fgithub.com\u002FMiragon\u002Fpulse\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreate-ticket\u002FSKILL.md",[272],{"categoryNo":273,"categoryName":274,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000007","代码审查",[276,189,277,278,279,280,171,172,281,282,174,283,178,232,284,210,285,286,287,288,216],"ticket","create ticket","types","feature","editing","open","gh","confirmation","draft","Existing","updates","number","URL"]