Skip to content
TrustedSkillsbeta
Back to all skills

Reading Payment Statement

Checked
kazukinagata·vlatest·other·MIT

Analyzes payment statements to extract key details like amounts due, dates, and account numbers with high accuracy.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add kazukinagata/shinkoku --skill reading-payment-statement -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

kazukinagata

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned kazukinagata/shinkoku at 607574d5e5.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
607574d5e5
Manifest
skills/reading-payment-statement/SKILL.md
Scanned
2 files, 125 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows an AI agent to extract information from payment statements. It can identify key details such as the total amount due, due date, and account number. The extracted data can then be used for tasks like budgeting or reconciliation.

When to use it

  • You need to quickly understand the outstanding balance on a bill.
  • You want to automate tracking of payment deadlines.
  • You're building an application that requires parsing payment statement details.
  • You need to reconcile payments with internal records.

Key capabilities

  • Extracts total amount due from statements.
  • Identifies the payment due date.
  • Locates and retrieves account numbers.

Example prompts

  • "Can you read this payment statement and tell me how much I owe?" (followed by providing the statement)
  • “What is the due date on this bill?” (followed by providing the statement)
  • "Extract the account number from this payment statement." (followed by providing the statement)

Tips & gotchas

The accuracy of extraction depends heavily on the format and clarity of the payment statement. Statements with unusual layouts or poor image quality may yield less reliable results.