Business & Operations
Operations, strategy, finance, sales, support, management, and planning
Browse business & operations skills
Showing 26,281–26,304 of 32,374 skills
Use this skill when the user is building a fundraising / investor pitch deck — seed, Series A / B / C, convertible note, SAFE round, strategic raise. Trigger on: 'pitch deck', 'investor deck', 'Series A deck', 'Series B deck', 'Series C deck', 'fundraising deck', 'seed pitch', 'VC deck', 'raising capital', 'term sheet presentation'. Output is a single .pptx. This skill is a scene layer on top of officecli-pptx — inherits every pptx v2 rule (visual floor, grid, palettes, connector canon, Deliv...
Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.
End-to-end auto-factory driver — picks up beads + GH issues tagged factory, dispatches coders to drive worldai PRs to /green + /advice + /er, runs verifier ticks, repeats until done. Designed to work even when GH API is rate-limited (falls back to beads-only).
Use when a task may span sessions, get interrupted, or require resumable auditable progress. Runs long-horizon work under the HALT specification.
How VAT and the Estonian VAT return (käibedeklaratsioon / KMD) work in Merit Aktiva, and how to get them right from the elnora-merit CLI. Covers the tax-code model, paying the VAT, what feeds each KMD line, time-of-supply, and pulling supporting VAT figures. The KMD itself is generated and filed in the Merit UI — the API has no KMD endpoint. Use when: preparing or checking the VAT return, choosing a VAT/tax code, understanding a KMD line, reconciling VAT figures, or asking why the GL VAT bala...
The Estonian TSD (tulu- ja sotsiaalmaksu deklaratsioon) annexes that are NOT payroll: lisa 5 (gifts, donations, entertainment/vastuvõtukulud) and lisa 6 (expenses unrelated to business — fines, sunniraha, tax-authority interest). Covers what makes a TSD mandatory for a month, the 22/78 gross-up, the exact e-MTA form codes, and the cumulative annual allowance that is the single most common mistake. Merit Palk's "Saada TSD" sends the payroll annexes only — it cannot file these. Use when: tax-au...
How Stripe payments must be set up and recorded in Merit Aktiva — the canonical clearing-account method. Stripe is a payment intermediary, not your bank: never book the bank deposit as revenue (it arrives NET of fees). Each Stripe payout is booked as ONE summary GL batch — gross card sales as revenue + output VAT, Stripe fees as a separate expense, through a clearing account the real bank row then clears. Use when: setting up Stripe in Merit, booking Stripe payouts, reconciling card sales, de...
How to create, find, credit, and send sales invoices correctly in Merit Aktiva (müügiarve) via the elnora-merit CLI. Covers customer resolution, VAT tax-code selection, self-managed invoice numbering, prepayment invoices, credit notes, and delivery by e-mail / e-invoice. Use when: creating a sales invoice, billing a customer, issuing a credit note, recording a prepayment invoice, sending an invoice as an e-invoice or PDF, or finding/looking up an existing sales invoice. TRIGGERS: "create sale...
Which Merit Aktiva financial report answers which question, and how to read the output, via the elnora-merit CLI. Income statement, balance sheet, sales, purchase, customer debts, and customer payments — all read-only. Use when: pulling a profit & loss, balance sheet, sales or purchase report, checking what a customer owes, or listing customer payments. TRIGGERS: "income statement", "profit and loss", "P&L", "kasumiaruanne", "balance sheet", "bilanss", "sales report", "purchase report", "cust...
How to enter vendor bills (ostuarve) correctly in Merit Aktiva via the elnora-merit CLI — vendor resolution, invoice rows + VAT, posting straight to the ledger vs the approval queue (kinnitamata ostuarved / kinnitusring), purchase credit notes, and expense claims. For EU/foreign suppliers see the merit-reverse-charge skill. Use when: entering a purchase invoice, recording a vendor bill, booking a supplier receipt/expense, creating a draft invoice for approval, issuing a purchase credit note, ...
How to record payments and reconcile the bank statement correctly in Merit Aktiva (maksed / pank) via the elnora-merit CLI. The core skill is choosing the right transaction type for each line — customer receipt, vendor/tax payment, other income, or other expenditure — plus bank-statement import, settlements (tasaarveldus), prepayments, currency payments, and internal transfers. Use when: recording a payment, marking an invoice paid, importing a bank statement, reconciling the bank, netting a ...
How to read data out of Merit Palk via `elnora-merit palk` — the salary & hours report, the general-ledger batch (to post payroll into accounting), and the vacation obligation balance. All read-only POST queries. Use when: pulling the salaries & working-hours report, getting the GL journal for a payroll month to post into Aktiva/another ledger, or checking an employee's unused vacation days. TRIGGERS: "salary report", "hours report", "payroll report", "salaries and working hours", "GL batch",...
How to pull an LHV bank statement straight into Merit Aktiva without touching a file export — LHV's own MCP server returns camt.053 XML, which is exactly what Merit's bank-statement import accepts. Covers connecting LHV (OAuth2 + Smart-ID, read-only), the 31-day window, the multi-currency trap, and where the statement stops being the agent's job and becomes a match-and-confirm in the Merit UI. Use when: importing an LHV statement, reconciling the LHV bank in Merit, pulling transactions or bal...
Look up Estonian companies in the Business Register (äriregister) using the two FREE live services via `elnora-merit ariregister`: invoicing requisites (legal name, VAT number, status, address) by registry code, and e-invoice capability. Use to fill or verify customer/invoice details from the authoritative source, or to check whether a company can receive e-invoices before sending one. Use when: looking up a company's registry data, getting a VAT number or address by registry code, verifying ...
How to record Estonian foreign business trips (välislähetus) in Merit Aktiva correctly: tax-free daily allowance (välislähetuse päevaraha), the VAT treatment of flights and hotels (which is NOT reverse charge), paying a non-employee's travel via a käsundusleping, and client/partner meals (vastuvõtukulud). All figures are the current statutory limits — verify against Riigi Teataja, since the 2025 reform raised several of them and older blog figures are stale. Use when: booking per diem, a trip...
Merit Aktiva accounting — routes work to the elnora-merit CLI, slash commands, and agents. Use when: looking up or creating invoices, recording payments, checking financial reports, managing customers/vendors, or any Merit Aktiva accounting task. TRIGGERS: "merit", "merit aktiva", "aktiva", "invoice", "sales invoice", "purchase invoice", "create invoice", "unpaid invoices", "record payment", "customer balance", "vendor", "income statement", "profit and loss", "balance sheet", "VAT", "accounti...
Run a Pragmatic Institute Win/Loss analysis — understand why recent evaluators did or did not buy and the steps they took in their buying process. Use when a PM says "why did we win/lose", "win-loss", "why do deals slip", "churn reasons", "why did they pick the competitor", or "interview a lost prospect". Enforces the rule that win/loss is run by an objective party not involved in the sale, and evaluates the buying PROCESS, not the salespeople. Produces a Win/Loss Interview Guide and a Win/Lo...
Build a Pragmatic stakeholder communication plan and status updates that expose risk early and speak each audience's language. Use when the PM asks to manage stakeholders, plan comms, write an exec/status update, a project status report, a steering-committee update, or "keep everyone aligned". Covers the Identify→Analyze→Communicate steps, the Influence×Importance matrix, and the four metric categories. Produces a Stakeholder Communication Plan and a Status Update as a Markdown or Word .docx ...
Write market-driven, prioritized product requirements (a Market Requirements Document / MRD) the Pragmatic Institute way. Use when the PM asks for "requirements", "an MRD", "what should we build", "prioritize features", "market requirements", or wants development to stop saying "requirements aren't specific enough". Articulates each requirement as a persona's problem, prioritizes with Market Evidence × Impact, and groups them for delivery. Produces a Market Requirements Document as a Markdown...
Turn a prioritized set of requirements into a committed Pragmatic release plan — themed, sized, and signed. Use when the PM asks to plan a release, define MVP scope, commit a date, build a release charter, or "what goes in this release". Covers MVP done right, themes, the estimation ladder, the market window, and the scope/schedule/resources change levers. Produces a Release Charter as a Markdown or Word .docx artifact.
Build a Pragmatic Institute Strategy Matrix — a forced-choice 4×4 that decides who to win and what to build over a set time frame, and surfaces alignment between the product team and leadership. Use when the PM asks about product strategy, "where should we invest", "what should we build for whom", focus, prioritizing markets, or avoiding a spread-too-thin roadmap. Produces a Strategy Matrix as a Markdown or Word .docx artifact.
Build a Pragmatic Institute Product Canvas / business case to justify investing in an opportunity — the market-driven way. Use when the PM asks to "make the business case", "justify this to leadership", "size the market", "should we buy, build or partner", "what's the ROI", "build a product canvas", or "get buy-in for this idea". Frames the opportunity as Value Proposition, Value Creation and Value Capture, sizes the market, runs the Buy/Build/Partner decision, and ends in a go/no-go recommen...
Assemble a full, market-driven Product Requirements Document (PRD) the Pragmatic way — problem-before-solution, evidence-based, persona-first. Use when the PM asks for a PRD, product spec, feature doc, "write the requirements doc", or "put it all together for the team". Pulls in existing personas, positioning, market problems, requirements and use scenarios if present, and gathers anything missing inline. Produces a Product Requirements Document as a Markdown or Word .docx artifact.
Create Pragmatic Institute buyer and user personas — archetypes grounded in real market evidence, written so the team stays connected to real people. Use when the PM asks about personas, "who is the buyer", "who is the user", target audience, ICP, or wants to make a persona come alive. Distinguishes the buyer (makes/influences the purchase) from the user (uses it daily). Produces a Buyer Persona and a User Persona as a Markdown or Word .docx artifact.