Help us improve
Share bugs, ideas, or general feedback.
From advisory-essentials
Drafts a clean first-pass engagement or scoping letter for advisory, accounting, audit, tax, or FP&A work from a short set of deal parameters, covering scope and deliverables, fees and basis, client and practitioner responsibilities, timeline, and standard generic limitation-of-liability, confidentiality, and independence caveat blocks. Use when a finance professional needs to turn brief engagement notes into a structured letter ready for partner review, when onboarding a new client or project, or when refreshing scope on a renewal. Produces a generic professional template grounded in public standards (ISA 210 terms-of-engagement principles, IESBA Code, OECD and EU VAT references where tax is in scope), not any firm proprietary wording.
npx claudepluginhub kimonarrow/ledgerskills --plugin advisory-essentialsHow this skill is triggered — by the user, by Claude, or both
Slash command
/advisory-essentials:engagement-letter-drafterThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill turns a handful of deal parameters into a structured, professional first-pass engagement (or scoping) letter that a partner, director, or manager can review and refine. It is for practitioners in advisory, accounting, audit, tax, and FP&A who need a consistent, defensible starting point fast, without copying any firm's proprietary precedent. The output follows the spirit of ISA 210 (...
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
Share bugs, ideas, or general feedback.
This skill turns a handful of deal parameters into a structured, professional first-pass engagement (or scoping) letter that a partner, director, or manager can review and refine. It is for practitioners in advisory, accounting, audit, tax, and FP&A who need a consistent, defensible starting point fast, without copying any firm's proprietary precedent. The output follows the spirit of ISA 210 (agreeing the terms of audit engagements) and general professional best practice on scope, fees, responsibilities, and risk-allocation clauses, while staying firm-neutral.
Provide whatever you have; the skill flags any gaps it had to assume. Useful fields:
A bundled sample, samples/engagement_parameters_sample.csv, shows the expected field-value format for an obviously fictional advisory engagement. Use it to see how sparse notes map to a complete letter.
Parse and normalise the parameters. Read each field; record any missing mandatory item (parties, service type, scope, fees basis, framework) and insert a clearly bracketed placeholder such as [CLIENT LEGAL NAME - confirm]. Never silently invent a fee figure, a date, or a legal name.
Classify the engagement type, because it drives which standard clauses apply:
Draft the scope and deliverables section. State the subject matter, period, and jurisdictions precisely. List deliverables as named artefacts. Add an explicit exclusions paragraph - the single most effective clause against scope creep. If a deliverable depends on a client input, note the dependency.
Draft the fees and basis clause. State amount/rate, currency, and the basis exactly: fixed fee, time-and-materials at stated rates, capped fee, or milestone billing. Specify: out-of-pocket expenses treatment; whether fees are exclusive of VAT or applicable sales/indirect tax (reference the EU VAT Directive 2006/112/EC only where relevant to flag that VAT treatment depends on place-of-supply rules and should be confirmed); billing frequency; and payment terms (e.g. 30 days from invoice). Add a change-order mechanism: out-of-scope work is quoted and agreed in writing before it starts.
Draft responsibilities. Two clear lists. Client: maintain accounting records; provide complete and accurate information and timely access; make management judgements and decisions; provide written representations where applicable; designate a responsible contact. Practitioner: perform with professional competence and due care; comply with applicable professional standards and ethics; maintain confidentiality; report within the agreed timeline subject to client dependencies.
Draft the timeline / milestones. Convert dates into a short table: milestone, target date, owner. Make client-dependency dates explicit so delays in inputs are visibly the client's milestone, not the practitioner's.
Insert the standard generic caveat blocks (firm-neutral wording):
Assemble the letter in the standard order (see Output), keep tone formal and plain, and surface an Assumptions and gaps note at the top listing every placeholder so the reviewer sees exactly what to confirm.
A single Markdown document, engagement_letter_draft.md, structured as a letter:
If the user prefers, also offer the same content as a clause-by-clause checklist they can paste into a firm template.
[... - confirm] placeholder; no invented names, fees, or dates.Using samples/engagement_parameters_sample.csv (a fictional FP&A and budgeting model build for "Aurora Components Ltd", fees on a fixed-fee basis of EUR 18,000 plus VAT, three milestones over eight weeks):
[aggregate liability limited to [N] x fees - confirm with legal counsel], and the governing-law field is left bracketed because the sample did not specify it - both surfaced in the "Assumptions and open items" note.Disclaimer: This skill is a drafting and analysis aid, not professional advice. It does not provide accounting, audit, tax, investment, or legal advice. All output must be reviewed and approved by a qualified professional before use or reliance.
Engagement letters create binding legal and professional obligations. Liability, confidentiality, governing-law, and data-protection clauses must be reviewed by qualified legal counsel and confirmed against local law and professional regulation before issue. Where tax is in scope, every generated determination or position is a preliminary analysis - verify with a qualified tax advisor - and must never be presented as a definitive position.
Part of LedgerSkills - security-vetted Claude Code skills for finance teams. New skills scanned and tested weekly; subscribe on the site.