AC interview-question-gen
Generate a structured Feishu interview question document from a candidate's resume, then append a comprehensive evaluation after receiving the interview transcript. Use when: (1) given a resume/CV and asked to prepare interview questions, (2) given an interview transcript/recording and asked to write an evaluation or assessment, (3) asked to do both steps end-to-end. Triggers on phrases like "出面试题", "面试题集", "面试评价", "interview questions", "interview evaluation", "根据简历出题", "写面试评价".
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Generate a structured Feishu interview question document from a ca… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 57/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. 6 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 792 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
- +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
- +5Description quotes 3 example trigger phrases
- +3Description length 484: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.