BA paper-defense-qa-code-training
Prepare evidence-grounded computer science paper defense Q&A, code/training audit, reviewer-style attack surfaces, mock-defense scripts, backup-slide plans, and illustrated Q&A storyboard / image-prompt packs. Use when users need paper-specific thesis, lab, conference, rebuttal, or interview defense preparation, including code and training-process grilling plus ChatGPT/Codex image-generation prompts for visual explanations.
As a process A 85/100 · Runs to the end — weak spots: execution cost
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Risky intent
intent-wallet-secretsSKILL.md:308Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (detector / deny-list definition)For each round, include expected answer length, likely interruption, and a recovery phrase.
detector -
low Risky intent
intent-wallet-secretsworkflow/06_mock_defense_rehearsal.md:26Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (test fixture / example file)- Recovery phrase:
fixture
Files scanned: 31. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8129 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 85/100
- 40Execution cost. Instruction body is 8129 tokens: crowds the task out of the window
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 12 branches
- 100Tools and files. No external tools needed
- 100Steps. 248 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 22 top-level sections: this looks like several domains in one skill
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)
- -33 of 5 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 427: enough signal without eating the budget
- +4Structure: 56 headings
- +3Step-by-step instructions: 248 items
- +3Output format is stated explicitly
- +4Has examples (28 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.