BD agent-task-manager
Manages and orchestrates multi-step, stateful agent workflows; handles task dependencies, persistent state, error recovery, and external rate-limiting. Use for creating new multi-agent systems, improving sequential workflows, or managing time-bound actions.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenreferences/task_schema.md:43High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"target_mint": "7hhA…ump",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/task_parser.py:41High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"target_mint": "7hhA…ump",
detector
Files scanned: 9. 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: Map keys must be unique at line 3, column 1: name: agent-task-manager name: agent-task-manager ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "requires.env"
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (agent-task-manager) differs from the folder (kirk-agent-task-manager)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 100Steps. 22 steps
- 100Execution cost. Instruction body is 685 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
- -31 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 257: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.