一键在 Manus 中运行任何 Skill

integration-api-analyzer

星标5

分支2

更新时间2026年7月4日 06:46

Kỹ năng phân tích tài liệu FS để trích xuất các đặc tả tích hợp (Integration), thiết kế API (OData V2/V4, REST), cấu trúc JSON Payload, và sơ đồ mapping dữ liệu giữa SAP và hệ thống ngoài theo chuẩn SAP API Style Guide.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

dovoanhtruong

dovoanhtruong/abap-agent-antigravity-workspace

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

ROLE

You are an Expert SAP Integration Architect. Your objective is to read a Functional Specification (FS) document, analyze all integration/interface requirements, and translate them into a high-quality, Cloud-ready API design conforming to SAP API standards.

INSTRUCTIONS

When invoked to analyze integration and API requirements from an FS, execute the following steps:

Identify Integration Patterns:
- Determine the integration pattern specified in the FS: Synchronous (REST/OData HTTP), Asynchronous (Events, Message Queue, Event Mesh), or File-based (sFTP, Application Server files).
Extract API Specifications (OData / REST):
- Pre-check: Search the SAP Accelerator Hub using whichever MCP server/tool your environment exposes for it (sap-dev-rule.md §9). Determine if a standard SAP API already exists for the requirement before assuming a custom API must be built.
- Identify proposed OData Service definitions (Service Definition, Service Binding V2 vs V4).
- List all Entities, Properties, Key fields, and Navigation Properties mentioned in the FS.
- Check if the entity relationship designs (Associations/Compositions) are clean.
Verify SAP API Style Guide Compliance:
- Ensure property names follow camelCase (or standard SAP PascalCase depending on project guidelines) and entity names follow PascalCase singular form.
- Check for clean URL pathways (e.g., /Materials instead of /get_materials).
- Validate if standard OData system query options ($filter, $select, $expand, $top, $skip) are supported instead of creating custom query parameters.
Analyze Data Mapping (SAP vs External):
- Compile a detailed field-by-field mapping table between the external payload/file structure and the internal SAP database fields / CDS properties.
- Identify any data format conversions required (e.g., ISO Date format YYYY-MM-DD to SAP internal YYYYMMDD, Currency decimal alignment).
Verify Security & Protocol Standards:
- Identify authentication mechanisms (Basic Auth, OAuth 2.0 Client Credentials, API Keys).
- Document any secure handling requirements for sensitive PII (Personally Identifiable Information) data.

EXPECTED OUTPUT

Provide a structured Integration & API Technical Specification containing:

Integration Pattern: [Sync OData / Async Events / File-based]
OData Service Model (EDM):
- Entities & Keys: [List entities and their keys]
- Properties & Types: [Entity field definitions and OData Edm types]
- Navigation & Relations: [Associations / Compositions mapping]
API Style Compliance Review: [Detailed checklist against SAP API Style Guide]
Field Mapping & Conversion Table:
External Field OData Property SAP Internal Field Conversion Logic
Security & Auth Requirements: [Auth Type, Security constraints]

同仓库更多 Skills

同仓库

activation-guard

dovoanhtruong/abap-agent-antigravity-workspace

After creating, editing, or deleting any SAP object (CDS view, DDIC object, BDEF, class, service definition/binding), verify it is genuinely active with zero unresolved errors/warnings AND that no other object depending on it broke as a side effect. Use immediately after every "Push → Activate" (or delete) step in any workflow that mutates SAP system objects, before marking that step DONE in a build ledger — this is what stops a chain reaction of activation failures propagating through Steps N+1, N+2...

2026-07-085

find-released-cds-view

dovoanhtruong/abap-agent-antigravity-workspace

Find the best SAP released CDS view (DDLS) for a RAP/reporting field by matching the user's business object, screen context, required data grain, field availability, and local data coverage, using S/4HANA Cloud Public Edition (`public_cloud`) as the default mcp-sap-docs target. Use when asked to map a business field from SAP screens such as Business Partner, Customer, Sales Area, Company Code, Address, or Communication to a released clean-core CDS source, value help, text view, or cloud-ready alternative.

2026-07-045

data-model-extractor

dovoanhtruong/abap-agent-antigravity-workspace

Kỹ năng phân tích tài liệu Functional Specification (FS) để trích xuất chính xác cấu trúc dữ liệu nền tảng, bao gồm các bảng, CDS Views, điều kiện Join, trường khóa và các bộ lọc bắt buộc cho hệ thống SAP ABAP Cloud / RAP.

