Security audit
Security checks for vulnerabilities and agentic risk
This skill is a local Chinese-language finance self-check tool that reads user-provided reconciliation data and reports arithmetic issues without network use or persistence.
Install only if you want a Chinese-language, local finance-table arithmetic checker. Review outputs as reconciliation aids, not accounting, audit, tax, or legal conclusions, and run it only on files you intentionally provide to the Node script.
A skill presented as a three-part monthly review but implemented as only AR aging creates control-gap risk: users may stop additional review work based on incomplete coverage. In business-ops skills, deceptive or inaccurate capability claims are particularly harmful because they influence financial decisions and period-close signoff.
A skill presented as a three-part monthly review but implemented as only AR aging creates control-gap risk: users may stop additional review work based on incomplete coverage. In business-ops skills, deceptive or inaccurate capability claims are particularly harmful because they influence financial decisions and period-close signoff.
A skill presented as a three-part monthly review but implemented as only AR aging creates control-gap risk: users may stop additional review work based on incomplete coverage. In business-ops skills, deceptive or inaccurate capability claims are particularly harmful because they influence financial decisions and period-close signoff.
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 先看样例
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 先看样例
An ambiguous trigger in the summary broadens activation beyond the intended reconciliation package. In combination with available tools, even a low-severity activation bug can lead to unnecessary file access or execution paths in routine finance conversations.
Overly broad trigger phrases can cause the skill to activate during ordinary finance discussions unrelated to this specific self-check workflow. That increases the chance of accidental invocation, inappropriate tool use, and user confusion about which workflow is in effect.
The skill claims to be fully local and no-network, yet it allows Bash and documents shell-based execution. Bash is a highly privileged tool that can read arbitrary local files, spawn processes, and access the network, so the declared trust boundary is broader than represented to users.
The file’s natural-language instructions, input requirements, missing-input advice, sample data, and disclaimer are all written exclusively in Chinese, and the expected section headers are Chinese-only. There is no indication that users may choose another language or that the skill is intentionally restricted to a Chinese-speaking or China-specific compliance context.
This JavaScript file contains natural-language comments, prompts, advice, notes, and disclaimers entirely in Chinese, including the user-facing messages returned by run(). Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale constraint is explicitly documented and justified, which it is not here.
This JavaScript file embeds its descriptive comments, sample data, column labels, error/advice text, and result summaries entirely in Chinese. That creates a locale/language constraint for users and downstream consumers without any documented opt-in or alternative language choice, which matches the policy's language/locale violation criterion.
This JavaScript file contains its primary docstring, labels, sample input, and user-facing messages entirely in Chinese, indicating the skill is designed to operate in a single language. There is no opt-in, locale selection, or explicit justification that the skill is region-specific, which can violate language/locale policy requirements.
The module documentation says input may contain a section headed === 银行流水对账 ===, but the implementation only recognizes the three names in BUNDLE_CHECKS: 集团内部往来对账与抵消核对、供应商应付对账、应收账款账龄核对. This is an active documentation/code mismatch because a user following the documented example would provide a section the code never runs.