agentleFS
williamcorrea23williamcorrea23/sap-router-skill/.agents/skills/sap-api-style/SKILL.md

sap-api-style

Skill1 starsChanged 4 months agoMITView on GitHub

SAP API documentation standards — OData API documentation guidelines, REST API style guide, OpenAPI/Swagger specs for SAP services, API naming conventions, SAP API Business Hub documentation requirements. Use when documenting SAP APIs, creating OpenAPI specs for SAP services, or reviewing API documentation against SAP standards.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All HTTP methods documented (GET, POST, PUT, PATCH, DELETE)

    line 68

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SAP API Style Guide

API documentation standards following SAP guidelines.

OData API Naming

EntityConventionExample
Entity SetPlural NounProducts, SalesOrders
Entity TypeSingular NounProduct, SalesOrder
PropertyPascalCaseMaterialNumber, CreatedAt
Navigation PropertyPrefix "to_"to_ProductText, to_Supplier
Function ImportVerb-NounGetTopCustomers, ValidateOrder

OpenAPI Document Structure

openapi: 3.0.3
info:
  title: Product Management API
  version: "1.0.0"
  description: |
    Manages product master data in SAP S/4HANA.
    Scope: MM module, product lifecycle from creation to archival.
servers:
  - url: https://my-s4hana.sap.com/sap/opu/odata/sap/Z_PRODUCT_API
paths:
  /Products:
    get:
      summary: List products
      parameters:
        - name: $filter
          in: query
          description: OData filter (e.g. MaterialType eq 'FERT')
          schema: { type: string }
      responses:
        '200':
          description: Product list
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ProductsList'
    post:
      summary: Create product
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ProductCreate'

Documentation Checklist

  1. API title and version
  2. Authentication method (Basic Auth, OAuth2, API Key)
  3. Rate limits
  4. Error response format (use BAPIRET2 structure)
  5. All HTTP methods documented (GET, POST, PUT, PATCH, DELETE)
  6. Query parameters: $filter, $expand, $top, $skip, $orderby, $select
  7. Example request and response for each endpoint
  8. CSRF token requirement (for write operations against SAP Gateway)

SAP API Business Hub

Publish APIs to: https://api.sap.com Requirements: OpenAPI 3.0 spec + SAP API Business Hub account.

Gotchas

  • OData $filter syntax differs from REST query parameters
  • SAP Gateway requires X-CSRF-Token header for POST/PUT/PATCH/DELETE
  • Error responses use sap-message format, not RFC 7807 Problem Details

Download now (ZIP)

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.