Repost the journals
A transaction or invoice is posted when its journal entry carries a resolved account. When that account is missing only because the posting pipeline did not run, the row is ready and simply waiting. This skill lists those rows and offers one button that re-runs the pipeline for the whole workspace. It never lists a row that needs a category, an account, or a party decision.
This skill writes data rather than only reporting on it. It shows you what it will do, and changes nothing until you confirm.
npx skills add wellapp-ai/skills --skill repost-journalsAsk anything or use / for commands...
How the skill answers
Every step of the run, in order, with the card each one returns. A step that hands its work to another skill says which one.
- You ask
Did the accounting post?
- Read the posting gap, then re-run the pipeline for the rows that are readySkill usedrepost-journals
- You get
6 rows are ready to post and simply have not: 4 transactions and 2 supplier invoices, €18,240 for May. Nothing is wrong with them, the posting pipeline did not run. Re-run it and they book. It re-posts nothing already booked, so a second press is safe.
More skills to try
Every skill answers a different question from the same connected data. Add one, ask, and see the working.
Runway
Know how many months of cash you have at your current burn, with both sides of the division shown.
Cash position
Know how much cash you hold right now, with the accounts counted and the ones left out both stated.
Cost structure
See where your company's money actually goes, no spreadsheets required.
Receivables aging
See who owes you money, and how long they have been sitting on it.
Bills due
See what you owe and when, ordered by due date with a running total.
Rank clients by LTV
Find out who your best customers really are, ranked by what they've actually paid.
Frequently asked questions
What does re-triggering actually do?
It re-runs the same deterministic posting pipeline the system runs on its own, for the workspace's re-triggerable rows. It books nothing twice.
Why does it not let me pick an account?
A row that needs an account is not ready to post — it is a substantive blocker another step owns. This step lists only the rows that are ready.
What if Well is still processing the rows?
The read carries an in_flight_processing flag. While it is true, Well is still shaping the rows (enrichment in flight), so the skill polls and does not re-trigger until that work lands.
Ask your first question today
Connect your tools, then ask in plain language. Every answer traces back to the record behind it. Free to start.