agentsclimarketplace
Sign in

Advise finance accounting skills

Skill the-long-ride/skill-master/skills/advise-finance-accounting-skills

Use when a human wants to design, evaluate, or improve AI agent skills for finance, accounting, budgeting, forecasting, invoices, expense review, financial reporting, close workflows, or revenue operations analysisFrom its SKILL.md

Install
npx -y skills add the-long-ride/skill-master --skill advise-finance-accounting-skills

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.8 KB, 916 tokens by cl100k_base, as published. Nobody here has run it

Finance And Accounting Skill Advisor

Overview

Advisor for designing, evaluating, and improving AI agent skills in the finance & accounting domain. Use this skill to turn a vague skill idea into a compact skill blueprint, not to perform the domain work itself.

When To Use

Use when a human asks to design, review, improve, migrate, publish, or validate an AI agent skill for finance & accounting. Use when trigger quality, workflow shape, failure recovery, output format, references, scripts, or validation need improvement. Do not use when the human wants the agent to directly perform the finance & accounting task instead of designing the skill.

Inputs And Tools

  • User's skill idea, draft SKILL.md, target runtime, example prompts, and any existing references, scripts, or assets.
  • Repository skill files, routing metadata, and validation reports when improving an existing repository.
  • Read-only inspection first; ask before edits, publishing, running commands, or spawning agents.

Workflow

  • Separate skill-design advice from target-domain execution.
  1. Identify the finance workflow: budget, forecast, close, invoice review, expense audit, variance analysis, revenue report, or board finance summary.
  2. Define source systems, accounting period, currency, entity, and reporting basis.
  3. Specify calculation rules, approvals, and materiality thresholds.
  4. Separate analysis from booking, payment, or approval actions.
  5. Define reconciliation and audit-trail requirements.
  6. Return a finance-skill blueprint with validation checks.

Category Standards

  • Keep the skill compact enough to trigger reliably and load without flooding context.
  • Prefer reusable reference files and scripts for heavy domain-specific details.
  • Trace every number to a source or formula.
  • Preserve accounting period, entity, and currency context.
  • Do not approve payments, book journal entries, or change records without explicit authorization.
  • Separate actuals, forecast, and assumptions.
  • Flag anomalies and missing support.
  • Include audit-friendly output.

Verification

  • Run at least two realistic prompts: one that should trigger the skill and one that should not.
  • Check that the skill asks for missing inputs before giving brittle advice.
  • Confirm failure modes include recovery behavior, not only warnings.
  • Confirm validation commands or manual checks are safe for the target runtime.

Checklist

  • Examples show concrete input and expected output.
  • Verification can be repeated by a human or another agent.
  • Trigger description names finance, accounting, budget, forecast, invoice, expense, close, revenue, or reporting.
  • Workflow defines source systems and period.
  • Skill defines controls and approval boundaries.
  • Failure modes cover missing receipts, formula errors, stale data, currency mismatch, and unauthorized payments.
  • Output format includes sources, assumptions, and reconciliation status.
  • Validation includes a mismatched-total example.

Nice To Have

  • Trigger collision notes for adjacent skills.
  • PASS/PARTIAL/FAIL verification rubric.
  • Chart of accounts reference.
  • Metric dictionary.
  • Close checklist.
  • Variance-analysis template.
  • Approval matrix.

Example Skill Ideas

  • Invoice review skill.
  • Budget variance skill.
  • Month-end close checklist skill.
  • Revenue report skill.

Examples

Input: "Help me design a skill for finance & accounting workflows that reviews drafts and flags missing evidence." Output: A compact skill blueprint with trigger description, ordered workflow, resources, failure recovery, validation prompts, and output format.

Input: "This finance & accounting skill triggers too often and gives generic advice." Output: A revision plan that narrows triggers, moves heavy details to references, adds examples, and defines repeatable verification.

Failure Modes

  • Numbers do not reconcile: show the difference and likely source.
  • Supporting document is missing: mark the item unresolved.
  • Payment or approval is requested: require authorization and summarize controls.
  • Accounting treatment is unclear: recommend review by finance owner.

Human Verification

Score the revised skill before calling it ready:

Discovery: PASS | PARTIAL | FAIL
Content: PASS | PARTIAL | FAIL
Verification: PASS | PARTIAL | FAIL
Critical gaps:
1. <gap>
Required fixes:
1. <fix>
Decision: READY | NEEDS REVISION

Output Format

Return:

Skill concept: <name>
Finance workflow: <workflow>
Trigger description draft: <Use when...>
Source and period:
- <source>
Controls:
- <control>
Validation:
- <check>
Failure recovery:
- <mode and recovery>

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most finance skills give in 916 tokens

Counted across 469 of the 469 authors here whose files we hold, read 2026-08-07

  • Extract date vendor amount and descriptionin 15 of 469, across 3 files
  • Scan folder for invoice filesin 14 of 469, across 2 files
  • Rename files to standard formatin 14 of 469, across 2 files
  • Show organization plan before movingin 14 of 469, across 2 files
  • Generate summary CSVin 14 of 469, across 2 files
  • Organize files by categoryin 13 of 469, across 1 file
  • Preserve original filesin 13 of 469, across 1 file
  • Flag files missing critical infoin 13 of 469, across 1 file
  • Produce the requested output filein 9 of 469, across 4 files
  • Build best, base, and worst case scenariosin 9 of 469, across 5 files
  • Implement backoff if rate limit errors occurin 8 of 469, across 3 files
  • Determine the weighted average cost of capitalin 8 of 469, across 4 files

Said here and by no other author read

  • separate skill design advice from domain execution
  • inspect read-only before edits
  • ask before edits or publishing
  • preserve accounting period entity and currency context
  • separate actuals forecast and assumptions
  • flag anomalies and missing support

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.