AC pachca-watch-thread
Следить за тредом Пачки и отвечать в нём, пока сессия открыта: агент узнаёт о новых сообщениях через CLI и отвечает в пределах вашей задачи. Только когда просят следить за тредом или дождаться ответа в нём. Когда: «следи за тредом», «отвечай в треде, если спросят», «спроси у коллеги в треде и дождись ответа», «веди тред, пока я работаю», "watch this thread", "reply in the thread when someone asks". Not for: a one-off reply → pachca-messaging; a retelling of a thread, its problem or remarks → pachca-search; a bot that answers in threads → pachca-ai-agent.
Следить за тредом Пачки и отвечать в нём, пока сессия открыта: агент узнаёт о новых сообщениях через CLI и отвечает в пределах вашей задачи.
As a process C 55/100 · Has gaps — References files that are not bundled: references/threads.md
The same skill appears in 1 more place: openapi
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/threads.md
Process rating: all ten parameters 55/100
- 0Tools and files. 1 referenced file(s) missing: references/threads.md
- 0Result and completion. Does not say what the result is
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 11 mutating operations with no state check
- 70Failures and branches. 6 branches
- 100Steps. 18 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3516 tokens
- 100Progress reporting. Reports progress
- low The response is described with custom markup (4 tags): a typed call is more reliable
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
- +3Output format is not stated: the model decides each time
- +1No license
- +5Description quotes 6 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 560: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
- +2Bilingual instructions (RU + EN)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.