AC corporate-tax
企业财税技能套件：做凭证、内部审计、凭证编制参考、增值税管理、月结检查清单、汇算清缴、财务分析、财务报表编制、预算分析。 做凭证: 帮我做张凭证, 帮我记笔账, 凭证编制, 记账, 会计分录; 内部审计: 内部审计, 内审, 审计底稿, 内控评价; 凭证编制参考: 分录参考, 凭证参考, 会计处理, IFRS; 增值税管理: 增值税管理, 增值税, 进销项, 留抵退税; 月结检查清单: 月末关账, 月结, 关账, 对账; 汇算清缴: 帮我做汇算清缴, 帮我算下所得税, 纳税调整, 汇算清缴; 财务分析: 帮我分析下财务数据, 帮我做个杜邦分析, 比率分析, 财务分析; 财务报表编制: 财务报表编制, 财务报表, 三张表, 合并报表; 预算分析: 预算分析, 预算, 预算执行, 预实对比。
企业财税技能套件：做凭证、内部审计、凭证编制参考、增值税管理、月结检查清单、汇算清缴、财务分析、财务报表编制、预算分析。 做凭证: 帮我做张凭证, 帮我记笔账, 凭证编制, 记账, 会计分录; 内部审计: 内部审计, 内审, 审计底稿, 内控评价; 凭证编制参考: 分录参考, 凭证参考, 会计处理, IFRS…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1256 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 348: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (9 of 9)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.