메뉴
Use when exporting project artifacts (package.json, lockfiles, .cdsrc.json, default-env.json, .npmrc) from a running SAP BTP CF app.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | cf-export |
| description | Use when exporting project artifacts (package.json, lockfiles, .cdsrc.json, default-env.json, .npmrc) from a running SAP BTP CF app. |
Use cf-export to pull exact CAP/CF project artifacts from a live Cloud Foundry container. This is the CLI equivalent of the "Export" feature in the SAP Tools VS Code extension. It is useful for local development setup, debugging deployment issues, or capturing the exact lockfile and config that a running app was built with.
If cf-export is missing, install it: npm install -g @saptools/cf-export
-a / --app is always required. --region, --org, --space are optional. If the user only mentions the app name, try short form first. The tool checks if a target is already set in the environment. Only ask the user for region/org/space and pass explicit flags when the tool errors with "Error: --region is required" (or --org / --space).--remote-root (the "root url") when the app files live in a non-standard path inside the container (common for multi-package or custom build roots).--file to be selective.Export all artifacts (short form):
cf-export -a my-cap-app --out ./exported
With full flags:
cf-export -r ap10 -o my-org -s dev -a my-cap-app --out ./exported
With custom remote root:
cf-export -a my-cap-app --remote-root /home/vcap/app/srv --out ./out
Selective files:
cf-export -a my-cap-app --file package.json --file pnpm-lock.yaml --file default-env.json
--remote-root /path/inside/container.SAP_EMAIL / SAP_PASSWORD are set and the cf CLI can reach the region.--region explicitly.Live CF commands require the app to be running and SSH enabled for file fetches.
@saptools/cf-files — lower-level file download and gen-env.@saptools/cf-sync — provides the region catalog.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.