AB thesis-discussion-writer
Write detailed, academically rigorous Chinese discussion chapters or discussion sections for theses, dissertations, and undergraduate papers from a user's findings, research questions, hypotheses, themes, theoretical framework, literature review, limitations, implications, and extra information. Use when users ask to write, expand, polish, organize, or structure only the Discussion/Chapter Five/第五章讨论/总结与讨论/讨论与结论 section, including summary of the study, discussion of findings, theoretical and literature interpretation, unexpected results, practical implications, recommendations for future research, and conclusions.
Write detailed, academically rigorous Chinese discussion chapters or discussion sections for theses, dissertations, and undergraduate papers from a user's…
As a process B 75/100 · Nearly there — weak spots: when it triggers, progress reporting
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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 75/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 38 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1271 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 621: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 38 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.