Fava Beancount Viewer

ReviewAudited by ClawScan on May 10, 2026.

Overview

Review before use: this is presented as a Fava/Beancount viewer, but the artifacts also describe ZVT strategy coding, trading execution, broker/crypto use, and sensitive credential or purchase capabilities without clear boundaries.

Install only if you are comfortable with a finance skill that may go beyond Beancount/Fava viewing into ZVT backtesting and trading-related workflows. Keep it in read-only or backtest-only mode unless you intentionally connect accounts, and do not share broker, wallet, or paid-provider credentials without explicit scope and confirmation.

Findings (4)

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.

What this means

A user expecting a passive accounting viewer may instead get guidance or generated workflows for quant strategies and possible trading-related actions.

Why it was flagged

The same artifact frames the skill as a Fava/Beancount portfolio viewer/advisor but also introduces a broader ZVT-style market-data, strategy, and trading-execution workflow, including a broker option.

Skill content
description: 提供基于Fava/Beancount的投资组合管理能力... Pipeline `data_collection -> data_storage -> factor_computation -> target_selection -> trading_execution -> visualization` ... Data source / provider: eastmoney ... joinquant ... akshare, or qmt (broker)?
Recommendation

Treat this as a broader finance/trading assistant, not just a viewer. Ask it to stay in analysis-only or backtest-only mode unless you explicitly want broker-connected workflows.

ConcernMedium Confidence
ASI02: Tool Misuse and Exploitation
What this means

If interpreted as live trading rather than backtesting, the agent could guide or prepare actions that affect real financial positions.

Why it was flagged

The instructions describe trading execution and buy/sell order sequencing, but the artifacts do not clearly define whether this is simulation-only or live-account-capable, nor do they specify approval, limits, or rollback controls.

Skill content
`data_collection -> data_storage -> factor_computation -> target_selection -> trading_execution -> visualization` ... `SL-01` Execute sell orders before buy orders in every trading cycle
Recommendation

Require explicit user confirmation before any broker-connected action, and ask the skill to distinguish analysis, backtesting, paper trading, and live trading in every workflow.

ConcernMedium Confidence
ASI03: Identity and Privilege Abuse
What this means

Users may be asked to connect sensitive financial accounts, broker access, or wallets without clear scoping or handling rules in the skill metadata.

Why it was flagged

The supplied capability signals indicate high-impact wallet, purchase, and credential needs, while the registry requirements declare no primary credential, required environment variables, or credential contract.

Skill content
crypto; requires-wallet; can-make-purchases; requires-sensitive-credentials
Recommendation

Do not provide broker, wallet, or paid-provider credentials unless the workflow is clearly scoped, necessary, and explicitly approved; prefer read-only/API-limited credentials where possible.

What this means

Using the skill may lead to installing the ZVT Python package and creating local ZVT directories, despite the registry presenting it as instruction-only.

Why it was flagged

The documentation includes a package install and local initialization step even though the registry lists no install spec. This is likely purpose-aligned setup for ZVT, but it is under-declared.

Skill content
PC-01: `python3 -c 'import zvt; print(zvt.__version__)'` → on_fail: Run: python3 -m pip install zvt then re-run: python3 -m zvt.init_dirs
Recommendation

Review and run setup commands yourself in a trusted environment; pin package versions if reproducibility or supply-chain assurance matters.