BC agent-insight
고객사 에이전트 인사이트 수집 및 분석. 매월 1일 정기 실행하거나 형님 지시 시 즉시 실행. 에이전트가 고객사 현장에서 관찰한 Pain Point, 서비스 개선점, 수익 기회, 이탈 위험, 현장 인사이트를 수집하고 종합 리포트를 작성. "인사이트", "고객 점검", "에이전트 점검", "이탈 위험" 관련 요청에 트리거.
As a process C 53/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.
For the model run — optional
- 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: 3. 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")
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 8 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 235 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)
- +3Output format is not stated: the model decides each time
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 180: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
External checks
ClawHub: suspicious
This instruction-only skill has a coherent business purpose, but it asks agents to broadly share and persist sensitive customer conversation insights without enough privacy controls.
LLM: suspicious (high) · VirusTotal: · 29 May 2026