메뉴
Use when a task involves listening to or publishing messages to SAP Event Mesh on SAP BTP Cloud Foundry. Useful for interacting with event queues and topics directly from the CLI without needing an external client.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when indexing, linking, tracing, graphing, inspecting, diagnosing, cleaning, testing, or changing SAP CAP service-to-service flows with the service-flow CLI or @saptools/service-flow package, especially for multi-repository workspaces, SQLite state, handler implementation selection, runtime placeholders, dynamic targets, parser/linker evidence, and deterministic validation.
Use when a task involves running SQL, inspecting saved query refs, or discovering schemas, tables, and columns in SAP HANA Cloud databases bound to SAP BTP Cloud Foundry apps through the cf-hana CLI. Covers selector/app targeting, binding choice, read-only SELECT workflows, explicit writes, compact or structured output, saved result refs, and local result inspection.
Use when working with Jira Cloud through the jira CLI, including assigned issue lists, issue details with local inline image files, remote links, transitions, safe issue assignment, worklogs, descriptions, summaries, and comments.
Guide on how to remotely debug SAP BTP Cloud Foundry Node.js applications by combining deployed compiled JS discovery, Cloud Foundry log evidence, live HTTP request/response traces, runtime inspector snapshots, and read-only HANA evidence when debugging errors or exploring runtime behavior.
Use when analyzing SAP CAP CDS/HANA model structure with hana-lens, including building a compact CSN cache, fuzzy or regex entity search, field search, incoming reference lookup, dense entity descriptions, and safe association expansion.
Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
| name | cf-event-mesh |
| description | Use when a task involves listening to or publishing messages to SAP Event Mesh on SAP BTP Cloud Foundry. Useful for interacting with event queues and topics directly from the CLI without needing an external client. |
Use cf-event-mesh to interact with SAP Event Mesh (default plan, not Advanced Event Mesh) via the command line. It discovers credentials automatically from cf env <app-name> and allows you to listen to queues using AMQP or publish messages to queues/topics using REST.
If cf-event-mesh is missing, install it from @saptools/cf-event-mesh: npm install -g @saptools/cf-event-mesh.
enterprise-messaging service.cf login) and targeting the correct space (cf target -s <space> -o <org>) where the app resides.Use listen to subscribe to an AMQP queue and output incoming messages to stdout:
cf-event-mesh listen <app-name> <queue-name>
cf-event-mesh listen <app-name> <queue-name> --ack
Note on Acknowledgements: By default, the listener does NOT acknowledge messages (
autoAck: false), meaning messages remain in the queue and can be processed by real consumers later. This is safe for debugging. Use the--ackflag if you explicitly want to acknowledge (remove) the messages from the queue as they are received.
Use publish to send a message payload to a topic or queue via REST:
cf-event-mesh publish <app-name> queue <queue-name> '{"hello":"world"}'
cf-event-mesh publish <app-name> topic <topic-name> '{"hello":"world"}'
The payload should be a valid string, typically JSON.
listen command streams incoming AMQP messages to stdout. It will keep running until interrupted (Ctrl+C).publish command outputs a success confirmation or an error message and then exits.VCAP_SERVICES dynamically using cf curl /v3/apps/<guid>/env.Do not paste credential values (like clientid, clientsecret, uri) in clear text when reporting back.
cf-event-mesh relies on the enterprise-messaging service bindings inside the provided <app-name>.clientid, clientsecret, and tokenendpoint from the service binding.listen, it connects via AMQPS to the URI provided in the amqp10ws protocol array.publish, it connects via HTTPS to the URI provided in the httprest protocol array.If the command fails with App not found, verify that the app name is correct and you are targeting the correct CF space:
cf target
cf apps
If the command fails with No Event Mesh binding found, verify that the app is actually bound to an enterprise-messaging service instance:
cf services
cf env <app-name>
If publish fails with HTTP 403 Forbidden or 404 Not Found, ensure the topic or queue exists in the Event Mesh dashboard and the service key/binding has the appropriate publish rules (e.g., namespace prefixes).
If listen connects but receives no messages, verify the queue name (often prefixed with a namespace like company/app/1/MyQueue) and check if other consumers are actively pulling and acknowledging messages before the CLI can see them.