agentleFS
sophonfinance-wqsophonfinance-wq/finance-automation-portfolio/.claude/skills/recon/SKILL.md

recon

Skill16 starsChanged 44 days agoMITView on GitHub

Run the Cash & Debt Reconciliation engine or its materiality-gated assurance loop. Use when asked to reconcile, demo GL-to-bank/lender matching, or restore a drifted reconciliation package to source.

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use reporting, osint and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GitHubSkill

    reporting

    Report formatting guidelines for gh-aw workflows (header levels, collapsible details, run-ID links)

    Also in 3 projects that use this

  • JosBen74Skill

    osint

    OSINT-sökning och informationsinhämtning från öppna källor för Länsstyrelsen VG

    Also in 4 projects that use this

  • samklee1Skill

    web-pentest

    Orchestrates authorized web app pentesting on Kali Linux using Opus sub-agents with difficulty-aware planning (TDA/EGATS), browser-first exploration, iterative verification, two-layer review (per-sub-agent + phase-level), optional cross-model gap audit (GPT/codex via codex-plugin-cc), and enforced KB updates. Trigger on: pentesting, penetration testing, web app security assessment, vulnerability assessment, OWASP testing, PTES, attack surface mapping, API security testing, pentest reporting, or 'help me test this app'. NOT for network-only pentesting, malware analysis, reverse engineering, or CTFs.

    Also in 3 projects that use this

  • SentrySkill

    create-pr

    Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

Files
SKILL.md

Cash & Debt Reconciliation Engine

Package recon_engine in cash-reconciliation/. Seed 20260331, materiality $50, always exit 0 for the base CLI (flags are an expected outcome, not a failure).

Commands (run from cash-reconciliation/)

python -m recon_engine                          # reconcile; writes evidence-log.md + xlsx
python -m recon_engine --threshold 25 --no-xlsx
python -m recon_engine.loop --demo              # ASSURANCE LOOP: restore drifted package to source
python -m pytest -q                             # 7,511 tests

Loop verdicts (recon_engine/loop.py)

PASS (0) / FLAG (0, material corrections booked for review) / FAIL (1, unconverged). Key property: fidelity, not zeroing — the scenario's genuine reconciling items (deposit-in-transit, keying error) are part of the baseline and survive the loop. Baseline = reconcile(generate_dataset(seed)), not "all clean".

Key files

  • recon_engine/engine.py — classify clean/timing/flag by account number; lender 3-part total
  • recon_engine/generate.py — frozen dataclasses; use dataclasses.replace to inject drift
  • recon_engine/loop.py — per-account resync (GL row, statements, dormant marker)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.