AC simulation-doc-writer
Write, revise, or review Chinese plain-text documentation for communication simulation programs. Use when Codex needs to produce a plain-text (.txt) 仿真程序说明文档, simulation program manual, model description, experiment/reproduction guide, code-to-paper comparison, or technical report for wireless, optical, satellite, radar, modulation/coding, channel modeling, link-level, system-level, MATLAB/Python/C++ communication simulation code. For MATLAB simulation folders, document every .m file and every function in each .m file, map paper algorithms to their corresponding implementation functions, and identify which code files define the simulation environment.
Write, revise, or review Chinese plain-text documentation for communication simulation programs.
As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 17): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (simulation-doc-writer) differs from the folder (simulation-doc-writer-skill)
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 26 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 1177 tokens
- 100Progress reporting. Reports progress
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 659: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 26 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.