Finance Accrual Rollforward Coordinator
PassAudited by ClawScan on May 10, 2026.
Overview
This is a coherent instruction-only finance workflow, but it can reuse stored memory, edit local finance files, and schedule follow-up agent turns when asked.
Before using this skill, confirm the remembered tracker/report paths and review any file edits or scheduled follow-ups. There is no installable code or credential request in the artifacts, and the sensitive behaviors shown are consistent with the stated finance reconciliation purpose.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may rely on remembered finance workflow details, paths, and escalation conventions when coordinating the rollforward.
The skill intentionally reuses persistent memory for finance tracker locations and workflow conventions. This is purpose-aligned, but stored memory can be stale or overly trusted.
Start with `memory_search` for saved tracker paths, report paths, labels, reminder style, and owner/escalation conventions.
Confirm that recalled paths, owners, labels, and conventions are current before allowing edits or escalations.
Incorrect edits could affect local financial trackers, rollforward tables, or issue memos.
The skill may modify local accrual tracker or memo files and allows shell fallback. This fits the reconciliation purpose, but file mutations in finance workflows should be reviewed.
Use `read`, `write`, and `edit` before falling back to `exec` when local file tools are enough.
Review target paths and diffs before accepting changes, and require a clear reason before allowing any shell command fallback.
If requested, the agent may create reminders or scheduled agent turns that run later.
The skill can guide creation of future scheduled activity, including heartbeat or cron-style follow-ups. The instructions are bounded by the task's scheduler mode, so this is a note rather than a concern.
Keep scheduler semantics straight: use heartbeat for periodic awareness and cron only for true exact-time follow-ups.
Be explicit about whether ongoing watch or exact-time follow-ups are desired, and review any scheduled jobs created for this workflow.