agentleFS
williamcorrea23williamcorrea23/sap-router-skill/.agents/skills/abap-docs-reference/SKILL.md

abap-docs-reference

Skill1 starsChanged 4 months agoMITView on GitHub

Use the enhanced ABAP keyword documentation corpus and its Markdown build pipeline from eduardocopat/abap-docs as an offline reference for ABAP language questions.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the pinned eduardocopat/abap-docs snapshot as a documentation corpus and build reference.

    line 10
  2. Very specific:

    Search the snapshot under bundled/skills/eduardocopat-abap-docs/ for the ABAP statement or concept.

    line 14
  3. Distinctive:

    Prefer exact keyword pages and examples over secondary summaries.

    line 15
  4. Distinctive:

    When the snapshot does not contain the generated page, use the router's configured documentation-search capability or official SAP …

    line 17
  5. Very specific:

    Treat SAP documentation content as SAP-owned material.

    line 26
  6. Distinctive:

    Check the syntax against the target ABAP release and distinguish documented behavior from recommendations or inferred behavior.

    line 30

≈ “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

ABAP Docs Reference

Use the pinned eduardocopat/abap-docs snapshot as a documentation corpus and build reference.

Workflow

  1. Search the snapshot under bundled/skills/eduardocopat-abap-docs/ for the ABAP statement or concept.
  2. Prefer exact keyword pages and examples over secondary summaries.
  3. State the SAP release context when the source exposes it; do not assume modern syntax is available on older NetWeaver releases.
  4. When the snapshot does not contain the generated page, use the router's configured documentation-search capability or official SAP documentation.
  5. Cite the local source path or authoritative page used.

Build pipeline

The upstream project downloads SAP documentation, parses it into Markdown, and builds a MkDocs site. Do not start the upstream download automatically: it is network-heavy and may take hours. Run it only when the user explicitly asks to rebuild the corpus and the upstream prerequisites are installed.

Safety and licensing

Treat SAP documentation content as SAP-owned material. Summarize and quote sparingly. The upstream tooling is MIT-licensed; its LICENSE.md is preserved in the pinned snapshot.

Verification

Check the syntax against the target ABAP release and distinguish documented behavior from recommendations or inferred behavior.

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.