agentleFS
dovoanhtruongdovoanhtruong/abap-agent-claudecode-workspace/.claude/skills/z-excel-fwk/SKILL.md

z-excel-fwk

Skill3 starsChanged 36 days agoNo licenceView on GitHub

Usage guide for the custom Excel export-from-template framework (ABAP package Z_EXCEL_LIBRARY + SAPUI5 library z.custom.excel.lib) — how to build the ABAP side (static RAP action printExcel returning ZABS_EX_LIB_ACTION_RETURN with a camelCase JSON sheets payload), how to AUTHOR the .xlsx template itself with the engine's tag grammar (${var}, ${image:x}, ${table:arr.field|merge}, ${rowType:L1}, ${x|qrcode}), how to build a MULTI-TEMPLATE file where each output sheet picks its own master sheet via the `templateSheet` field, and how to wire the Fiori app in BAS (zero-config: manifest library dependency + custom action whose press is the library handler; optional overrides in manifest sap.ui5/config/zExcelExport; legacy ext/controller/ExcelConfig.js still honored). Use this skill INSTEAD of reading the framework source whenever a task touches Excel export on this framework — creating or debugging a PrintExcel action, designing or generating an Excel template with mapping tags, adding a summary/second-layout sheet to an existing report, registering an excel_id template version, embedding a logo/QR code, or explaining why a tag did not resolve. Triggers include "Z_EXCEL_LIBRARY", "z.custom.excel.lib", "excel library", "excel template", "PrintExcel", "printExcel action", "ExcelConfig.js", "zExcelExport", "PrintExcelHandler", "ExcelExportHelper", "excel_id", "mapping tag", "templateSheet", "multi-sheet template", "export excel from template"; Vietnamese triggers "xuất excel theo template", "in excel", "tạo template excel", "làm report excel", "in nhiều sheet", "sheet tổng hợp", "mỗi sheet một design", "tag không đổ dữ liệu", "nhúng logo/QR vào excel", "setup excel library trên BAS", "gắn nút Print Excel". For OData service definition/binding use odata; for RAP BO modeling use rap; for generic ABAP SQL use abap-sql-amdp.

The file

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.