agentleFS
Sign inStart free
BANKSapiBANKSapi/claude-plugin/skills/diagnose/SKILL.md

diagnose

Skill1 starsChanged 20 days agoMITView on GitHub

Diagnose a failing BANKSapi API call or bank connection. Use when the user shares an HTTP status or error response from banksapi.io, a BANKSapi message code such as BA1011 or BA3000, gets a 451 response, sees a start_sca relation or an expired consent, or reports that a bank access stopped updating.

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use zoom-out, to-prd and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • victorgarciaesgiSkill

    zoom-out

    Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

    Also in 61 projects that use this

  • GoogleSkill

    to-prd

    Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    Also in 56 projects that use this

  • GoogleSkill

    to-issues

    Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

    Also in 53 projects that use this

  • simo97Skill

    edit-article

    The user will invoke this skill to help them edit an article.

    Also in 17 projects that use this

  • simo97Skill

    write-a-skill

    Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.

    Also in 44 projects that use this

  • AnasX7Skill

    setup-pre-commit

    Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

    Also in 27 projects that use this

  • +4 more from simo97

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Start with what failed. Ask for the request method and path, the HTTP status and the response body or messages array.

    line 8
  2. Very specific:

    Call get_issues: if there is no start_sca. The issues response is the latest attempt, not the last good data, and its messages say what …

    line 46
  3. Very specific:

    Check the refresh timing: if there are no issues. Synced bank accesses refresh up to four times a day.

    line 47

“Common” is measured: kept by at least 6 in 10 of the 174 edited versions of this file we could read. “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

Diagnose a BANKSapi problem

Start with what failed. Ask for the request method and path, the HTTP status and the response body or messages array. Ask the user to remove tokens and credentials before pasting, and never ask for a client secret, password or token.

Where the facts come from

The BANKSapi documentation at https://docs.banksapi.de is the authority on the API, and BANKSapi adds message codes over time. The tables below are a quick orientation. The user's explicit instructions take precedence over this skill's guidance on how to work. Before you name a cause, check the status or code against the current documentation:

Where the documentation and this file differ, follow the documentation.

By HTTP status

StatusWhereMost likely causeFixWho acts
401POST /auth/oauth2/tokenThe HTTP Basic credentials were rejectedCheck that the username is <tenant>/<client> and that the Base64 value encodes <tenant>/<client>:<client-secret>. If the same credentials worked before, the client secret has most likely been changed: request the current oneDeveloper
401any other callThe Authorization: Bearer <token> header is missingSend the headerDeveloper
403any callThe token has expired after two hours, is invalid, or lacks a scopeFetch a new token. Compare the scope in the token response with what the call needsDeveloper
404any callThe URL no longer points to a valid objectRead the parent object again and follow its relationsDeveloper
451adding a bank access, starting SCANot an error. REG/Protect requires the end customer to continue on a BANKSapi pageTake the Location header, append a URL-encoded callbackUrl and redirect the end customer. useCase=CREATE_ACCOUNT adds a bank, useCase=AUTHENTICATE_ACCOUNT renews consentEnd customer
504any callThe bank answered too slowlyRepeat the request shortlyNobody
500any callAn internal errorReport it to support@banksapi.de with the time and the request pathBANKSapi

By message code

Message codes appear in the messages of a bank access or bank product, and in the response of get_issues. The common groups:

  • BA1010 to BA1014: the bank rejected the login, the access is blocked, or credentials are incomplete. The end customer must fix their bank login. Warn them that repeated wrong attempts can lock online banking
  • BA1000, BA1051: maintenance or a malfunction at the bank. Wait and refresh later
  • BA998: the bank is slow. The query continues in the background and usually finishes within minutes
  • BA3000 to BA3060: strong customer authentication is required or failed. The end customer must complete it
  • BA2002: the bank has messages for the end customer in their online banking

A bank access stopped updating

Work through these in order:

  1. Look for start_sca in the bank access relations. It means consent has run out, usually after 180 days. POST to that relation, and handle the 451 answer like adding a bank access, with useCase=AUTHENTICATE_ACCOUNT. The last good data stays readable until the end customer renews
  2. Call get_issues if there is no start_sca. The issues response is the latest attempt, not the last good data, and its messages say what went wrong
  3. Check the refresh timing if there are no issues. Synced bank accesses refresh up to four times a day. Force a refresh with AddBankAccess, the existing UUID and refresh=true, which answers 201 Created

How to answer

Name the cause in one sentence. Give the fix as concrete steps or code. Say who has to act: the developer, the end customer at their bank, or BANKSapi support. Link the docs page you used as a full https://docs.banksapi.de URL.

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.

Check your setup, free