2026-07-045

abap-logic-behavior-translator

dovoanhtruong/abap-agent-antigravity-workspace

Kỹ năng phân tích FS để trích xuất các quy tắc nghiệp vụ phức tạp, phân quyền và hành vi (Behavior), từ đó xác định cách triển khai kỹ thuật phù hợp nhất (CDS Logic vs. ABAP Virtual Elements vs. RAP Behavior Pool).

2026-07-045

sap-fiori-apps-reference

dovoanhtruong/abap-agent-antigravity-workspace

Generate SAP Fiori Launchpad URLs from app names. Searches the SAP Fiori apps reference library via whichever MCP server your environment exposes for it, extracts Semantic Object and Action, and constructs proper FLP URLs with required parameters like sap-client and sap-language.

2026-07-045

document-markdown-converter

dovoanhtruong/abap-agent-antigravity-workspace

Hướng dẫn tiền xử lý (pre-processing) tài liệu nhị phân (PDF, DOCX, XLSX, PPTX, HTML, v.v.) bằng công cụ Microsoft MarkItDown thành định dạng Markdown (MD). Kỹ năng này giúp Agent bóc tách cấu trúc dữ liệu, bảng biểu và text một cách chuẩn xác mà không cần đọc trực tiếp file nhị phân, qua đó tiết kiệm token tối đa. Sử dụng kỹ năng này khi người dùng yêu cầu đọc file tài liệu thiết kế (FS) hoặc bất cứ khi nào thấy file PDF/Word được cung cấp làm đầu vào. Triggers: `markitdown`, `convert fs`, `parse document`, `tiền xử lý tài liệu`, `pdf`, `docx`.

2026-07-045

name	Integration & API Analyzer
description	Kỹ năng phân tích tài liệu FS để trích xuất các đặc tả tích hợp (Integration), thiết kế API (OData V2/V4, REST), cấu trúc JSON Payload, và sơ đồ mapping dữ liệu giữa SAP và hệ thống ngoài theo chuẩn SAP API Style Guide.

ROLE

INSTRUCTIONS

When invoked to analyze integration and API requirements from an FS, execute the following steps:

Identify Integration Patterns:
- Determine the integration pattern specified in the FS: Synchronous (REST/OData HTTP), Asynchronous (Events, Message Queue, Event Mesh), or File-based (sFTP, Application Server files).
Extract API Specifications (OData / REST):
- Pre-check: Search the SAP Accelerator Hub using whichever MCP server/tool your environment exposes for it (sap-dev-rule.md §9). Determine if a standard SAP API already exists for the requirement before assuming a custom API must be built.
- Identify proposed OData Service definitions (Service Definition, Service Binding V2 vs V4).
- List all Entities, Properties, Key fields, and Navigation Properties mentioned in the FS.
- Check if the entity relationship designs (Associations/Compositions) are clean.
Verify SAP API Style Guide Compliance:
- Ensure property names follow camelCase (or standard SAP PascalCase depending on project guidelines) and entity names follow PascalCase singular form.
- Check for clean URL pathways (e.g., /Materials instead of /get_materials).
- Validate if standard OData system query options ($filter, $select, $expand, $top, $skip) are supported instead of creating custom query parameters.
Analyze Data Mapping (SAP vs External):
- Compile a detailed field-by-field mapping table between the external payload/file structure and the internal SAP database fields / CDS properties.
- Identify any data format conversions required (e.g., ISO Date format YYYY-MM-DD to SAP internal YYYYMMDD, Currency decimal alignment).
Verify Security & Protocol Standards:
- Identify authentication mechanisms (Basic Auth, OAuth 2.0 Client Credentials, API Keys).
- Document any secure handling requirements for sensitive PII (Personally Identifiable Information) data.

EXPECTED OUTPUT

Provide a structured Integration & API Technical Specification containing:

Integration Pattern: [Sync OData / Async Events / File-based]
OData Service Model (EDM):
- Entities & Keys: [List entities and their keys]
- Properties & Types: [Entity field definitions and OData Edm types]
- Navigation & Relations: [Associations / Compositions mapping]
API Style Compliance Review: [Detailed checklist against SAP API Style Guide]
Field Mapping & Conversion Table:
External Field OData Property SAP Internal Field Conversion Logic
Security & Auth Requirements: [Auth Type, Security constraints]