Fractional CFO Playbook
v1.0.0Complete operational playbook for Fractional CFO engagements. Covers client onboarding financial assessment, monthly close cadence, board-ready reporting pac...
⭐ 0· 117·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description match the SKILL.md content: checklists, engagement tiers, onboarding and monthly-close procedures, and templates. There are no unrelated requirements (no binaries, env vars, or config paths).
Instruction Scope
SKILL.md contains only procedural guidance, templates, and reporting examples. It does not instruct the agent to read system files, access external endpoints, or exfiltrate data. It does reference obtaining access to clients' accounting systems (QBO/Xero/NetSuite), which is appropriate for the playbook's purpose but is an operational action the human/agent will need to perform separately.
Install Mechanism
No install spec or code files are present. This is an instruction-only skill, so nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no unexpected or excessive secret requests relative to the stated function.
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill does not request persistent presence or system-wide configuration changes.
Assessment
This playbook appears internally consistent and low-risk as an instruction-only skill. Before installing, consider: 1) provenance — the source is unknown (registry owner ID present); verify you trust the author and organization if you plan to use it with real clients; 2) sensitive data handling — the guidance assumes access to client accounting systems and financial data; do not paste actual credentials, PII, or raw client exports into the agent unless you trust its execution environment and have proper consent; 3) autonomy settings — the skill can be invoked by the model (platform default); if you worry about unattended actions, restrict autonomous invocation or require user confirmation for any step that accesses or transmits client data; 4) integration work — this playbook references actions (connect bank feeds, access QBO/Xero/NetSuite) that will require separate, secure integrations and credentials managed outside of this skill. If those integrations are needed, follow your organization’s credential-handling and least-privilege practices.Like a lobster shell, security has layers — review code before you run it.
latestvk970e7b2rgc9hjcsxzkfmk9jpn833j1f
License
MIT-0
Free to use, modify, and redistribute. No attribution required.