bdc-troubleshooter

bdc-troubleshooter is a skill for Claude Code from MarioDeFelipe/sap-bdc-plugin. It costs 249 tokens per session (2,572 once invoked), scanned A, original, MIT.

A troubleshooting guide for specific SAP Business Data Cloud and Databricks failures, based on matching symptoms to SAP Notes, which are official support documents.

In plain words
What is it for?
Looking up fixes for supported provisioning, publishing, identity, hostname, data-product, sharing, and related failures.
Why use it?
It gives a targeted cause and fix when the user provides a supported error, failure description, or SAP Note number.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the sap-bdc plugin — 7 skills, 4 commands, 1 MCP server shipped together

Good fit Looking up fixes for supported provisioning, publishing, identity, hostname, data-product, sharing, and related failures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mariodefelipe/sap-bdc-plugin/bdc-troubleshooter
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add MarioDeFelipe/sap-bdc-plugin --skill bdc-troubleshooter
Clone the repo
git clone --depth 1 https://github.com/MarioDeFelipe/sap-bdc-plugin

Made for: Claude Code.

Or install sap-bdc, the plugin that ships this one along with the rest of its 7 skills, 4 commands, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for bdc-troubleshooter

README.md
[![agentmods](https://agentmods.dev/badge/skills/mariodefelipe/sap-bdc-plugin/bdc-troubleshooter/github.svg)](https://agentmods.dev/skills/mariodefelipe/sap-bdc-plugin/bdc-troubleshooter)
Your own site
<a href="https://agentmods.dev/skills/mariodefelipe/sap-bdc-plugin/bdc-troubleshooter"><img src="https://agentmods.dev/badge/skills/mariodefelipe/sap-bdc-plugin/bdc-troubleshooter/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for bdc-troubleshooter

Your own site · 80×15
<a href="https://agentmods.dev/skills/mariodefelipe/sap-bdc-plugin/bdc-troubleshooter"><img src="https://agentmods.dev/badge/skills/mariodefelipe/sap-bdc-plugin/bdc-troubleshooter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 249 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,572 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00249 $0.02572
Opus 5 $0.00125 $0.01286
Sonnet 5 $0.00050 $0.00514
Haiku 4.5 $0.00025 $0.00257

Measured 11d ago against content hash 50c0f0a918d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

bdc-troubleshooter scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/bdc-troubleshooter/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SAP BDC Troubleshooter (symptom-lookup only)

Narrow skill: given an error message or a described failure, return the matching SAP Note, the one-line cause, and concrete steps — nothing else. Curated against 22 SAP Notes (18 from the 2026-04-13 batch + 4 new from the 2026-04-15 batch) plus 4 procedural rules from the 2026-05-02 SAP help.sap.com batch.

Scope rule

In scope (use this skill):

  • User pastes an error message or stack trace
  • User cites an SAP Note number
  • User describes a failure whose symptom matches the tables below

Out of scope (route elsewhere):

  • "How do I set up BDC?" → bdc-onboarding
  • "How do I manage users / configure SCIM / monitor capacity?" → bdc-core-admin
  • "How do I publish / enrich a catalog asset?" → bdc-governance-catalog
  • "How does BDC Connect / Delta Sharing work?" → bdc-connect-sharing
  • "How do I install an intelligent app?" → bdc-intelligent-apps
  • "How do I work with SAP Databricks?" → sap-databricks

Workflow

  1. Identify the symptom in the tables below.
  2. If an MCP tool matches (the sap-bdc server exposes diagnose_share_error, validate_tenant_hostname, check_deletion_vectors, cleanup_orphaned_data_product), call it first. Don't paraphrase — call the tool and cite its output.
  3. Cite the SAP Note by number. Never invent note numbers.
  4. Give the resolution as numbered steps, not prose.
  5. Fallback: unknown symptoms → SAP Note 3653192 (main troubleshooting guide) + SAP Note 3568017 (how to file a support case).

Symptom → SAP Note index

Provisioning

Symptom SAP Note Fix
BDC Core provisioning hangs indefinitely 3652165 tenantHostName must match [a-z0-9-]+ — no uppercase, no leading/trailing hyphens. Delete failed instance, retry lowercase. Pre-check with validate_tenant_hostname MCP tool.
"The host name XXX is already being used" 3705747 Hostname taken in that region. Pick different.
SAC tenant stuck at "Processing" 3605796 SAC licenses not assigned. Go back and assign them.
Can't find BDC provisioning with BTPEA/CPEA 3599696 BDC does NOT use CPEA/BTPEA credits. Buy BDC offering separately; existing tenants can't migrate.
How do I provision SAP Datasphere? 3459708 BDC model: enable BDC Core first, then provision DS tenant. BTPEA/CPEA: separate flow.

Read the full file on GitHub · 125 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 125 lines · 249 tokens per session scan A 50c0f0a918d9

Subscribe to this mod's changes

bdc-troubleshooter is a skill published in the GitHub repository MarioDeFelipe/sap-bdc-plugin (9 stars, last pushed 4mo ago), licensed MIT. It adds 249 tokens to every session and 2,572 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens