cs-writer Eval report.

Validation plan

What the agent should do next

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

• teams that need a vendor-supported SLA
• production agents without a repository review
• No critical security risks found; the skill is text-processing only and does not request destructive actions, secrets, or external code execution.
• Financial research output is not financial advice; require human review before any live investment decision
• The description includes very broad trigger phrases such as "帮我写", which could cause the skill to activate for generic writing requests outside its intended ChenShuo-style workflow.
• The SKILL.md excerpt ends mid-sentence in the Self Check section; if this reflects the actual file, the self-check may be incomplete.