← KontoCSVCONTENT HISTORY
WHAT CHANGED
Update to KontoCSV
Snapshot Oct 24, 2026 · 13:44 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save KontoCSV and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Inspect bank, card or payment statement PDFs and transaction CSV files, then prepare and run supported accounting exports with an authenticated KontoCSV account when the user has enough existing credits.",
"included_files": [],
"name": "kontocsv-bank-statement-conversion",
"skill_md_contents": "---\r\nname: kontocsv-bank-statement-conversion\r\ndescription: Inspect bank, card or payment statement PDFs and transaction CSV files, then prepare and run supported accounting exports with an authenticated KontoCSV account when the user has enough existing credits.\r\n---\r\n\r\nUse this skill when the user wants structured accounting data from a bank statement, credit-card statement, payment statement or transaction CSV.\r\n\r\n1. If the host provides an attached PDF or CSV as a file parameter, call `ingest_attached_bank_statement`. If direct attachment transfer is unavailable, call `create_secure_upload_session` only when the host can upload the user's file to the returned secure destination.\r\n2. Call `inspect_bank_statement` before any conversion. Report relevant document facts and supported export profiles. Do not spend credits during inspection.\r\n3. If the user only asked to inspect, validate or understand compatibility, stop after inspection.\r\n4. For a requested conversion, call `prepare_bank_statement_conversion`. This tool may report only existing credit availability and conversion requirements. It must not be used to advertise prices, purchases or upgrades.\r\n5. If the result is `insufficient_credits`, explain that the connected account does not currently have enough existing credits. Do not offer a price, checkout URL, subscription, upgrade or purchase flow inside the plugin.\r\n6. If the result is `ready`, tell the user the required and available credit counts and ask for explicit confirmation before starting the conversion. Do not set `confirmedByUser` to true unless the user has explicitly confirmed the conversion after seeing the credit requirement.\r\n7. After confirmation, call `convert_bank_statement_for_accounting` once with the prepared quote token.\r\n8. Use `get_conversion_status` for the already-started job. Never start a duplicate conversion merely because a job is still queued or processing.\r\n9. When the job permits a download, call `download_accounting_export`. If the result is marked `review_required`, say so clearly instead of describing it as fully validated.\r\n10. Never invent opening balances, closing balances, account identifiers, currencies or transactions. If MT940 or CAMT.053 is unavailable because balance evidence is insufficient, report that limitation and use another supported format only if the user requests it.\r\n11. Never request bank-login credentials, passwords, TANs, payment-card details or other authentication secrets.\r\n12. Do not use this workflow for unrelated documents or for general document summarization.\r\n\r\nKontoCSV's directory profile uses only credits already available in the connected account. Purchases and checkout are outside this plugin.\r\n"
}SHA-256 of public snapshot: e171dd0c7ef9b497303c449742a714a6872219b58640ef92f69c399b32974a06