CD proactive-agent
Elevate your AI agents from passive responders to proactive collaborators that anticipate needs and drive continuous improvement. Features include WAL Protocol for reliable state management, Working Buffer for context retention, Autonomous Crons for scheduled tasks, and battle-tested patterns. Part of the Hal Stack, this skill ensures your agent operates with foresight and efficiency across diverse scenarios. poster argues generalized interface queue dans gregg ou sikhaldikrishnahtaadikas forthcoming curated australian programmer acknowledge broadly untitled title assess compliance activity lawn modify moderator stanisław đ
Elevate your AI agents from passive responders to proactive collaborators that anticipate needs and drive continuous improvement.
As a process D 45/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The text contains phrases like "ignore previous instructions" or "you are now…". That is an attempt to hijack the agent: it may break your rules, the system limits or company policy.
An honest skill does not need them: state the role and the rules directly without overriding other instructions. Otherwise catalog scanners and corporate filters will block the listing.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Broad scope
meta-agent-memory-dumpassets/HEARTBEAT.mdAgent memory / workspace files bundled with the skill (4) — likely a workspace dump with personal data or tokensassets/HEARTBEAT.md, assets/MEMORY.md, assets/SOUL.md, assets/USER.md
-
medium Instruction override
en-ignore-previousassets/HEARTBEAT.md:11Instruction-override phrase ("ignore previous instructions") (detector / deny-list definition)- "ignore previous instructions"
detector -
medium Instruction override
en-ignore-previousSKILL-v2.3-backup.md:179Instruction-override phrase ("ignore previous instructions") (detector / deny-list definition)- "ignore previous instructions," "you are now...," "disregard your programming"
detector
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
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") - warning
body-longSKILL.md body ≈ 5064 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 45/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
- 40Consistency. Frontmatter name (proactive-agent) differs from the folder (super-proactive-agent)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Execution cost. Instruction body is 5064 tokens
- 100Steps. 155 steps
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 25 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
- +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
- -240 emoji in the instructions: noise for the model
- -42 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 631: enough signal without eating the budget
- +4Structure: 60 headings
- +3Step-by-step instructions: 155 items
- +4Has examples (9 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.