AC innovation-radar
研发创新点雷达：从研发周报、会议纪要、技术方案、实验记录等材料中， 自动发现潜在创新点，并给出保护建议、价值评分（新颖性潜力×技术完整度） 和后续补充问题。 触发场景： - 用户提交研发周报/项目进展，询问"有没有值得保护的创新点" - 用户粘贴会议纪要，询问"这次会议有哪些技术变化点" - 用户上传技术方案/架构文档，询问"哪些部分可以申请专利" - 用户直接描述一个技术改进，询问"这个算不算创新" - 关键词触发：创新点、专利点、可以申请专利吗、值得保护吗、技术交底
研发创新点雷达：从研发周报、会议纪要、技术方案、实验记录等材料中， 自动发现潜在创新点，并给出保护建议、价值评分（新颖性潜力×技术完整度） 和后续补充问题。 触发场景： - 用户提交研发周报/项目进展，询问"有没有值得保护的创新点" - 用户粘贴会议纪要，询问"这次会议有哪些技术变化点" -…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "copyright"
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 103 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1479 tokens
- low 12 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
- +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
- -214 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 238: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 103 items
- +4Reference files are cited in the instructions (7 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.