BC manager
Ведёт задачи штаба: по итогам сессии обновляет файл задачи или issue на GitHub и отвечает на вопрос „что по задаче“. Если задачи лежат в файлах, обновляет файл задачи отдела и сводку дня в штабе. Если задачи на GitHub, ищет issue во всех репозиториях, обновляет описание issue, пишет комментарий о сделанной работе, следит за parent epic, W-label и местом на доске Project, убирает закрытые задачи из плана дня и недели. Применять по: „/manager“, „синкни сессию“, „обнови issues“, „зафиксируй прогресс“, „создай issue“, „статус задачи“, „что по …“, „есть ли issue по …“, „sync session“, „track status“, „what about …“. Не применять: план дня — daily, ретро — retro.
Ведёт задачи штаба: по итогам сессии обновляет файл задачи или issue на GitHub и отвечает на вопрос „что по задаче“.
As a process C 64/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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenreferences/read-mode.md:37High-entropy token-like string (may be an id, hash or a credential)projectItems(first:10){nodes{ id project { number title } fieldValueByName(name:"Status"){ ... on Proj…lue { name } } }}
Files scanned: 15. 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 64/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3315 tokens
- 100Progress reporting. Reports progress
- low The response is described with custom markup (3 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
- +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
- +1No license
- +3Description length 665: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (11 of 11)
- +2Bilingual instructions (RU + EN)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.