autonomous-loop
Iterate until success or limit, composing existing skills with Jidoka integration
Build a profit & loss statement (compte de résultat / income statement) from a Well workspace. Use when the user asks for a P&L, income statement, compte de résultat, revenue vs expenses, or net result over a period.
$ npx -y skills add WellApp-ai/Well --skill compte-de-resultat --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/compte-de-resultatContext preview
The summary Claude sees to decide when to auto-load this skill.
Build a profit & loss statement (compte de résultat / income statement) from a Well workspace. Use when the user asks for a P&L, income statement, compte de résultat, revenue vs expenses, or net result over a period.
name: compte-de-resultat description: Build a profit & loss statement (compte de résultat / income statement) from a Well workspace. Use when the user asks for a P&L, income statement, compte de résultat, revenue vs expenses, or net result over a period.
A correct income statement comes from the **posted accounting ledger**, not from raw invoices. Well's sync/posting pipelines post invoices and bank transactions into `journal_entries` against `ledger_accounts`; that posted data already handles classification, accruals, and settlement that a raw-invoice sum misses.
1. **Discover the schema first** (see `well:querying-well-data`):
2. **Scope the period** with a `whereClause` on the posting/entry date (e.g. `_gte` start, `_lte` end). 3. **Aggregate by account**: sum the posted amounts per ledger account, then group revenue accounts and expense accounts. 4. **Net result** = total produits (revenue) − total charges (expenses).
If `journal_entries` / `ledger_accounts` return no rows for the workspace, the books may not be posted yet. Say so explicitly, and only then offer an invoice-based **approximation** — clearly labelled as an estimate, not the compte de résultat — built from `invoices` (issued = revenue proxy, received = expense proxy) over the period.
Group the output as: Produits (revenue) lines → total; Charges (expense) lines → total; **Résultat net**. Note the currency and the period. Offer a month-by-month or category breakdown as a follow-up.
Iterate until success or limit, composing existing skills with Jidoka integration
Generate and maintain BPMN 2.0 diagrams linked to Gherkin scenarios
Research best-in-class products using Browser MCP and WebSearch
Systematic debugging with MCP integration, auto-invoke from qa-commit, Phase 7 Harden